As a Caliper user, I would like to be able to discount initial/final transactions from my collected statistics
It is useful to be able to discount initial/final transactions from both transaction and resource statistics. This is because:
- certain code types need a "warm up phase"
- as transaction queues build/drain, the performance characteristics change
It should be possible to specify an explicit option within the benchmark file such that it is possible to customise the window within which measurements are taken during a round.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.