lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]



Please, and thanks,

do keep such pages (or: this particular one?) with realistic & optimized performance figures. I'm trying to lobby for Lua (vs. Java & Python) but having less-than-optimal figures won't help. Not that beating the scores would, either, but at least it wouldn't be counted as a minus.

Imho, Lua should begin to rank as the "fourth" viable scripting language, alongside Perl, Python, and Ruby. More often than not, only these three are mentioned.

-ak


Mike Pall kirjoitti 25.7.2005 kello 14.56:

Hi,

ouli wrote:

    It is:
http://shootout.alioth.debian.org/benchmark.php? test=all&lang=lua&lang2=java&sort=fullcpu

According to the first bench mark, java is about 3x faster than lua.
I can not believe it. It is something wrong with the result?


Yes, there is.

1. Some of the Lua benchmarks there are not optimized.
I've hand-optimized a few of them (with sizeable gains), but
I've not had the time to clean them up and submit them, yet.

2. They've added quite a few new benchmarks recently and not
all of them have Lua equivalents, yet. This has a very negative
impact on the ranking, too.

3. Another problem is that they are using a Lua binary that has
the Lua core compiled as a shared library. Unfortunately this
comes with a sizeable performance loss on x86 CPUs. Since the
other languages are statically compiled, the comparison is
not completely fair.

Note: Yes, all of this is our (the Lua community's) fault.
The shootout maintainers just take whatever the respective
language community gives them. IMHO we should do something
about it. It's not good for Lua PR.

Could someone else please step up and take the lead for
fixing #1 and #2? I will gladly send my optimized versions
to anyone's mailbox. I have: ackermann, count-words, random,
spellcheck, tcp-echo, threads, threads-flow, word-frequency.
[All the others I optimized have been removed from the shootout.]

We already discussed #3 in March/April with no immediate
solution.

Bye,
     Mike