zCost Management extends soft capping capabilities around container pricing and mobile workload pricing to maximize cost and performance optimization.
PARIS, FRANCE, September 27, 2018– zCost Management©, one of the leading company in mainframe cost control, announced today, the release of version 4.2 of AutoSoftCapping, a software designed to optimize mainframe capacity for cost control and performance.
The ability to reinvest mobile discounts for enhanced performance
IBM mobile workload pricing (MWP) is intended to reduce the impact of growing mobile workloads on costs. 60% of the consumption of these workloads are excluded from the billing in the form of discounts at the end of each month.
“Our customers told us that they have a fixed budget for their mainframe activities, thus they are not so interested by these discounts. They are also unpredictable as customers do not have any control over the number of mobile workloads running of their platform.”, Bruno Koch, CEO of zCost Management©, explained. “They prefer to keep the same level of billing and use these discounts to boost the performance of their machine”.
In version 4.2 of AutoSoftCapping, Mobile workload activity is tracked in real time and incorporated inside the capacity management process. Simply put, 60% of this activity is removed from the calculation of soft capping limits. The immediate effect is a performance boost with no extra costs when mobile workloads are running.
In addition, mobile workload activity is now displayed in real time in AutoSoftCapping reporting to give customers insights about their mobile consumption.
A better capacity management with Container pricing
Container pricing does not rely on the rolling 4-hour average for billing. This means that it escapes the scope of soft capping.
Customers can choose to delegate container workloads to specific LPARs or choose to let the workloads run among all LPARs, which is known as a “collocated container.” However, when it comes to the latter option, they run the risk of overexerting LPARs. By default, container consumption contributes to the sub-capacity limit, so given this constraint a system is prone to performance capping.
The utility of AutoSoftCapping 4.2 for container pricing is two-fold:
- Container pricing exemption: Exclude container workloads from the billing limit calculation and free up LPARs.
- Real time reporting: Identify and record consumption of the different containers according to their profile (Advanced Development and Testing, Payments Pricing, and New Applications). This way, users are able to track the consumption of every container and make adjustments accordingly.
# # #
To learn more about the new version 4.2 of AutoSoftCapping, read the full release note.