Why would I need BoxScore II if I'm not upgrading hardware?
Verifying initial performance of new hardware is just one of the many uses of BoxScore II. Another use is to identify the impact that configuration changes have on performance. Changes to things like the number of logical processors or the number of LPARs can easily cause small increases in CPU usage. And a 5 percent increase in CPU per transaction time adds up. These increases in CPU usage can impact the rolling 4-hour average (R4HA), which drives up software charges, and it can force premature capacity upgrades. Running BoxScore II every week can pinpoint these hidden, slow-growing performance issues so you can address them before you incur any more unnecessary costs.
Here are just a few of the other uses of BoxScore II if run on a weekly basis:
- Identify changes in performance due to application of PTFs.
- Identify changes in CPU usage due to change in CPU utilization.
- Identify changes due to a WLM policy change that impacts performance.
- Identify increase in CPU due to the addition of compression by an application.
- Identify decrease in CPU due to purchase of a zEDC card.
- Quantify the effects of a performance tuning project for a specific application.
- Determine the effect of upgrading to a new middleware release, such as a new release of CICS, or a new compiler.
- Determine overhead of activating simultaneous multithreading (SMT) on a zIIP processor.
- Determine response time improvement due to activating SMT on a zIIP.