unexpected window size impact on tls conncetions with h2 large uploads
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.6k
- Forks
- 382
- Avg merge
- 20h 23m
- Merged PRs (30d)
- 9
Description
We are using H2 to transfer 16 MB payloads. During our benchmarking, we are noticing a significant difference in b/w when we are using streaming frames.
I have put together a small benchmark repo where I am sending that payload 100 times, and I see an approximately 2x difference locally as well as when I run the client and servers separately on EC2 boxes.
This is not a functionality issue, but I am wondering if there is a performance guideline around the use of frames for performance.
Contributor 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.
Research direction
Start with the linked hyper-large-payload benchmark and compare its 16 MB uploads using streaming frames with the reported alternatives. Review the h2 code and existing documentation for window and frame guidance; done should be a clear, project-supported explanation of the performance difference and any recommended usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, performance
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100