Nope - no swap enabled.
top - 16:53:14 up 12 days, 6:11, 3 users, load average: 1.99, 2.63, 5.03 Tasks: 133 total, 1 running, 132 sleeping, 0 stopped, 0 zombie Cpu(s): 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 35840228k total, 33077580k used, 2762648k free, 263388k buffers Swap: 0k total, 0k used, 0k free, 29156108k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ SWAP COMMAND 3398 root 20 0 203g 1.2g 186m S 0 3.5 5124095h 202g jsvc 4162 hadoop 20 0 9095m 84m 9544 S 0 0.2 5124095h 8.8g java 32153 hadoop 20 0 9057m 154m 9416 S 0 0.4 5124095h 8.7g java 18091 hadoop 20 0 9257m 561m 9460 S 0 1.6 17232821w 8.5g java 4267 hadoop 20 0 2400m 85m 9404 S 0 0.2 5124095h 2.3g java 4289 hadoop 20 0 2337m 78m 9348 S 0 0.2 0:01.44 2.2g java On 20 September 2010 17:48, Peter Schuller <peter.schul...@infidyne.com>wrote: > > Can anyone help shed any light on why this might be happening? We've > tried a > > variety of JVM settings to alleviate this; currently with no luck. > > Extremely long ParNew (young generations) pause times are almost > always due to swapping. Are you swapping? > > -- > / Peter Schuller >
