Jukka Zitting a écrit :
Hi,
On Thu, Oct 9, 2008 at 5:10 PM, Cédric Chantepie <[EMAIL PROTECTED]> wrote:
Can you use something like the "top" tool to ensure that it's actually
the server Java process that's taking up all that time. At least the
stack traces you sent don't seem to indicate any major processing.
BR,
Jukka Zitting
I've tried again, with some indexing configuration I thought can
decrease indexing process work (http://pastebin.com/m721093de), but it
still overload (even if it "seem", not really sure if significant, that
when transfer was ended load was lesser than previously, >>"just"<< ~2).
top - 17:32:28 up 30 days, 5:55, 4 users, load average: 5.22, 3.38, 2.18
Tasks: 78 total, 2 running, 76 sleeping, 0 stopped, 0 zombie
Cpu(s): 99.7%us, 0.3%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si,
0.0%st
Mem: 645732k total, 639072k used, 6660k free, 17496k buffers
Swap: 522216k total, 198580k used, 323636k free, 284316k cached
[...]
24 0 730m 207m 11m S 99.5 32.9 4:57.27 java
Thanks for any help,
Cédric
