Test HTTP/2 benchmarks with artificially induced latency
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
- Domain
- backend, networking, performance
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
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aspnet/Benchmarks
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
aspnet/Benchmarks#2226 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
aspnet/Benchmarks#2015 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
aspnet/Benchmarks#2204 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
aspnet/Benchmarks#2161 ·
-
Test io_uring impactOpen
Difficulty 4/5 3-5 days Newbie friendliness 20/100
aspnet/Benchmarks#2153 · 21 reactions ·
All issues in aspnet/Benchmarks
Similar issues
-
area-NavigationView bug needs-triage team-Controls
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
microsoft/microsoft-ui-xaml#12671 · 3 comments ·
Maintainers usually reply within 2 days
-
Retarget the extension to Fallout 10.5Possibly taken @ChrisonSimtian claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Improve time codes: status hint doesn't mention the new Shift+F7 / Shift+F8 "to check" navigationOpen
Difficulty 1/5 Under an hour Newbie friendliness 88/100
SubtitleEdit/subtitleedit#16943 ·
Maintainers usually reply within 1 day