{"action":"created","issue":{"url":"https://api.github.com/repos/HangfireIO/Hangfire/issues/1266","repository_url":"https://api.github.com/repos/HangfireIO/Hangfire","labels_url":"https://api.github.com/repos/HangfireIO/Hangfire/issues/1266/labels{/name}","comments_url":"https://api.github.com/repos/HangfireIO/Hangfire/issues/1266/comments","events_url":"https://api.github.com/repos/HangfireIO/Hangfire/issues/1266/events","html_url":"https://github.com/HangfireIO/Hangfire/issues/1266","id":362689411,"node_id":"MDU6SXNzdWUzNjI2ODk0MTE=","number":1266,"title":"StackExchange.Redis 2.x","user":{"login":"brightertools","id":6533238,"node_id":"MDQ6VXNlcjY1MzMyMzg=","avatar_url":"https://avatars0.githubusercontent.com/u/6533238?v=4","gravatar_id":"","url":"https://api.github.com/users/brightertools","html_url":"https://github.com/brightertools","followers_url":"https://api.github.com/users/brightertools/followers","following_url":"https://api.github.com/users/brightertools/following{/other_user}","gists_url":"https://api.github.com/users/brightertools/gists{/gist_id}","starred_url":"https://api.github.com/users/brightertools/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brightertools/subscriptions","organizations_url":"https://api.github.com/users/brightertools/orgs","repos_url":"https://api.github.com/users/brightertools/repos","events_url":"https://api.github.com/users/brightertools/events{/privacy}","received_events_url":"https://api.github.com/users/brightertools/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":11,"created_at":"2018-09-21T16:26:36Z","updated_at":"2018-10-19T06:34:19Z","closed_at":null,"author_association":"NONE","body":"\r\nI have a .net core 2.1 app that uses HangfirePro with redis, SignalR with redis and session with redis.. \r\n\r\nThe app is currently referencing the \"StrongName\" version 1.2.6 , and I seems to have many timeouts, which is is causing havoc with my sessions. I want to try StackExchange.Redis 2.x and wondering when this will be available within HangFire Pro?"},"comment":{"url":"https://api.github.com/repos/HangfireIO/Hangfire/issues/comments/431259590","html_url":"https://github.com/HangfireIO/Hangfire/issues/1266#issuecomment-431259590","issue_url":"https://api.github.com/repos/HangfireIO/Hangfire/issues/1266","id":431259590,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMTI1OTU5MA==","user":{"login":"odinserj","id":1078718,"node_id":"MDQ6VXNlcjEwNzg3MTg=","avatar_url":"https://avatars1.githubusercontent.com/u/1078718?v=4","gravatar_id":"","url":"https://api.github.com/users/odinserj","html_url":"https://github.com/odinserj","followers_url":"https://api.github.com/users/odinserj/followers","following_url":"https://api.github.com/users/odinserj/following{/other_user}","gists_url":"https://api.github.com/users/odinserj/gists{/gist_id}","starred_url":"https://api.github.com/users/odinserj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/odinserj/subscriptions","organizations_url":"https://api.github.com/users/odinserj/orgs","repos_url":"https://api.github.com/users/odinserj/repos","events_url":"https://api.github.com/users/odinserj/events{/privacy}","received_events_url":"https://api.github.com/users/odinserj/received_events","type":"User","site_admin":false},"created_at":"2018-10-19T06:34:19Z","updated_at":"2018-10-19T06:34:19Z","author_association":"MEMBER","body":"The majority of the timeout problems related to .NET Core application was caused by inner implementation of the networking layer of SE.Redis in the `netstandard1.5` target, which was the only available for .NET Core applications in version 1.2.6 and below.\r\n\r\nOther platforms worked well, because in .NET Framework, custom threads were used to process responses, in `netstandard2.0` (unavailable in official SE.Redis 1.2.6 and below) it's possible to process them in I/O Completion Port threads. But in `netstandard1.5` we are limited only to worker threads to process response continuations. So if there are no available threads to process a response, request threads will still be blocked.\r\n\r\nYes, this issue was fixed in SE.Redis 2.0, because request/response processing logic was re-written almost entirely. But the new implementation adds another sort of blocking, this time when sending a request, which also results in worse throughput. So I've decided to take 1.2.6 as is and just add the `netstandard2.0` target and internalize it into the HF.Pro.Redis package (so there's also no need for HF.Pro.Redis.StrongName package).\r\n\r\nThese changes are available in the [Hangfire.Pro.Redis 2.3.0](https://www.hangfire.io/blog/2018/10/18/hangfire.pro.redis-2.3.0.html) released yesterday."}}
{"actor":{"display_login":"odinserj"}}