automated test for automatic restalking feature about honey-badger-testing HOT 5 CLOSED

restalking tests have been extended by also filling the pots and csv outputing the total stake in PR #103,
this total stake value can be used to verify the correct behaviour of the restaking feature.

from honey-badger-testing.

the first performance tests has shown that the restake feature does not have a serious negativ performance impact on the epoch end.
But we did not have Pots defined in those tests.
i am working on rerunning the tests after we also got filled pots.

from honey-badger-testing.

be careful with the settings you want to run on the test hardware.
8 Core AMD EPYC 7282 could not handle a test with 25 nodes.

here is an example where the hardware VM could not handle the load and drops out nodes because of the early epoch end feature.
The system was never able to scale up to 25 nodes, what would mark the beginning of the test,, and the early epoch end feature even started to throw out nodes at block 224.

lscpu.txt
main.log
starttime.txt
versions.txt

from honey-badger-testing.

removed task "Check for exisint diamond DB Implemetations to visualize stake changes in grafana. " because it is a separate task now: #98

from honey-badger-testing.

here is a test with 10 nodes, and 2000 delegators.
a negative performance impact could not be measured.

block_creation_result.csv
main.log
starttime.txt
versions.txt

from honey-badger-testing.