3 ms·
> By adding a benchmarking script to my continuous integration and archiving the results, it was easy for me to identify when my measurements changed. This ass
by styfle 3y ago
> By adding a benchmarking script to my continuous integration and archiving the results, it was easy for me to identify when my measurements changed.
This assumes CI runs on the same machine with same hardware every time, but most CI doesn’t do that.
- boesboes 3y agoAnd that the hardware is not overbooked. I found that my ci/cd runs would vary between 8 and 14 minutes (for a specific task in the pipeline, no cache involved) between reruns. And it seemed correlated to time of day. So pretty sure they had some contention there. Edit: and that was with all the same cpu’s reported to the os atleast