The caching of benchmark results can be very helpful or frustrating during development, depending on what you're doing. This story is to add an option() to disable the caching when desired. At a minimum this means not reading from any cache; it may mean not writing to one or actively wiping it between runs. To keep consistency, the default should probably be to continue the current caching behavior; this option would be to opt-out, not opt-in. The name should be something like arrowbench.cache_benchmark_results or similar.
The caching of benchmark results can be very helpful or frustrating during development, depending on what you're doing. This story is to add an
option()to disable the caching when desired. At a minimum this means not reading from any cache; it may mean not writing to one or actively wiping it between runs. To keep consistency, the default should probably be to continue the current caching behavior; this option would be to opt-out, not opt-in. The name should be something likearrowbench.cache_benchmark_resultsor similar.