Uh oh!
There was an error while loading. Please reload this page.
HttpConnectionPool improvements - #62935
Conversation
ghost
commented
Dec 17, 2021
Tagging subscribers to this area: @dotnet/ncl Issue DetailsTwo related improvements: (1) Reduce contention on the pool lock. This is done mainly by (a) not calling TrySetResult on the queued waiter under the lock -- instead, do this outside the lock and retry as necessary for canceled requests; (b) avoid doing diagnostic logging under the lock. Fixes #60654
|
geoffkizer
commented
Dec 17, 2021
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
geoffkizer
commented
Dec 22, 2021
@dotnet/ncl Can I get a review? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
geoffkizer
commented
Jan 5, 2022
I pushed fixes for the issues identified above. |
geoffkizer
commented
Jan 5, 2022
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Two related improvements:
(1) Reduce contention on the pool lock. This is done mainly by (a) not calling TrySetResult on the queued waiter under the lock -- instead, do this outside the lock and retry as necessary for canceled requests; (b) avoid doing diagnostic logging under the lock.
(2) Improve handling of failed connection attempts so we don't fail requests unnecessarily. See #60654 for details.
Fixes#60654