On 14 Nov 2008 18:58:27 GMT,
(Mark Sizzler) wrote,
quoted or indirectly quoted someone who said :
>We have problems with the Java Garbage Collector.
>It is very slow when we hold large tables in memory and perform many inserts and updates.
Others will tackle your problem directly. Here are some things to
check before you invest big bucks in new GC package.
Have you instrumented to be sure the problem is GC? not the
operations on the tables themselves?
Does your table technique keep allocating new objects frequently? It
should be doing something like ArrayList does, using a buffer bigger
than needed and only growing it when it overflows.
Have you done a study of the objects to make sure there is no
packratting? No GC is going to work well if you accidentally hold on
to objects you don't really need. see
http://mindprod.com/jgloss/packratting.html
Finally there is the ballerina in phone booth problem. What is your
ratio of live object space to heap space? No GC will work well when
that ratio gets too large.
--
Roedy Green Canadian Mind Products
http://mindprod.com
Your old road is
Rapidly agin'.
Please get out of the new one
If you can't lend your hand
For the times they are a-changin'.