Ruleset CPU Usage varies a lot
search cancel

Ruleset CPU Usage varies a lot

book

Article ID: 405185

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

New CPU usage figures available from LISTDSI .

So essentially all it ever does is: Address OPER "Command('MODIFY AXR,IAXDMEM') nooutput"                

However it seems to use a lot of CPU which varies a lot too, I wouldn't expect either of these to be the case.

Fire count: 402

Low CPU: 1352

Average CPU: 3720   

High CPU: 17129      

 

Are you able to explain how the CPU used by the rule can vary so much??

Resolution

Please find the  below link to IBM doc where this explains why the CPU stats may vary outside of code changes.

https://www.ibm.com/docs/en/zos/3.1.0?topic=time-cpu-variation 

 

Additional Information

It is also important to note that due to these operating system variables, the most important metric to pay attention to is the average time. Over many executions a more true value will be seen in average. This becomes even more valuable when comparing the average execution time against the same rule with a code change. This can give a good idea how the new code has made an effect on the rule.