Kevin Huber wrote:
> This is a comparison of mops running on Parrot (-O6 on an Athlon 700)
> versus Java JDK 1.4.0 beta 2 jitted and interpreted. You can see that
> Parrot performance is very comparable to Java in interpreted mode.
I have an Athlon 700 too. With these compiler flags:
PERL-CFLAGS = -O3 -fomit-frame-pointer -pipe -s -march=pentium -ffast-math \
-fexpensive-optimizations -fno-strict-aliasing \
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
I'm seeing 24 mops which puts Parrot even closer to Java. Do those
flags improve your times?
When you run mops.pbc through pbc2c what kind of performance do
you get?
I have a feeling that Parrot will end up with higher code density
than a JVM so performance in "real world" cases will be better. Of
course most of the effort in Java is going into JIT, so shooting for
JVM interpreter speeds is likely to be shooting way too low.
- Ken
