search for: benchmark_repetit

...hmark executable multiple times before moving to the next > executable; but given that we don't have that today I'm just not using the > multisample option personally as it's not better than submitting multiple > benchmarking jobs anyway... > I think its better to use "benchmark_repetitions=n" option of google benchmark than "--exec-multisample=n" as in multisample data initialization will also be executed again along with the main kernel but benchmark_repetitions option runs only the main kernel n times. The repeated execution of data inititalization will only add...

Not going into all the detail, but from my side the big question is whether the benchmarks inner loop is small/fine grained enough that stabilization with google benchmark doesn't lead to dozens of seconds benchmark runtimes. Given that you typically see thousandsd or millions of invocations for small functions... > On May 29, 2018, at 2:06 PM, Michael Kruse via llvm-dev <llvm-dev at