Hi Edd, On Fri, Feb 12, 2016 at 7:44 PM, Edd Barrett <[email protected]> wrote: > To be clear, what I called an "iteration" is one in-process run of an > entire benchmark.
Oops, sorry. The subject of this thread is "Experiences with Microbenchmarking". I naturally assumed that a microbenchmark is doing one simple thing not in a loop, in which case "iterations" is simply repeating that simple thing. If you have in mind benchmarks that are not as micro as that, then I stand corrected. A bientôt, Armin. _______________________________________________ Speed mailing list [email protected] https://mail.python.org/mailman/listinfo/speed
