We solve that partially by running the base state and the delta version through concurrently. This way most types of impact will impact both at the same time. This gives us the relative delta between versions.
Other than that, just like always, run benchmark on a stable dedicated set of hardware.
Yes. Or for a sufficiently long duration. Some things like allocation rate and significantly worse performance are obvious and can be seen in shorter runs.
I can't say. It's definitely not the same as running on bare metal. Then again, any benchmark in a test environment is just an approximation of the real thing. To see how anything will act in the real environment, you have to run it there.
In our use case we wanted a way to quickly and easily set up benchmarks that would allow us to compare our software to our competitors under the same conditions. Given that Benchi can run the same benchmark scenario for different tools, the results are comparable with each other. We also run all benchmarks on an empty AWS EC2 instance, to minimize any other factors. But does that mean that the collected results show the absolute limit of what the tools can handle? Probably not. Under different conditions, results can change, but that's just the nature of benchmarks.
Other than that, just like always, run benchmark on a stable dedicated set of hardware.
In our use case we wanted a way to quickly and easily set up benchmarks that would allow us to compare our software to our competitors under the same conditions. Given that Benchi can run the same benchmark scenario for different tools, the results are comparable with each other. We also run all benchmarks on an empty AWS EC2 instance, to minimize any other factors. But does that mean that the collected results show the absolute limit of what the tools can handle? Probably not. Under different conditions, results can change, but that's just the nature of benchmarks.