[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug awt/23536] New: Toolkit.createImage() is extremely slow
From: |
hendrich at informatik dot uni-hamburg dot de |
Subject: |
[Bug awt/23536] New: Toolkit.createImage() is extremely slow |
Date: |
23 Aug 2005 16:48:51 -0000 |
While loading images from files via Toolkit.createImage( filename )
is pretty fast in current classpath (kudos Sven!), the remaining
variants of createImage() are still incredibly slow.
Run the attached testcase on any test image, preferably a large image
like a 4 Megapixel (or above) digicam image. Example timings on my
Athlon 2600+ under SuSE Linux with JDK 1.4.2 and Classpath CVS 20050823
with jamvm 1.3.1:
java PRxxxxx /home/hugo/img_3000.jpg
-#- createImage (file) took 2 msecs.
-#- MediaTracker (file) took 227 msecs.
-#- createImage (URL) took 0 msecs.
-#- MediaTracker (file) took 295 msecs.
-#- createImage (byte[]) took 0 msecs.
-#- MediaTracker (file) took 223 msecs.
jamvm -mx300m PRxxxxx /home/hugo/img_3000.jpg
-#- createImage (file) took 42 msecs.
-#- MediaTracker (file) took 0 msecs.
-#- createImage (URL) took 8054 msecs.
-#- MediaTracker (file) took 0 msecs.
-#- createImage (byte[]) took 8037 msecs.
-#- MediaTracker (file) took 0 msecs.
In other words, Classpath+jamvm is faster for createImage(file), but
nearly 40 (fourty) times slower for URLs and raw bytes.
Also note that Classpath somehow seems to already 'MediaTrack' the
Images before they are used.
--
Summary: Toolkit.createImage() is extremely slow
Product: classpath
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: awt
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: hendrich at informatik dot uni-hamburg dot de
CC: bug-classpath at gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23536
- [Bug awt/23536] New: Toolkit.createImage() is extremely slow,
hendrich at informatik dot uni-hamburg dot de <=