Bug with ExtendedHandshakeMessage.MaxRequests
See original GitHub issueThere is problem with ExtendedHandshakeMessage.MaxRequests
because when creating ExtendedHandshakeMessage
property MaxRequests
not filed by value.
And when this message parsed in Mode.HandleExtendedHandshakeMessage
property PeerId.MaxSupportedPendingRequests
become 1
.
Then in Mode.PreLogicTick
value PeerId.MaxPendingRequests
always will be 2
and this make bad effect on download speed.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Jashik Got that patched and merged! Do let me know if it helps performance for you!
@carlosib This may help performance for you too. This change will make MonoTorrent -> MonoTorrent connections better, which is one area you showed an issue.
That doesn’t seem good at all! Do you think you could submit a pull request updating the code and adding a new test?