mirror of
https://github.com/nspcc-dev/neo-go.git
synced 2024-11-29 23:33:37 +00:00
9efc110058
32 is a very good number, but we all know 42 is a better one. And it can even be proven by tests with higher peaking TPS values. You may wonder why is it so good? Because we're using packet-switching networks mostly and a packet is a packet almost irrespectively of how bit it is. Yet a packet has some maximum possible size (hi, MTU) and this size most of the time is 1500 (or a little less than that, hi VPN). Subtract IP header (20 for IPv4 or 40 for IPv6 not counting options), TCP header (another 20) and Neo message/payload headers (~8 for this case) and we have just a little more than 1400 bytes for our dear hashes. Which means that in a single packet most of the time we can have 42-44 of them, maybe 45. Choosing between these numbers is not hard then. |
||
|---|---|---|
| .. | ||
| capability | ||
| extpool | ||
| payload | ||
| blockqueue.go | ||
| blockqueue_test.go | ||
| compress.go | ||
| discovery.go | ||
| discovery_test.go | ||
| fuzz_test.go | ||
| helper_test.go | ||
| message.go | ||
| message_string.go | ||
| message_test.go | ||
| notary_feer.go | ||
| peer.go | ||
| prometheus.go | ||
| server.go | ||
| server_config.go | ||
| server_test.go | ||
| state_sync.go | ||
| tcp_peer.go | ||
| tcp_peer_test.go | ||
| tcp_transport.go | ||
| transport.go | ||