[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug awt/27926] Graphics2D drawing primitives performance (and demo)
From: |
hendrich at informatik dot uni-hamburg dot de |
Subject: |
[Bug awt/27926] Graphics2D drawing primitives performance (and demo) |
Date: |
7 Jun 2006 12:08:18 -0000 |
------- Comment #3 from hendrich at informatik dot uni-hamburg dot de
2006-06-07 12:08 -------
> You could try running this application on a JIT-capable JVM like cacao. Cacao
> can be built as easy as JamVM and you can even let the two VMs share the same
> GNU Classpath installation.
OK; just got myself a brand new cacao 0.96 (Note to cacao developers: I had to
specify --disable-disassembler to build the thing on my SuSE 8.2. I guess that
doesn't break anything.)
Here is some data (x86 Linux SuSE 8.2 with GTK 2.8, Athlon 2600+, 512MB):
<java> GraphicsDemo -size 150
paintComponent times in msec:
#objects Cacao Jamvm JDK 1.5 gcj -O3
fillRect (22500) 390 350 35 ?
drawRect (22500) 1220 1170 45 ?
fillOval (5625) 700 770 8 ?
drawOval (5625) 1880 1940 9 ?
drawLine (22500) 1300 1250 30 ?
drawArc (5625) 1750 1840 12 ?
Either the JIT-compiler isn't working correctly, or it has little effect, or
jamvm is pretty good (or all of the above). Perhaps the JNI overhead for
calling into Cairo is the bottleneck?
Don't misunderstand me; I really like Graphics2D being the default now. But a
little extra performance would be even better :-)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27926