QUIC transport seems to perform slower on windows (at least in CI)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
Windows qlog does not look good. Large latency in the RTT measurement and the session takes ~300ms with a lot of gaps of inactivity on a recording with just 2 streams.
Here's the qlogs:
[qlogs.zip](https://github.com/libp2p/go-libp2p/files/11521463/qlogs.zip)
_Originally posted by @MarcoPolo in https://github.com/libp2p/go-libp2p/issues/2296#issuecomment-1555446998_
Contributor guide
No contributing guide indexed for this repository
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 by inspecting the attached qlogs.zip and comparing the Windows recording with the reported two-stream behavior, focusing on RTT latency and inactivity gaps. Trace the QUIC transport path used in Windows CI to identify where the approximately 300 ms session delay arises. Done means the cause is isolated and the Windows performance issue is corrected and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100