An update: it appears that this is not a memory leak, but a consequence of
the way the Java 6 VM GC works combined with the NIO buffering system.
Using jmap -histo:live was the way to go: it showed a fairly constant size
after a while because it seems to force a general GC, whereas the -histo
Trustin Lee wrote:
You might be writing too fast so that the write request queue piles
up. Could you run jmap to dump your server's memory map?
Do you mean you'd like a hprof memory dump?
The test client is certainly writing as fast as it can, but the operational
server is actually very
Trustin Lee wrote:
On Nov 21, 2007 7:27 PM, Matt Phillips [EMAIL PROTECTED] wrote:
Trustin Lee wrote:
You might be writing too fast so that the write request queue piles
up. Could you run jmap to dump your server's memory map?
Do you mean you'd like a hprof memory dump?
Yes
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
