Re: PermGen, Garbage Collection and CPU utilization

Thank you for the response. That is very interesting and actually
related more to a problem I had in a prior project and I have passed
that info along to folks doing the care and feeding these days.

I learned something this morning that should have beeen obvious, but
went overlooked and that is the distinction between Java Process
Memory and Java Heap Space. In my situation, Solaris 32-bit running on
Sparc hardware, any single process cannot take and or use more that
2Gb of physical memory. So therefore I cannot actually allocate the
Xmx3000m and that really becomes 2000m (max memory per process). So,
that would seem fine, but the problems occur when Java fills all the
allocated 'heap' space with objects and leaves nothing for any of the
other tasks that need to happen to keep the JVM happy and the process
running like creating threads and garbage collection and mundane
things like that.

When you read the Java garbage collection tuning material (http://
java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html) and it tells you:

"Unless you have problems with pauses, try granting as much memory as
possible to the virtual machine."

Make sure you know that there are caveats to that statement. "As much
memory as possible" does not mean as much memory as the OS will allow
you to grant. It really means do your homework and profile your
application to learn how it is using the memory it has been given.
Learn what its upper and lower limit regions of usage are and allocate
accordingly, if necessary. Java 1.5 or greater running on a server-
class machine will automatically calculate the memory it can allocate
to the Java heap, but it is capped by the HotSpot JVM to 1Gb no matter
the amount of physical memory available. This seems to make sense as
Java probably need the other gig available to the process to do the
other fun things it needs to do to stay happy and healthy.

The moral of the story is:

Java likes memory, but there are really two "heaps" to consider.

or

It pays to know your hardware as well as you know your software.


Lost in the heap,
Jason

On Feb 3, 12:00 pm, alexandre_pater...@xxxxxxxx wrote:
PermGen is a Sun VM specificity and there
are --albeit rare-- known and documented
very weird bugs related to the PermGen.

Hibernate + Sun VM + Tomcat can exhibit, under
special circumstances, this bug and has proved
to be a real headaches to diagnose.  No easy
solution besides changing one of the components
because "it's nobody's fault" of course.

(the link should work)

http://www.jroller.com/agileanswers/entry/preventing_java_s_java_lang

My point is that maybe you're not doing anything
wrong and it's really a bug out of your control,
depending on the VM and 3rd party APIs you're using.

Have you tried with a non-Sun VM to see if it
could fix your problem?

.

Relevant Pages

  • Re: Struct inside class
    ... The compiler figures computes the ... including anything derived from "Object": Heap pointer ... memory leaks and why the .NET good garbage collector is required. ... If GC_ALLOCATE can't allocate the requested ...
    (microsoft.public.dotnet.framework)
  • Re: run-time vs compile-time
    ... > offset related to some location (like stack base) somewhere. ... > offset from heap to pi. ... When you allocate an int on the heap, it is allocated at address 1. ... application has a given amount of memory it can use as it wishes. ...
    (alt.comp.lang.learn.c-cpp)
  • Re: run-time vs compile-time
    ... > offset related to some location (like stack base) somewhere. ... > offset from heap to pi. ... When you allocate an int on the heap, it is allocated at address 1. ... application has a given amount of memory it can use as it wishes. ...
    (comp.lang.cpp)
  • Re: Huge pages and small pages. . .
    ... >> what looks like contiguous memory and away you go. ... you need to have them cached in the TLB; if the TLB runs out of ... > low end of the heap, until someone figures out a way to tell the system ... When you allocate memory, the kernel just marks a promised ...
    (Linux-Kernel)
  • Re: Huge pages and small pages. . .
    ... Since the CPU uses virtual memory always, ... them, you need to have them cached in the TLB; if the TLB runs out of room, you invalidate entries; then when you hit entries not in the TLB, the TLB has to searhc for the page mapping in the PTE chain. ... When you allocate memory, the kernel just marks a promised ... They will stay forever allocated until the highest pages of the heap are unused by the program, in which case the heap manager brks down the heap and frees them to the system. ...
    (Linux-Kernel)