On Nov 22, 2007 3:08 PM, Matt Phillips <[EMAIL PROTECTED]> wrote: > Trustin Lee wrote: > > > > I opened the hprof files you provided in YourKit profiler and it seems > > like the actual amount of memory the JVM is very small: > > > > http://www.nabble.com/file/p13891096/avis-profiler-report.zip > > avis-profiler-report.zip > > > > I often observe JVM increases its total heap size too much even when the > > application doesn't demand that much. Wouldn't it be such a case? > > > > OK, now I'm really confused. Am I reading the output of the jmap -histo > output wrong? The output I cited in the original mail seemed to be saying > there were 2,192,677 instances of > java.util.concurrent.ConcurrentLinkedQueue$Node, taking up 35,082,832 bytes. > And 8,285 byte arrays taking up 23,427,664 bytes. Which seems excessive for > a server with just 20 connections, to put it mildly. But, as you say, the > reports that YourKit generated don't bear this out (although that output is > not from the exact same instance as the hprof's, it was taken earlier in my > testing).
Hmm.. I don't have much experience with jmap histogram. It might be including the objects to be GC'd or that has been GC'd so far. I'm not sure. Do you get OOM btw? > Thanks for your help so far, No problem. Please keep up updated to find out any potential problem. :) Thanks, Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
