mempool/lanes: Validate MVP implementation on 200-nodes testnet · Issue #4168 · cometbft/cometbft · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the MVP implementation is finished in the feature branch, and before merging it into the main branch, we need to validate in our usual 200-nodes testnet that the performance of the new code is not degraded with respect to the main branch.
The text was updated successfully, but these errors were encountered:
In all experiments we injected a transaction load of 400 tx/s. Until v1.0.0-alpha2, we used this load as the saturation point of the system. In main and feature/mempool-qos, it seems that the saturation point could now be higher, but more tests are needed to corroborate that.
Results
main and feature/mempool-qos not only do not degrade the general performance compared against v1.0.0-alpha2 but they also improve on almost all metrics.
The metrics of feature/mempool-qos are overall equivalent to those of main. This was expected because in this test scenario system resources never reached their limits, which is when we would expect Lanes to kick in and show better results than main.
Therefore, the implementation in feature/mempool-qos has passed the test.
Metrics
v1.0.0-alpha2 (e42f62b68)
main (1323b1cdd)
feature/mempool-qos (fa9ae0c44)
number of txs in chain
rate of tx processing (txs/min)
rate of block creation (blocks/min)
block size
number of blocks
average mempool size
maximum mempool size
number of rounds
number of peers
CPU load
memory usage
hvanz
changed the title
mempool/lanes: Validate MVP implementation on 200 nodes
mempool/lanes: Validate MVP implementation on 200-nodes testnet
Sep 24, 2024
Uh oh!
There was an error while loading. Please reload this page.
When the MVP implementation is finished in the feature branch, and before merging it into the main branch, we need to validate in our usual 200-nodes testnet that the performance of the new code is not degraded with respect to the main branch.
The text was updated successfully, but these errors were encountered: