Found the problem in the custom application code. Apparently there was a system
call to get the system time which was executing 1000's of times per transaction
... :)
Thanks for all the assist/ideas
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4096092#
Hey Pete,
We did take a closer look at some of the TP-Processorxxx threads and that got
the developers thinking it might be their code. We've now isolated it to our
application code.
Now the real fun begins...
-Rob
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewto
Interesting there are no other takers on this ... Nobody else is seeing high
system time (1:1 with User cpu time)?
I separated apache and Jboss to different physical boxes and the problem
followed jboss/jvm. So under load, apache is truely snoozing...
I'm looking into things like strace, oprof
Implemented each of the suggestions in 1 and 2 and also went up to 1024/250
with really no noticed improvement in the ratio. I'll keep tweaking but I'm
wondering, does everyone else see a similar ratio between user and system cpu
time?
Thanks,
-Rob
View the original post :
http://www.jboss.
On our production app servers I'm seeing high system cpu time as compared with
user cpu time. The ration is 1:1 which I feel can be improved upon ... Yes?/No?
We're running apache and JBoss on the same server with mod_jk connector and
have narrowed the high system cpu time down to the JBoss proc
