Zombienet performance tests

[sandreim]

This will enable us determine the current performance characteristics of nodes and test networks and prevent performance regressions. The goal here is to ensure the following expectations are met for a given series of scenarios with different configuration parameters and scale:

• disputes concluded are always faster than initiated
• dispute conclusion throughput is > 2/s
• parachain block-time is a tight ~12s
• parachain blocks never take longer than 30s
• parachain wasm compilation < 10s
• approval checking finality lag < 3 blocks
• TBD

This is a list of the network configuration parameters driving the performance numbers and scale of the tests. We are not aiming to do stress testing, so we will constrain the values to some reasonable numbers. This is a good starting point and we might need to adjust.

• variable PoV size 4-16MB PoV
• 3s execution time
• scale up to 1000 validators
• 8-16MB Code Size
• up to 20 approvals needed
• 25-100kb of HRMP messages per block
• code upgrade once every 24hrs
• up to 100 parachains

Tests will assume the reference hardware is being used for all validators (including malus validators): 8 CPUs, 16GB Ram, 500Mbps up/down.

Tasks:

• [ ] Low scale version of all tests (max 4 validators)
  • [x] parachain wasm compilation < 10s
  • [ ] parachain block-time is a tight ~12s
  • [ ] parachain blocks never take longer than 30s
  • [x] approval checking finality lag < 3 blocks
  • [x] dispute conclusion throughput is > 2/s
  • [x] disputes concluded are always faster than initiated
  • [ ] transactions per second
• [ ] Scale up to 100 validators
• [ ] TBD