automated test for automatic restalking feature

[SurfingNerd]

Testing for: DMDcoin/diamond-contracts-core#43

• including the impact of small delegate stakes on validators.

• figure out if the blockchain will be able to create a block within 1 minute.

• plot a graph of the impacts

• Network generation

  • with 25 Nodes (it could be only 1 Node, since it "should" scale lineary) but with 25 nodes wrong expectations are addressed. for a local test, 7 Nodes should do fine, so we do not have a overload of the local machine.
  • Epoch Length should be long enough so the long lasting block can be created within 1 epoch, and short enough
    to get results within a convinient timeframe. Since the target block creation timeframe is 1 minute, 10 Minutes should be a good value, that gives enough time to do the key generation.
  • network needs to be generated with only 1 validator - the rest of the validators need to be filled, so they become regular validators that are possible to be staked on, instead of MOC Validators.

• maybe develop with the capability to test it both on a remote and a localnet. (current ostacle: localnet vs remotenet as config param ? #97) (no, we do not need remotenet support)

• Increase the number of delegators each block by a configurable step (100 ?) for each epoch.

• figure out the block that does the reward call, and measure the time consumed for creating the block.

• write out each created epoch switch as a CSV line.

• create a plot (libre office calc?) to visualize the result.

• highlight the breakpoint of the target time of 1 Minute, so we know the hard minimum boundary for delegator min stake.

• append the data and visualisation in this issue.

[SurfingNerd]

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.

[SurfingNerd]

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.

[SurfingNerd]

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

[SurfingNerd]

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

[SurfingNerd]

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