We find the disk I/O is the major bottleneck. Device: rrqm/s wrqm/s r/s w/s rsec/s wsec/s avgrq-sz avgqu-sz await svctm %util sda 1.00 0.00 85.21 0.00 20926.32 0.00 245.58 31.59 364.49 11.77 100.28 sdb 5.76 4752.88 53.13 131.08 10145.36 39206.02 267.91 168.34 857.96 5.44 100.28 dm-0 0.00 0.00 5.26 7.52 78.20 60.15 10.82 5.60 461.24 78.31 100.10 dm-1 0.00 0.00 146.12 4875.94 32617.54 39007.52 14.26 5498.79 1021.17 0.20 100.28 dm-2 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
On Wed, May 13, 2009 at 12:01 AM, Steve Loughran <ste...@apache.org> wrote: > Stefan Will wrote: > >> Yes, I think the JVM uses way more memory than just its heap. Now some of >> it >> might be just reserved memory, but not actually used (not sure how to tell >> the difference). There are also things like thread stacks, jit compiler >> cache, direct nio byte buffers etc. that take up process space outside of >> the Java heap. But none of that should imho add up to Gigabytes... >> > > good article on this > http://www.ibm.com/developerworks/linux/library/j-nativememory-linux/ > >
