Dear All,
just curious is this behavior normal?
this is a multi-core server (total 16-core), and sometimes we found the java process (jetty) runs up to 250% CPU% in "top" listing, just like below :
Code:top - 16:03:58 up 81 days, 3:52, 4 users, load average: 1.78, 2.73, 3.56 Tasks: 326 total, 1 running, 325 sleeping, 0 stopped, 0 zombie Cpu(s): 13.0%us, 1.1%sy, 0.0%ni, 85.8%id, 0.0%wa, 0.0%hi, 0.2%si, 0.0%st Mem: 12296764k total, 11419060k used, 877704k free, 383992k buffers Swap: 25165812k total, 312k used, 25165500k free, 3701628k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 6228 zimbra 15 0 5976m 5.2g 16m S 222.5 44.7 18852:56 java
the java process is for jetty server :
I think it just means that this process almost consume almost 3 CPU cores for job processing, and we still have lots of space (total 16-core) for other processes. is my understanding correct?Code:zimbra 6228 6227 17 Jan28 ? 13-02:15:32 /opt/zimbra/java/bin/java -server -Djava.awt.headless=true -XX:+UseConcMarkSweepGC -XX:NewRatio=2 -XX:PermSize=128m -XX:MaxPermSize=128m -XX:SoftRefLRUPolicyMSPerMB=1 -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintGCApplicationStoppedTime -Xss256k -Xms4803m -Xmx4803m -Xmn1200m -Djava.io.tmpdir=/opt/zimbra/mailboxd/work -Djava.library.path=/opt/zimbra/lib -Djava.endorsed.dirs=/opt/zimbra/mailboxd/common/endorsed -Dzimbra.config=/opt/zimbra/conf/localconfig.xml -Djetty.home=/opt/zimbra/mailboxd -DSTART=/opt/zimbra/mailboxd/etc/start.config -jar /opt/zimbra/mailboxd/start.jar /opt/zimbra/mailboxd/etc/jetty.properties /opt/zimbra/mailboxd/etc/jetty-setuid.xml /opt/zimbra/mailboxd/etc/jetty.xml
any advice? Thanks.


LinkBack URL
About LinkBacks

