Michael Durket wrote:
>
> I started up the SwingSet demo and noticed how slow it was. I ran
> top and noticed that even when I was doing nothing (i.e. no mouse
> moves, no selections, just sitting there) the demo was eating up
> 16 MB of memory and 50-60% of my cpu. It seems as if the virtual
> machine never waits (at least when running this demo).
>
One of the issues with Swing performance has to do with the Swing
components not having native peers (unlike AWT). With AWT, the peering
mechanism creates a native widget which handles all the drawing of the
widget; Swing has to do all of its own drawing and so forth, which is
why many people find Swing slow, and also may be related to the memory
usage you're seeing in the SwingSet demo.
--
Jeff Galyan
http://www.anamorphic.com
http://www.sun.com
jeffrey dot galyan at sun dot com
talisman at anamorphic dot com
Sun Certified Java(TM) Programmer
======================================================================
Linus Torvalds on Microsoft and software development:
"... if it's a hobby for me and a job for you, why are you doing such a
shoddy job of it?"
The views expressed herein do not necessarily reflect those of my
employer.
Sun Microsystems, Inc., has no connection to my involvement with the
Mozilla Organization.
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
