Ok, I guess we are closing in on making a 7.6 release. This is the current shootout benchmark status against some other similar languages.
Java PHP Perl Pike Python Ruby TCL 1: 3.60 12.56 4.91 0.63 4.59 9.40 Failed (ackermann) 2: 1.68 11.91 4.76 1.40 3.06 8.61 15.19 (ary3) 3: 2.89 12.13 6.37 1.55 4.46 7.00 11.63 (fibo) 4: 7.94 5.98 5.72 4.69 3.83 18.67 7.75 (hash) 5: 1.48 8.62 3.47 1.09 2.48 6.30 8.33 (heapsort) 6: 5.46 Missing 3.19 2.70 4.73 2.44 27.44 (lists) 7: 2.17 Missing 5.90 1.83 4.76 3.38 Missing (methcall) 8: 7.27 Failed 17.91 0.91 13.95 35.87 34.39 (nestedloop) 9: 3.61 Missing 12.99 3.37 5.99 6.16 Missing (objinst) 10: 1.81 5.80 2.23 1.43 2.92 5.93 5.87 (random) 11: 6.57 Failed 12.19 4.52 9.16 18.39 50.59 (sieve) 12: 3.12 4.50 2.32 1.90 4.21 3.80 7.02 (strcat)
I have altered the lists test to use arrays, as intended, and not strings (which lowers the time from 13.1 seconds to 2.7). The languages are gcj/gij 2.3 (the compilation time is included), PHP 4.3.4RC3, Perl 5.8.2, Pike 7.5.13, Python 2.3.2, Ruby 1.8.0 and TCL 8.3. In the year since last benchmark we can see some significant improvements in the Python performance, almost 50% in many tests (though it is still not possible to run ackermann(3,9) without running out of stack). Perl is also doing good with about 25% better since 5.8.0. From test 8 we can see that multipass strength reduction isn't implemented in any other language. On the whole it looks like Perl and Python is now only twice as slow as Pike, so we better watch out...
Det vore kanske relevant med javasiffror utan kompileringstiden också, och likadant för andra språk där man kan välja att göra hela eller delar av kompileringen i förväg.
/ Niels Möller (igelkottsräddare)
Previous text:
2003-12-03 02:15: Subject: More benchmarks
Ok, I guess we are closing in on making a 7.6 release. This is the current shootout benchmark status against some other similar languages.
Java PHP Perl Pike Python Ruby TCL
1: 3.60 12.56 4.91 0.63 4.59 9.40 Failed (ackermann) 2: 1.68 11.91 4.76 1.40 3.06 8.61 15.19 (ary3) 3: 2.89 12.13 6.37 1.55 4.46 7.00 11.63 (fibo) 4: 7.94 5.98 5.72 4.69 3.83 18.67 7.75 (hash) 5: 1.48 8.62 3.47 1.09 2.48 6.30 8.33 (heapsort) 6: 5.46 Missing 3.19 2.70 4.73 2.44 27.44 (lists) 7: 2.17 Missing 5.90 1.83 4.76 3.38 Missing (methcall) 8: 7.27 Failed 17.91 0.91 13.95 35.87 34.39 (nestedloop) 9: 3.61 Missing 12.99 3.37 5.99 6.16 Missing (objinst) 10: 1.81 5.80 2.23 1.43 2.92 5.93 5.87 (random) 11: 6.57 Failed 12.19 4.52 9.16 18.39 50.59 (sieve) 12: 3.12 4.50 2.32 1.90 4.21 3.80 7.02 (strcat)
I have altered the lists test to use arrays, as intended, and not strings (which lowers the time from 13.1 seconds to 2.7). The languages are gcj/gij 2.3 (the compilation time is included), PHP 4.3.4RC3, Perl 5.8.2, Pike 7.5.13, Python 2.3.2, Ruby 1.8.0 and TCL 8.3. In the year since last benchmark we can see some significant improvements in the Python performance, almost 50% in many tests (though it is still not possible to run ackermann(3,9) without running out of stack). Perl is also doing good with about 25% better since 5.8.0. From test 8 we can see that multipass strength reduction isn't implemented in any other language. On the whole it looks like Perl and Python is now only twice as slow as Pike, so we better watch out...
/ Martin Nilsson (saturator)
Java compilation time is aprox. 0.01 s. The measurement noise is somewhere around +/- 0.03.
/ Martin Nilsson (saturator)
Previous text:
2003-12-03 09:42: Subject: More benchmarks
Det vore kanske relevant med javasiffror utan kompileringstiden också, och likadant för andra språk där man kan välja att göra hela eller delar av kompileringen i förväg.
/ Niels Möller (igelkottsräddare)
As for java, gcj isn't exactly good. If it's on Linux (x86 at least), using IBM's JRE would probably be a better choice.
/ David Hedbor
Previous text:
2003-12-03 02:15: Subject: More benchmarks
Ok, I guess we are closing in on making a 7.6 release. This is the current shootout benchmark status against some other similar languages.
Java PHP Perl Pike Python Ruby TCL
1: 3.60 12.56 4.91 0.63 4.59 9.40 Failed (ackermann) 2: 1.68 11.91 4.76 1.40 3.06 8.61 15.19 (ary3) 3: 2.89 12.13 6.37 1.55 4.46 7.00 11.63 (fibo) 4: 7.94 5.98 5.72 4.69 3.83 18.67 7.75 (hash) 5: 1.48 8.62 3.47 1.09 2.48 6.30 8.33 (heapsort) 6: 5.46 Missing 3.19 2.70 4.73 2.44 27.44 (lists) 7: 2.17 Missing 5.90 1.83 4.76 3.38 Missing (methcall) 8: 7.27 Failed 17.91 0.91 13.95 35.87 34.39 (nestedloop) 9: 3.61 Missing 12.99 3.37 5.99 6.16 Missing (objinst) 10: 1.81 5.80 2.23 1.43 2.92 5.93 5.87 (random) 11: 6.57 Failed 12.19 4.52 9.16 18.39 50.59 (sieve) 12: 3.12 4.50 2.32 1.90 4.21 3.80 7.02 (strcat)
I have altered the lists test to use arrays, as intended, and not strings (which lowers the time from 13.1 seconds to 2.7). The languages are gcj/gij 2.3 (the compilation time is included), PHP 4.3.4RC3, Perl 5.8.2, Pike 7.5.13, Python 2.3.2, Ruby 1.8.0 and TCL 8.3. In the year since last benchmark we can see some significant improvements in the Python performance, almost 50% in many tests (though it is still not possible to run ackermann(3,9) without running out of stack). Perl is also doing good with about 25% better since 5.8.0. From test 8 we can see that multipass strength reduction isn't implemented in any other language. On the whole it looks like Perl and Python is now only twice as slow as Pike, so we better watch out...
/ Martin Nilsson (saturator)
then you belong to the group which results from: everyone - almost_everyone; which is: almost_noone.
greetings, martin.
Add me to the almost_noone group, then. I think Java programmers tend to use Sun's JVM when developing. It's the reference implementation...
/ Johan Schön (Firefruit)
Previous text:
2003-12-03 19:34: Subject: Re: More benchmarks
then you belong to the group which results from: everyone - almost_everyone; which is: almost_noone.
greetings, martin.
/ Brevbäraren
The Sun version is only for x86, so the tendency does not include programmers with real computers. Blackdown is based on the same source, so it's a pretty good reference too.
/ Marcus Comstedt (ACROSS) (Hail Ilpalazzo!)
Previous text:
2003-12-03 19:38: Subject: Re: More benchmarks
Add me to the almost_noone group, then. I think Java programmers tend to use Sun's JVM when developing. It's the reference implementation...
/ Johan Schön (Firefruit)
I have to side with David here. I, and everyone I know (almost), only use the one from Sun, a rare few of them sometimes use the one from IBM.
Outside of myself, I know of only one person who actually knows what blackdown is.
Just my 0.02c
/ Peter Lundqvist (disjunkt)
Previous text:
2003-12-03 19:34: Subject: Re: More benchmarks
then you belong to the group which results from: everyone - almost_everyone; which is: almost_noone.
greetings, martin.
/ Brevbäraren
Blackdown is the Sun source. It's recommended in various Linux packages depending on Java, so I see it almost everywhere I have to administer som Linux machine with Java projects on.
/ Peter Bortas
Previous text:
2003-12-03 19:41: Subject: Re: More benchmarks
I have to side with David here. I, and everyone I know (almost), only use the one from Sun, a rare few of them sometimes use the one from IBM.
Outside of myself, I know of only one person who actually knows what blackdown is.
Just my 0.02c
/ Peter Lundqvist (disjunkt)
Blackdown is the Sun source.
Yes, but it is not a Sun release - is it?
/ Peter Lundqvist (disjunkt)
Previous text:
2003-12-03 20:29: Subject: Re: More benchmarks
Blackdown is the Sun source. It's recommended in various Linux packages depending on Java, so I see it almost everywhere I have to administer som Linux machine with Java projects on.
/ Peter Bortas
pike-devel@lists.lysator.liu.se