Re: Language Shootout explanation?



On Aug 11, 11:27 am, Lars Rune Nøstdal <larsnost...@xxxxxxxxx> wrote:
On Aug 11, 6:46 pm, jrwats <jrw...@xxxxxxxxx> wrote:

Here is a link to the comparison between C++ and Lisp.  Lisp doesn't
fair too bad for most things but then blows up in the k-nucleotide
test (15x slower than C++).  I took a 10 minute look at the source
code and couldn't see any glaring problems and was wondering if anyone
had any explanation for this?

http://shootout.alioth.debian.org/u64q/benchmark.php?test=all〈=sb...

Not sure if it's relevant for this particular case, but they should
really upgrade to a newer SBCL (again) as there has been some nice
improvements wrt. floating point stuff there recently.


There doesn't seem to be a 1.0.30 binary available for Linux X86 or
Linux AMD64

http://sbcl.sourceforge.net/platform-table.html
.



Relevant Pages

  • Re: Language Shootout explanation?
    ... fair too bad for most things but then blows up in the k-nucleotide ... test (15x slower than C++). ... There doesn't seem to be a 1.0.30 binary available for Linux X86 or ... They'll need thread-support and thus need to compile from source ...
    (comp.lang.lisp)
  • Re: Language Shootout explanation?
    ... fair too bad for most things but then blows up in the k-nucleotide ... test (15x slower than C++). ... For example READ-DATA is a bottle-neck, there are ways to make it much ...
    (comp.lang.lisp)
  • Re: Language Shootout explanation?
    ... fair too bad for most things but then blows up in the k-nucleotide ... test (15x slower than C++). ... improvements wrt. floating point stuff there recently. ...
    (comp.lang.lisp)
  • Re: Language Shootout explanation?
    ... fair too bad for most things but then blows up in the k-nucleotide ... test (15x slower than C++). ... They'll need thread-support and thus need to compile from source ...
    (comp.lang.lisp)
  • Re: Language Shootout explanation?
    ... fair too bad for most things but then blows up in the k-nucleotide ... test (15x slower than C++). ... code and couldn't see any glaring problems and was wondering if anyone ... had any explanation for this? ...
    (comp.lang.lisp)