You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For personal education :) What is technical reason for SE.Redis to use ThreadPool.QueueUserWorkItem instead of RunContinuationsAsynchronously for asynchronous continuations?
The text was updated successfully, but these errors were encountered:
I wish I could coherently answer this, unfortunately part of the answer is we don't know. Enabling them solved some edge cases, but also caused all sorts of totally inexplicable task behavior due to deep implementations in the runtime across various scenarios. It got to the point we rolled it back, basically doing more harm than good. Some deadlock situations were the most apparent. For example: #401 and #434.
Marc/Nick,
For personal education :) What is technical reason for SE.Redis to use ThreadPool.QueueUserWorkItem instead of RunContinuationsAsynchronously for asynchronous continuations?
The text was updated successfully, but these errors were encountered: