Recent discussions have illustrated the need for an up-to-date Haskell benchmark suite. The goal would be to package a number of representative benchmarks, written in Haskell, which users can run on their machine. Gathering (and publishing) performance numbers for these benchmarks on a number of different machines will hopefully help in guiding future development of both Haskell compilers and programs.

Recent discussions have illustrated the need for an up-to-date Haskell benchmark suite. The goal would be to package a number of representative benchmarks, written in Haskell, which users can run on their machine. Gathering (and publishing) performance numbers for these benchmarks on a number of different machines will hopefully help in guiding future development of both Haskell compilers and programs.

+

+

+

== News ==

+

+

July 29, 2010: The effort has been rebooted, now with the goal of obtaining a happy ending :-) All will be done in the open, see the repo on [http://github.com/itkovian/HaBench github]. See also the [http://www.haskell.org/pipermail/haskell-cafe/2010-June/079352.html mail thread] on the Haskell cafe list.

== Contributors ==

== Contributors ==

Revision as of 13:44, 29 July 2010

Contents

Haskell Benchmark Suite

Recent discussions have illustrated the need for an up-to-date Haskell benchmark suite. The goal would be to package a number of representative benchmarks, written in Haskell, which users can run on their machine. Gathering (and publishing) performance numbers for these benchmarks on a number of different machines will hopefully help in guiding future development of both Haskell compilers and programs.

News

July 29, 2010: The effort has been rebooted, now with the goal of obtaining a happy ending :-) All will be done in the open, see the repo on github. See also the mail thread on the Haskell cafe list.

Make sure code is pure Haskell as accepted by standard Haskell 98 (with addendums) or Haskell'

For each program include a correct version along with several buggy versions (perhaps even bugs that the programmer introduced while writing the benchmark) so that the programs can be used to test debuggers

For each program, include a clean, simple idiomatic version, and a hand-optimized fast version. This should hopefully give clues as to which programs have the most room for improvement, as well as what types of optimizations are helpful for a given program.

Notes

Random notes are below.

(JohnMeacham) Insert non-formatted text here pretty much every compiler has a mode similar to 'ghc --make', so just let the user specify an arbitrary command line for the compiler to use, like 'jhc -v -flint $< -o $@' or 'ghc --make $< -o $@'

(beelsebob) read Olaf's paper, he has evidence that speed problems in Haskell are usually because people are doing things too strictly