search

EOS-Nation / bpvalidate

Tools to validate BPs have set up their public configuration correctly
MIT License
20 stars 19 forks source link

Test time to actually perform a transaction #51

Open matthewdarwin opened 5 years ago

matthewdarwin commented 5 years ago

CPU speed on API nodes really matters.

some test results with delegatebw 2.7GHz AWS (r4.x2large) node - ~3100us 4.4GHz bare metal node - ~1900us

matthewdarwin commented 5 years ago

https://github.com/EOSIO/eos/pull/8023

matthewdarwin commented 5 years ago

From Eric:

What would be a good add is to instead of testing the uptime - which in my opinion is bad because it puts negative pressure to have high performant peering and instead go for amount of peers, and also to create choking points...

Would be to test the CPU of the peering network. Meaning connect 2 processes, push a transaction through #1 and see if it appears in the queue on #2

The transaction to push can start with the eos mechanics test, and then have other tests on the same contract which consume higher and higher CPU. This way the peering network can be tested. And instead of relying on always having open peers - it would actually provide value.

Both of them can be connected all the time, will only consume 2 peers, meaning there should be ample opportunity to test if given a couple of days for each node.