In the read-write asset benchmark it could check the number of times submitTransaction is called in preload-assets/delete-assets
davidkel opened this issue · 1 comments
davidkel commented
preload-assets and delete-assets are designed to create the exact number of assets requested no matter how matter how many workers are defined. This requires a specific benchmark configuration to use this such that all workers execute the transaction exactly once.
We can detect in the workload module that it is called exactly once and any further calls could either be ignored or fail with an error
It should also be possible to report an issue if not all workers run submitTransaction through the cleanupWorkloadModule()
call (but not tested this so assuming that it is possible)
davidkel commented
This has been added now