This repository has been archived by the owner on Jul 9, 2024. It is now read-only.
Use SocketsHttpHandler and EnableMultipleHttp2Connections as default handler #251
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SocketsHttpHandler
has been the default handler ofHttpClientHandler
since .NET 5. This change usesSocketsHttpHandler
directly from Kiota, without going throughHttpClientHandler
.This change also enables
EnableMultipleHttp2Connections
, which improves performance when there are over 100 concurrent requests to the same server.This can be performance tested by starting a HTTP/2 server that holds connections open for some time, and a client which makes over 100 parallel requests. e.g.
server:
client:
This causes performance to continue to scale when there are over 100 connections rather than stop scaling at 100 connections. There doesn't seem to be any performance impact, positive or negative, below 100 connections.
fixes #239