Excessive ZOWESVR CPU and EXCP consumption about community HOT 8 CLOSED

This has been raised as RTC defect 21171.
https://jazzk01.hursley.ibm.com:9443/ccm/web/projects/Zowe#action=com.ibm.team.workitem.viewWorkItem&id=21171

from community.

Some questions:

1. Is this normal for WAS Liberty servers?
2. Is this only apparent on zD&T systems, or do zD&T systems suffer more?
3. Is this consistent across different systems? What is the CPU+EXCP consumption per hour on an idle system?

from community.

It would be worth checking the Liberty configuration as by default it will poll for configuration and application updates and this will cause CPU consumption even in an idle system.

Polling can be turned off by adding
<config updateTrigger="mbean"/>
and
<applicationMonitor updateTrigger="disabled"/>
to server.xml configuration.

from community.

Thanks. So far, we've added this to server.xml

<applicationMonitor dropinsEnabled="false" updateTrigger="disabled"/>
<config updateTrigger="disabled"/>
<automaticLibraries monitorEnabled="false"/>

Please advise if yours is better.

We also added this to jvm.options:

-Xtune:virtualized  
-Xjit:iprofilerBufferSize=4096

We've isolated the nodeServer and zssServer to separate STCs, which are not as hungry as the STC that runs Liberty, so Node resource consumption is not the prime cause.

from community.

I've also heard of a recurrent CPU issue in Node, thought to be fixed in version 6.14.3 but now reappeared. While Node contributes to the overall CPU of ZOWESVR, it's Liberty Atlas which consumes the most by far.

from community.

The CPU problem seemed to vanish after I tore down the ZOSMF server and angel processes a couple of times. Currently ZOWESVR3, the greediest CPU user, is averaging 4.5% at idle.

from community.

I am hoping to have a CPU, memory and storage view of Zowe by the end of the week. My big concern is the mix of processes (JAva, Node and C) under ZoweSVR

from community.

Close by issue 21 below:
zowe/explorer-server#21

from community.