On Jan 20, 7:22 pm, CuppoJava patrickli_2...@hotmail.com wrote:
Some articles I read point to Java's use of garbage collection as the
culprit, and I'm wondering whether that is true. I know Scheme and
Common Lisp also use garbage collection, so do gui programs written
those languages also
In general, accusing garbage collection of being culprit for sluggish
GUI performance is plain wrong. Swing GUIs can be quite snappy when
done right - but surely there are lots of not-so-right done apps out
there.
Also, the amount of GC required depends a lot on what you're doing,
and how.
On Jan 21, 3:20 am, Joonas Pulakka joonas.pula...@gmail.com wrote:
In general, accusing garbage collection of being culprit for sluggish
GUI performance is plain wrong. Swing GUIs can be quite snappy when
done right - but surely there are lots of not-so-right done apps out
there.
From my
Thanks for the responses.
It seems the consensus is that the slow responsiveness of Java apps is
mostly due to an issue with Swing and how it is used rather than with
garbage collection. That sounds very encouraging.
The last point that interested me was: I heard someone mention that
It seems the consensus is that the slow responsiveness of Java apps is
mostly due to an issue with Swing and how it is used rather than with
garbage collection. That sounds very encouraging.
Determining whether the GC is responsible is pretty easy. Just runt
with -verbose:gc (or -XX:+PrintGC)
Often you will also get better behavior by using appropriate -Xms/-Xmx
options. The above are just examples of course and not the way to do
it or anything.
i would like a JVM that has a hot spot jit for GC tweaking.
--
You received this message because you are subscribed to the Google
Groups
Hi,
Java was my first language, and my favorite platform to work in, but I
do notice (especially after buying a mac and experiencing Mac OS X)
that gui programs written on the JVM are noticeably less responsive
than their native counterparts.
Some articles I read point to Java's use of garbage
Thanks for your opinions
for the most part, it is theoretically (and research implementations
have shown) that GC can be just as responsive from an end-user
perspective as manual memory management. i believe the price to pay is
usually a significantly larger memory footprint. and, there is
If you are talking about gui's written in swing you might have more
luck with AWT since that is supposed to be using native gui components
rather than doing it's rendering in java. I suspect that the
sluggishness of swing is due to the fact that it has to copy a lot of
data between the java heap
