[Haskell-cafe] Progress on shootout entries

Sebastian Sylvan sebastian.sylvan at gmail.com
Tue Jan 3 17:03:37 EST 2006


On 1/3/06, Sebastian Sylvan <sebastian.sylvan at gmail.com> wrote:
> On 1/3/06, Chris Kuklewicz <haskell at list.mightyreason.com> wrote:
> > Hello,
> >
> >   Where there were no entries to the
> > http://shootout.alioth.debian.org/benchmark.php?test=chameneos&lang=all
> > benchmark, there are now two.  The one by Josh Goldfoot is already
> > posted, the one Einar Karttunen and I optimized has been submitted and
> > will run faster/smaller.  Our code is at
> > http://haskell.org/hawiki/ChameneosEntry
> >
> >   Now for improving the fasta benchmark,
> > http://shootout.alioth.debian.org/benchmark.php?test=fasta&lang=all ,
> > which currently has a space leak in the Haskell entry.
> >
> >   A non-leaking version which has been optimized to run 3.5 times faster
> > is now up at http://haskell.org/hawiki/FastaEntra (ooops..my spelling
> > mistake).
> >
> >   It could still be made to run about 3 times faster, if the other
> > languages are any guide.  Anyone want to help polish this one?
> >
> >  Also, two other existing entries have space leaks, as can be seen at
> > http://shootout.alioth.debian.org/benchmark.php?test=all&lang=ghc&lang2=ghc
> >
> >  And finially, the haskel entry for
> > http://shootout.alioth.debian.org/benchmark.php?test=fannkuch&lang=all
> >  is currently the *slowest* entry out of 28 languages.  It is 813x
> > slower than the c-code, 500x slower than OCaml.  Should be easy to make
> > it faster...
>
> While the implementation is far from "nice" it still finishes with N=9
> (which, AFAICT, is what the benchmark is run with) in a fraction of a
> second on my machine (and not anywhere near 51s as in the
> benchmark)... I have a 2.6 Ghz P4...
>
> I was going to rewrite it using mutable STArrays for a pure version
> that's still fast but i sorta feel like I lost the motivation now that
> it turns out the existing implementation, though ugly, performs
> somewhat okay...

Hmm.. This may be due to laziness. Since it's only supposed to print
out the first 30 lines it won't compute the full n! values...


/S


--
Sebastian Sylvan
+46(0)736-818655
UIN: 44640862


More information about the Haskell-Cafe mailing list