While criterion is really great, sometimes you do just want to measure timings. For that, you might want to give my package chronograph ( http://hackage.haskell.org/package/chronograph) a try. On Thu, Oct 23, 2014 at 10:40 PM, Carter Schonwald < carter.schonwald@gmail.com> wrote:
indeed. My suggestion is 1) use criterion, its awsome 2) run the criterion suite with a variety of optimization flag choices so you can understand how that changes performance 3) use criterion some more !
On Thu, Oct 23, 2014 at 10:35 AM, Daniel Trstenjak < daniel.trstenjak@gmail.com> wrote:
Hi Magnus,
Given that all I'm interested in is relative timings it might even be enough to do a rough comparison of two implementations too.
Optimizations - especially in Haskell - can change the runtime behaviour quite dramatically. So comparing the runtime performance without turned on optimizations is pretty much pointless.
Meaningful benchmarking is hard and adding any kind of uncertainty doesn't make it in any way easier.
Greetings, Daniel _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe