We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
crank --config https://raw.githubusercontent.com/aspnet/Benchmarks/main/scenarios/httpclient.benchmarks.yml --scenario httpclient-kestrel-get --profile aspnet-gold-lin --server.framework net9.0 --client.framework net9.0 --variable useHttpMessageInvoker=true --variable concurrencyPerHttpClient=1 --variable numberOfHttpClients=256 --json 256x1.json crank --config https://raw.githubusercontent.com/aspnet/Benchmarks/main/scenarios/httpclient.benchmarks.yml --scenario httpclient-kestrel-get --profile aspnet-gold-lin --server.framework net9.0 --client.framework net9.0 --variable useHttpMessageInvoker=true --variable concurrencyPerHttpClient=256 --variable numberOfHttpClients=1 --json 1x256.json crank --config https://raw.githubusercontent.com/aspnet/Benchmarks/main/scenarios/httpclient.benchmarks.yml --scenario httpclient-kestrel-get --profile aspnet-gold-lin --server.framework net9.0 --client.framework net9.0 --variable concurrencyPerHttpClient=1 --variable numberOfHttpClients=256 --json 256x1-client.json crank --config https://raw.githubusercontent.com/aspnet/Benchmarks/main/scenarios/httpclient.benchmarks.yml --scenario httpclient-kestrel-get --profile aspnet-gold-lin --server.framework net9.0 --client.framework net9.0 --variable concurrencyPerHttpClient=256 --variable numberOfHttpClients=1 --json 1x256-client.json
At high RPS, the contention behind using a single CancellationTokenSource to handle CancelPendingRequests shows up:
CancellationTokenSource
CancelPendingRequests
A quick test of splitting requests across ProcessorCount CTS instances based on CurrentManagedThreadId recovers the whole perf difference.
ProcessorCount
CurrentManagedThreadId
When we get around to improving this, we could also consider avoiding the linked CTS allocation we incur per request.
The text was updated successfully, but these errors were encountered:
Tagging subscribers to this area: @dotnet/ncl See info in area-owners.md if you want to be subscribed.
Sorry, something went wrong.
No branches or pull requests
At high RPS, the contention behind using a single
CancellationTokenSource
to handleCancelPendingRequests
shows up:A quick test of splitting requests across
ProcessorCount
CTS instances based onCurrentManagedThreadId
recovers the whole perf difference.When we get around to improving this, we could also consider avoiding the linked CTS allocation we incur per request.
The text was updated successfully, but these errors were encountered: