The ThruPut Manager team is pleased to announce that our blogging efforts are continuing, but in a new home. Posts related to batch automation and ThruPut Manager will now appear on the industry leading Compuware Inside Tech Talk blog.
CPU busy, as plotted on a graph, is not a linear function. And yet, many of us assume it is, and use that assumption for capacity planning. While linear regression may work for CPU busy functions from 20-80%, it doesn’t help you much at the lower or higher end of the utilization graph. And that’s where you actually want to know the impact of changes in transaction volume or batch workload.
Even knowledgeable performance experts make the mistake of throwing more resources at work. If 10 buffers are good, 15 would be even better, right? If we have more batch work, throw initiators at it; it will get things moving faster. But it turns out that overinitiation is very similar to putting up more toll collectors on a bridge. Immediately after the toll is paid, the lanes have to shrink to the number that fits on the bridge. If you have too many toll takers, the merge following the toll gets crazy, accidents can happen and no one is moving fast.
In the 21st century, we’ve given up our tool belts, relinquished the tape robots, and enjoyed the ease of keying in parameters, code fixes, and more on a PC dedicated to our needs. So, perhaps, it’s time to give up things like hand-managing batch performance. Sometimes, we stick with things because they’ve become habit. We know there is probably a better way to do them; but, we don’t want to fight the battle to get new software and face a learning curve.
Even without Automated Capacity Management (ACM), ThruPut Manager’s automation engine – Service Level Manager – can really speed up your batch workload and, in most cases, reduce your batch window. But it can also save you CPU cycles; and, anything you can do to put off an upgrade or reduce your MSU numbers means you’ve saved your company money.