Re: [dtrace-discuss] Java Process in LCK/SLP

2008-04-18 Thread przemolicc
We had such case in the past. I don't think it is the same reason but might give you some ideas. We had a lot of locks. By using plockstat it turned out that those locks comes from malloc. Using mtmalloc or libumem reduced a number of locks but it was still a huge number (and eating our CPU). By us

Re: [dtrace-discuss] Java Process in LCK/SLP

2008-04-16 Thread Jim Mauro
Try linking the JVM to libumem.so.1 (export LD_PRELOAD=/usr/lib/libumem.so.1) I have, in the past, been able to reduce lock contention in malloc using libumem malloc. If that does not help, you need to see where the mallocs are coming from in the code, and see if there's opportunity to change the

[dtrace-discuss] Java Process in LCK/SLP

2008-04-15 Thread Kleyson Rios
Hi, I am a newbie in dtrace. There is a multi-thread application running in my box. But looking prstat –Lmp i saw that almost all time is LCK and SLP. A ran plockstat and saw the most locks were malloc, so I changed my application to use mtmalloc, but didn’t resolv the problem. After cha