Personal tools

Benchmarks Game

From HaskellWiki

(Difference between revisions)
Jump to: navigation, search
(update)
m (Future benchmarks)
(22 intermediate revisions by 5 users not shown)
Line 1: Line 1:
This is for entries to [http://shootout.alioth.debian.org/index.php The Great Language Shootout].
+
This is for entries to [http://shootout.alioth.debian.org/index.php The Computer Language Benchmarks Game] (Formerly known as The Great Language Shootout). You can see [http://shootout.alioth.debian.org/u64q/benchmark.php?test=all&lang=all the current Haskell results].
  +
  +
[[Image:Chartvs.png|center|frame|Haskell entries compared to C on the quad core, Feb 2009]]
  +
  +
== Parallel implementations ==
  +
New implementations written for parallelism. You should almost certainly
  +
be working on these only:
  +
  +
* [[/Parallel]]
   
 
== Submitting guide ==
 
== Submitting guide ==
   
Now that GHC 6.6 is available, please use it! This gives us the option
+
Now that GHC 6.10 is installed on the Benchmarks Game servers, please make full use of it! There is an immediate need for a complete revamp of all the entries to fix and optimise them for this version of GHC. Please pick a program and contribute!
of using:
+
* Data.ByteString
+
GHC 6.10 gave us the option of
* Text.Regex.{PCRE,...}
+
* parallel garbage collector
* bang patterns
+
  +
GHC 6.8 gave us the option of
  +
* `par`
  +
* SMP runtime
  +
* new regex libs
  +
* lots of other stuff
  +
  +
GHC 6.6 gave the option of using:
  +
* [http://haskell.org/ghc/docs/latest/html/libraries/base/Data-ByteString.html Data.ByteString]
  +
* [http://haskell.org/ghc/docs/latest/html/libraries/regex-posix/Text-Regex-Posix-ByteString.html Text.Regex.*]
  +
* [http://www.haskell.org/ghc/docs/latest/html/users_guide/sec-bang-patterns.html bang patterns]
 
which should greatly improve clarity and brevity. Line count is not
 
which should greatly improve clarity and brevity. Line count is not
 
significant now (code is gzipped to determine size), so aim for maximum
 
significant now (code is gzipped to determine size), so aim for maximum
 
clarity.
 
clarity.
   
Suggested best practices for submiting an entry to the shootout include:
+
Suggested best practices for submitting an entry to the Benchmarks Game include:
   
* Posting the proposed code to the community to allow for a best of breed entry. Proposed code is here on the wiki and often in the haskell-cafe mailing list. This has already helped improve the submitted code.
+
* Posting the proposed code to the community to allow for a best of breed entry. Proposed code is here on the wiki and often in the Haskell-cafe mailing list. This has already helped improve the submitted code.
   
 
* Provide complete performance measurements against the current best entry.
 
* Provide complete performance measurements against the current best entry.
Line 20: Line 20:
 
* Creating clean, functional-style code or fast, imperative-style code. There are multiple versions ("GHC", "GHC#2", "GHC#3", "GHC#4") of GHC codes on many of the benchmarks with no clear rational for the different versions. It'd be better to have entries for "GHC" be clean, short, functional code and entries for "GHC-#2" be fastest, probably-ugliest code.
 
* Creating clean, functional-style code or fast, imperative-style code. There are multiple versions ("GHC", "GHC#2", "GHC#3", "GHC#4") of GHC codes on many of the benchmarks with no clear rational for the different versions. It'd be better to have entries for "GHC" be clean, short, functional code and entries for "GHC-#2" be fastest, probably-ugliest code.
   
* Include a reference to "http://haskell.org/haskellwiki/Great_language_shootout" in the header of the source code file in order to point other contributors to the Hawiki efforts.
+
* When you submit via the trac system, record in the wiki section for that entry a link to the submission.
  +
  +
* Check for gzip file size before you submit -- lots of points to be had there.
  +
  +
* Try different compile options and the other ideas on the [[Performance/GHC]] page.
 
 
 
<haskell>
 
<haskell>
Line 36: Line 36:
 
Haskell results for all benchmarks: [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=ghc&lang2=ghc Gentoo/P4] and [http://shootout.alioth.debian.org/benchmark.php?test=all&lang=ghc&lang2=ghc Debian/AMD Sempron]
 
Haskell results for all benchmarks: [http://shootout.alioth.debian.org/gp4/benchmark.php?test=all&lang=ghc&lang2=ghc Gentoo/P4] and [http://shootout.alioth.debian.org/benchmark.php?test=all&lang=ghc&lang2=ghc Debian/AMD Sempron]
   
== Current benchmarks ==
+
== Old Single Core Benchmarks ==
   
 
* [[Shootout/Binary trees]] - for [http://shootout.alioth.debian.org/gp4/benchmark.php?test=binarytrees&lang=all Gentoo/P4], [http://shootout.alioth.debian.org/benchmark.php?test=binarytrees&lang=all Debian/AMD Sempron]
 
* [[Shootout/Binary trees]] - for [http://shootout.alioth.debian.org/gp4/benchmark.php?test=binarytrees&lang=all Gentoo/P4], [http://shootout.alioth.debian.org/benchmark.php?test=binarytrees&lang=all Debian/AMD Sempron]
   
* [[Shootout/Cheap concurrency]] - for [http://shootout.alioth.debian.org/gp4/benchmark.php?test=message&lang=all Gentoo/P4], [http://shootout.alioth.debian.org/benchmark.php?test=message&lang=all Debian/AMD Sempron]
+
* [[Shootout/Cheap concurrency]] - for [http://shootout.alioth.debian.org/gp4/benchmark.php?test=thread-x&lang=all Gentoo/P4], [http://shootout.alioth.debian.org/benchmark.php?test=thread-x&lang=all Debian/AMD Sempron]
  +
  +
* [[Shootout/Thread ring]] - for [http://shootout.alioth.debian.org/gp4/benchmark.php?test=thread-ring&lang=all Gentoo/P4], [http://shootout.alioth.debian.org/benchmark.php?test=thread-ring&lang=all Debian/AMD Sempron]
   
 
* [[Shootout/Chameneos]] - for [http://shootout.alioth.debian.org/gp4/benchmark.php?test=chameneos&lang=all Gentoo/P4], [http://shootout.alioth.debian.org/benchmark.php?test=chameneos&lang=all Debian/AMD Sempron]
 
* [[Shootout/Chameneos]] - for [http://shootout.alioth.debian.org/gp4/benchmark.php?test=chameneos&lang=all Gentoo/P4], [http://shootout.alioth.debian.org/benchmark.php?test=chameneos&lang=all Debian/AMD Sempron]
Line 73: Line 73:
   
 
* [[Shootout/SumFile]] - for [http://shootout.alioth.debian.org/gp4/benchmark.php?test=sumcol&lang=all Gentoo/P4], [http://shootout.alioth.debian.org/benchmark.php?test=sumcol&lang=all Debian/AMD Sempron]
 
* [[Shootout/SumFile]] - for [http://shootout.alioth.debian.org/gp4/benchmark.php?test=sumcol&lang=all Gentoo/P4], [http://shootout.alioth.debian.org/benchmark.php?test=sumcol&lang=all Debian/AMD Sempron]
  +
  +
== Todo ==
  +
  +
The current benchmarks can highlight weak spots in libraries and
  +
compilers that need improving. Some things noticed included:
  +
  +
* hashtable performance is poor. A simple binding to a basic C hashtable would be very useful
  +
* it would be nice to have tre regexes in the core libs (instead of POSIX ones)
  +
  +
''Why tre regexes? The libtre code is buggy, though if the shootout avoids the bugs then I guess one might want to use it. Would libpcre be a better choice?''--[[User:ChrisKuklewicz|ChrisKuklewicz]] 00:21, 24 February 2009 (UTC)
   
 
== Obsolete benchmarks ==
 
== Obsolete benchmarks ==
Line 87: Line 97:
   
 
[[Category:Contests]]
 
[[Category:Contests]]
  +
[[Category:Code]]

Revision as of 22:47, 22 January 2012

This is for entries to The Computer Language Benchmarks Game (Formerly known as The Great Language Shootout). You can see the current Haskell results.

(thumbnail)
Haskell entries compared to C on the quad core, Feb 2009

Contents

1 Parallel implementations

New implementations written for parallelism. You should almost certainly be working on these only:

2 Submitting guide

Now that GHC 6.10 is installed on the Benchmarks Game servers, please make full use of it! There is an immediate need for a complete revamp of all the entries to fix and optimise them for this version of GHC. Please pick a program and contribute!

GHC 6.10 gave us the option of

  • parallel garbage collector

GHC 6.8 gave us the option of

  • `par`
  • SMP runtime
  • new regex libs
  • lots of other stuff

GHC 6.6 gave the option of using:

which should greatly improve clarity and brevity. Line count is not significant now (code is gzipped to determine size), so aim for maximum clarity.

Suggested best practices for submitting an entry to the Benchmarks Game include:

  • Posting the proposed code to the community to allow for a best of breed entry. Proposed code is here on the wiki and often in the Haskell-cafe mailing list. This has already helped improve the submitted code.
  • Provide complete performance measurements against the current best entry.
  • Creating clean, functional-style code or fast, imperative-style code. There are multiple versions ("GHC", "GHC#2", "GHC#3", "GHC#4") of GHC codes on many of the benchmarks with no clear rational for the different versions. It'd be better to have entries for "GHC" be clean, short, functional code and entries for "GHC-#2" be fastest, probably-ugliest code.
  • When you submit via the trac system, record in the wiki section for that entry a link to the submission.
  • Check for gzip file size before you submit -- lots of points to be had there.
  • Try different compile options and the other ideas on the Performance/GHC page.
--
-- The Great Computer Language Shootout, http://shootout.alioth.debian.org/
-- Haskell Shootout entries, http://haskell.org/haskellwiki/Great_language_shootout
-- 
-- Simon Marlow
-- Shortened by Don Stewart
--

3 Results

Haskell results for all benchmarks: Gentoo/P4 and Debian/AMD Sempron

4 Old Single Core Benchmarks

5 Todo

The current benchmarks can highlight weak spots in libraries and compilers that need improving. Some things noticed included:

  • hashtable performance is poor. A simple binding to a basic C hashtable would be very useful
  • it would be nice to have tre regexes in the core libs (instead of POSIX ones)

Why tre regexes? The libtre code is buggy, though if the shootout avoids the bugs then I guess one might want to use it. Would libpcre be a better choice?--ChrisKuklewicz 00:21, 24 February 2009 (UTC)

6 Obsolete benchmarks

7 Future benchmarks