In zkapp scheduler when zkapps are deployed, it's done before sending of transactions in one burst.
In order to make this function more reliably, implement pause between zkapp deployments (in the same way it's being done for zkapp transactions), in such a way that number of zkapps deployed per second doesn't exceed tps.
E.g. if 54 zkapps are to be deployed, tps = 0.2 and experiment duration is 20 minutes, it's expected that for the first three minutes exactly 18 zkapp deployments per minute will be sent out. And starting from fourth minute zkapp transactions will be sent. So that 54 zkapp deployment transactions and 306 zkapp transactions will be sent out.
Run always ends after duration minutes pass, even if not all zkapps are deployed.
mrmr1993
commented
2 weeks ago
In zkapp scheduler when zkapps are deployed, it's done before sending of transactions in one burst.
In order to make this function more reliably, implement pause between zkapp deployments (in the same way it's being done for zkapp transactions), in such a way that number of zkapps deployed per second doesn't exceed
tps.E.g. if 54 zkapps are to be deployed,
tps = 0.2and experiment duration is 20 minutes, it's expected that for the first three minutes exactly 18 zkapp deployments per minute will be sent out. And starting from fourth minute zkapp transactions will be sent. So that 54 zkapp deployment transactions and 306 zkapp transactions will be sent out.Run always ends after
durationminutes pass, even if not all zkapps are deployed.