Benchmark message serialization and floods Measures what sending costs the sending thread: serializing a vote or a block into the buffer a channel sends, handing a vote to the channels of a flood, and picking those channels among 256 peers. The flood sends to fake channels, which serialize and drop, and the peers are local connections that carry no traffic, so the numbers are the sender's own work. Every benchmark reports time, heap allocations and bytes per message or flood. The per-channel loop that every flood ended in moves into `network::send_to`, so the benchmark drives the same code as the floods. The allocation counter moves to the shared benchmark header and takes the name of its unit.
__________
Type: commit
Hash: 333097e886a3a1d853b98f7ed9dd10831bc7286b
Created: today
__________
gr0v1ty/nano-node:333097e886a3a1d853b98f7ed9dd10831bc7286b
| Test Case | Status | Duration | Median Deviation | Log | Graph |
|---|