I have a job that runs for 7 minutes and processed 10 records, and I have another job ran for the same7 minutes but processed 1000 records, how could I determine which is a bad performer?
Joined: 06 Jun 2008 Posts: 8697 Location: Dubuque, Iowa, USA
Talk to your site support group and get their assistance. Your post lacks many critical details for anyone on this forum to assist you:
- each job "runs for 7 minutes" but is that elapsed time or CPU time (there is a major and distinct difference in the two)?
- what are you defining as "bad performer"? There are many, many, many ways to classify performance on a computer system (CPU usage, records processed per second of CPU time, I/O performed, data base accesses are just a few) and without defining what you're looking for either job could be a bad performer or a good performer.
- how are the jobs defined? If one of the jobs has 250 steps while the other job has 1 step and they both run "run for 7 minutes", you are pretty much comparing apples to kumquats.
- if you're looking at elapsed time, you need to quit doing so. IBM itself tells you that elapsed time for a job can vary drastically depending upon a large number of factors. At a previous employer, programmer compiles would typically complete in 5 minutes or less of elapsed time. However, when a compile was done during the month-end batch processing window, the elapsed time went up to 5 hours. Same job, same CPU usage, but very different elapsed times.
- is zIIP processing involved for one or both of the jobs?
From the outside you cannot tell, it will be down to the amount of processing done for those records. Talk to the designer of the job, s/he should have some idea.
