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
{{ message }}
Repository navigation
HttpClient creates Quic threads even if HTTP/3 is not in use #74629
Create simple console app with HTTP and run simple http1.1 request on Windows 11 or Server 22.
look at application threads.
Application crates 2x threads per core even if HTTP/3 and Quic are not in used. This was originally reported on legacy system with 54 cores. That will create 100+ threads ... for nothing.
We should figure out how to make Quic.IsSupported cheap and defer thread creation until needed.
This will impact legacy app that has no clue tor intention to use Quic or HTTP/3.
I think we can simply try opening and closing the API registration (that should deallocate the internal MsQuic threadpool), and then lazily reopen it when we actually intend to use it.
Activity
rzikm commentedon Aug 26, 2022
I think we can simply try opening and closing the API registration (that should deallocate the internal MsQuic threadpool), and then lazily reopen it when we actually intend to use it.
karelz commentedon Aug 30, 2022
Triage: This contributes to 1MB per core Working set regression on Windows 2022/Win11+ and on Linux when msquic is present.
We should fix it in 7.0.
35 remaining items
karelz commentedon Sep 13, 2022
Open questions:
karelz commentedon Sep 23, 2022
Fixed in main (8.0) in PRs #75163 and #75441 and in 7.0 (GA) in PR #75521 and in 6.0.15 in PR #80785.
karelz commentedon Jan 20, 2023
We have customers impacted on 6.0 as well - only via Kestrel. Reopening for 6.0.x backport.
ManickaP commentedon Feb 15, 2023
Closing as #80785 is merged
karelz commentedon Feb 21, 2023
Fixed also in 6.0.15 in PR #80785 -- see #74629 (comment) for details.