On Thu, 1 Jul 2010 22:19:56 -0400
Greg <g...@kinostudios.com> wrote:
> I don't see how the loop is relevant here, at least if the same benchmarking
> function is used for all the benchmarks you're doing, it should make a
> difference then since the overhead is the same.
It depends on what you're benchmarking. If the loop time is much
smaller than either the actual code time or the standard deviation in
the measurements, then it's just noise, and you can ignore it. If it's
on the order of the same size as the standard deviation, then it can
fool you into falsely concluding that there's no statistically
significant difference between two algorithms. Once it gets to be
around half the total benchmark time, your results are pretty much
worthless.
<mike
--
Mike Meyer <m...@mired.org> http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
