One cannot set the number of iterations for the benchmark, since it is a constant member variable of benchmark::State class (set in its constructor). When run from a command line, Google benchmark allows to set the number of iterations via --benchmark_iterations command line option. However, such an option is not available on the online quick-bench.com instance.
Is there any way how to set the number of iterations for benchmarks on quick-bench.com? Would it be possible to add some front-end option for this functionality and pass the number to the back end?
I'm asking since sometimes, I experience timeouts, which I suspect are caused by high load of AWS machines. Maybe, setting a smaller number of iterations would help.
One cannot set the number of iterations for the benchmark, since it is a constant member variable of
benchmark::Stateclass (set in its constructor). When run from a command line, Google benchmark allows to set the number of iterations via--benchmark_iterationscommand line option. However, such an option is not available on the online quick-bench.com instance.Is there any way how to set the number of iterations for benchmarks on quick-bench.com? Would it be possible to add some front-end option for this functionality and pass the number to the back end?
I'm asking since sometimes, I experience timeouts, which I suspect are caused by high load of AWS machines. Maybe, setting a smaller number of iterations would help.