4 Commits (buildbot-testing)

Author	SHA1	Message	Date
Martin Holst Swende	06151eb581	p2p/msgrate: be more lenient when calculating 'mean' (#25653) ... The p2p msgrate tracker is a thing which tries to estimate some mean round-trip times. However, it did so in a very curious way: if a node had 200 peers, it would sort their 200 respective rtt estimates, and then it would pick item number 2 as the mean. So effectively taking third fastest and calling it mean. This probably works "ok" when the number of peers are low (there are other factors too, such as ttlScaling which takes some of the edge off this) -- however when the number of peers is high, it becomes very skewed. This PR instead bases the 'mean' on the square root of the length of the list. Still pretty harsh, but a bit more lenient.	2 years ago
Justin Traglia	2c5648d891	all: fix some typos (#25551) ... * Fix some typos * Fix some mistakes * Revert 4byte.json * Fix an incorrect fix * Change files to fails	2 years ago
Felix Lange	427175153c	p2p/msgrate: return capacity as integer, clamp to max uint32 (#22943) ... * p2p/msgrate: return capacity as integer * eth/protocols/snap: remove conversions * p2p/msgrate: add overflow test * p2p/msgrate: make the capacity overflow test actually overflow * p2p/msgrate: clamp capacity to max int32 * p2p/msgrate: fix min/max confusion	4 years ago
Péter Szilágyi	3e795881ea	eth, p2p/msgrate: move peer QoS tracking to its own package and use it for snap (#22876) ... This change extracts the peer QoS tracking logic from eth/downloader, moving it into the new package p2p/msgrate. The job of msgrate.Tracker is determining suitable timeout values and request sizes per peer. The snap sync scheduler now uses msgrate.Tracker instead of the hard-coded 15s timeout. This should make the sync work better on network links with high latency.	4 years ago