Test HTTP/2 benchmarks with artificially induced latency

Open
#1,672 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp

Research direction

Start by reviewing the existing end-to-end benchmark setup and the Kestrel Connection Middleware entry point referenced in the issue. Determine how to induce latency for HTTP/2 benchmark connections, then verify that benchmarks exercise high-latency flow-control behavior and report results under the induced conditions.

Written by the indexing model from the issue text.

Description

This might be interesting for all of our end-to-end benchmarks, but benchmarking with high-latency connections is particularly important for HTTP/2 because Kestrel and HttpClient implement their own flow control logic. This came up during discussion with some msquic folks about the relatively small 128 KB default size of Kestrel's HTTP/2 connection window.

An artificial latency inducer is probably most easily done with Kestrel Connection Middleware.

@nibanks

Dominant language
C#
Stars
1.2k
Forks
244
Avg merge
4d 4h
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aspnet/Benchmarks

All issues in aspnet/Benchmarks

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.