Meenakshi, Vinoth - CW wrote: >In environment we are using 2818-X02 box with around 1100 MIPS
That is 2 processors with zIIP and zAAP. Not a bad small machine, but has space for some growth. >... and this boxes is utilized by couple of LPARS(SYSP & SYST). One is a PROD >and other is Play LPAR and almost 90% of weight is contributed to PROD SYSP >system. We have a scenario of High CPU utilized only during our batch >window(4hours) and few days back the system was recycled due to the high CPU >utilized ... Why 'recycle' it just because of high CPU? Unless you're having serious delays/response time problems/etc there is no need to drop and start a machine just because of high CPU. We generally let our machines run at 100%, so our CPU graphs are looking like Table Mountain - flat at 100% during the day. Only when users are starting complaining about response times and delays, then we look again at our machines. >and we feel that this may create impact during Peak season in November, >December. >Also we got a report from our batch team and most of batch jobs are using >more CPU time with very high elapsed time and below is for your ref. >JOB NAME CPU TIME ELAPSED TIME >Job A 29:22.1 01.48.26.24 >Job B 19:12.3 02.44.26.24 >We are position to bring down the CPU Utilization time and make the system >healthy and we are trying to split the Batch jobs and run on different time. Only that two jobs? You should look at the full picture. Look at all your STC, TSO, Network, Batch, etc. And see how are they running. What is RMF (or other measurement tools) telling you? What are the WLM settings for them? I hope you did not put them in 'Siberia' (slow running) class. ;-) >I would like to get some clarity on the Elapsed time, whether this elapsed >will make use of the CPU and will it be the cause of high CPU utilized during >batch window? Kindly clear me. What were the jobs doing? Are you experiencing any delays? Excessive paging? etc? Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
