Capacity Planning: Are You Proactive or Reactive?
When IBM first introduced sub-capacity pricing, it was a boon for capacity managers. From a financial standpoint, it allowed them to be more proactive in their capacity planning. In the pre-sub-capacity era, you had to carefully manage upgrades because of the huge potential impact on software pricing. Now, you can rightsize your hardware and worry less about software costs—until you hit a soft cap, that is.
Caught in a reactive bind
Because of this, capacity planning has become more of a reactive game for many. Either the monthly sub-capacity reporting tool (SCRT) reports increasing costs or you’re getting a stat call indicating performance problems with a key workload. Faced with this situation, many feel it’s safer to overestimate requirements to ensure they can meet service level agreements (SLAs). Hitting a cap just isn’t worth it—even if it means that you can’t deliver the cost savings management wants.
Caught in the bind between lower software bills and being blamed for unhappy customers, the decision seems simple. But capacity planning is supposed to be about being proactive—there must be another way!
Smart Capacity Planning
Fortunately, there is. The key is to ensure that you hold back less time-critical workloads to protect the more critical online workloads (OLTP). While that sounds simple, in the dynamic world of managing the rolling four-hour average (R4HA), no person can really predict what might change, let alone plan for it. No, you must delegate this task to a technology that is always on, and always aware—Compuware ThruPut Manager.
First you need to understand how batch contributes to your peak R4HA using the MSU Analyzer. Once you identify how reducing batch demand at key points can change your peak CPU demand, you’re able to see the value of a solution that can automatically detect and reduce batch demand to keep all workloads performing.
The Automation Solution
ThruPut Manager’s Automated Capacity Management (ACM) allows you to reduce your R4HA and the resulting MLC costs with, or without, soft caps, and with considerably lower risk. ACM gives you the productivity you want (unless you’d prefer to stay up 24 hours a day monitoring and tweaking workloads every 10 seconds).
Reactive capacity management is so 20th century, isn’t it? Cloud, mobile, Big Data and power management issues are introducing ever increasing complexity to capacity planning. You need to free up time to tackle these challenges. And you can only achieve this by letting smart software aid in your work.
Latest posts by Denise Kalm (see all)
- Breaking Down Dev and Ops Silos with Communication, Collaboration and Trust - April 19, 2018
- What Do Performance and Capacity Roles Have to Do with DevOps? - February 1, 2018
- How Developers Can Boost DevOps Through Automated Batch Processing - December 7, 2017