Definition of Done:
We can generate ~1024 transactions in several minutes.
Currently the bottleneck for the load generation is the proof generation step, that should be executed for each transaction before sending. It takes from 30s to 2min, depending on a transaction kind. We need to run several generators in parallel to generate enough transaction, but even so, there are resource limitations, as each generator needs 16 CPUs (fewer are possible, but with the price of doubling proof time).
There are two options:
Pre-generate all transactions and store them, then for each run load them and send to the chain
Generate single transaction template with a proof, and then update its nonce before signing/sending.
Definition of Done: We can generate ~1024 transactions in several minutes.
Currently the bottleneck for the load generation is the proof generation step, that should be executed for each transaction before sending. It takes from 30s to 2min, depending on a transaction kind. We need to run several generators in parallel to generate enough transaction, but even so, there are resource limitations, as each generator needs 16 CPUs (fewer are possible, but with the price of doubling proof time).
There are two options: