Wind Tunnel scenarios

[ThetaSinner]

This is an epic to cover Wind Tunnel scenarios to be created. It does not need to be complete and can be added to over time

Regression tests for single conductor performance

• [x] App installation speed
• [ ] First zome call to a newly installed app
  • [x] To trigger init that succeeds
  • [ ] holochain/holochain-performance-testing#3
• [ ] Post-init, zome call rate for
  • [x] Calling a no-op function (how quickly can we load, run, return)
  • [x] Database read get performance, (joining proof? get entry on your agent id, parent action of response is the joining proof)
  • [x] Database read chain query performance
  • [x] database read/write
  • [ ] Network read
• [ ] Local signal send rate
  • [x] Zome fn to emit 10k signals, then measure how long it took and how many signals the client was able to receive
• [ ] Validation performance with must_get_agent_activity
• [ ] Validation performance for simple structures with must_get_* other than agent_activity

Network performance

• [ ] Time to receive required validation receipts Just measure target redundancy
• [ ] Remote call send/receive rate: https://github.com/holochain/wind-tunnel/issues/50
• [ ] Remote signals send rate Very similar to remote calls for now
• [ ] Rate of saturation to reach target redundancy with publishing (fast push)
• [ ] Measure how much time is spent on rebuilding the time tree during gossip at the DHT size (history) grows - has to be over time, because that's the partition that should stabilise

Network performance with fault injection

• [ ] DHT sync performance with node volatility so that some nodes will come and go during the scenario

Countersigning performance

• [ ] Two-party countersigning
• [ ] Neutral neighborhood countersigning

Validation performance

• [ ] Validation rate (in ops/sec)

[ThetaSinner]

Best estimate for this issue is 3 weeks.