IN ORDER TO have benchmarks that all take approx. the same amount of time
WE WANT TO use larger problem sizes so that a single run of benchmark.normalRun takes ~2 seconds
discussion point: if we loop a benchmark over and over to increase its benchTime, does that impact the data we get? wouldnt it be better to just run once and leave it at that?
option:
zu schnelle benchmarks in JS künstlich aufblasen durch inner iterations ODER neue verified ergebnisse finden
Decision with @phischu:
leave "innerIterations" at one, accept that some microbenchmarks return 0 or 1 millis as benchTime
that way we dont "verfälschen" the ergebnisse of the benchmarks
IN ORDER TO have benchmarks that all take approx. the same amount of time WE WANT TO use larger problem sizes so that a single run of benchmark.normalRun takes ~2 seconds
discussion point: if we loop a benchmark over and over to increase its benchTime, does that impact the data we get? wouldnt it be better to just run once and leave it at that?
option: zu schnelle benchmarks in JS künstlich aufblasen durch inner iterations ODER neue verified ergebnisse finden