Personal tools

Benchmarks Game

From HaskellWiki

(Difference between revisions)
Jump to: navigation, search
(Port GLS page)
 
m (Submitting guide)
Line 9: Line 9:
 
* 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/hawiki/ShootoutEntry" in the header of the source code file in order to point other contributors to the Hawiki efforts.
+
* 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.
 
 
 
<haskell>
 
<haskell>
 
--
 
--
 
-- The Great Computer Language Shootout, http://shootout.alioth.debian.org/
 
-- The Great Computer Language Shootout, http://shootout.alioth.debian.org/
-- Haskell Shootout entries, http://haskell.org/hawiki/ShootoutEntry
+
-- Haskell Shootout entries, http://haskell.org/haskellwiki/Great_language_shootout
 
--
 
--
 
-- Simon Marlow
 
-- Simon Marlow

Revision as of 07:02, 4 October 2006

This is for entries to The Great Language Shootout.

Contents

1 Submitting guide

Suggested best practices for submiting an entry to the shootout 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.
  • 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.
--
-- 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
--

2 Results

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

3 Current benchmarks

4 Obsolete benchmarks

5 Future benchmarks