Test Activation of Cores Using Temporary Capacity
» Table of Contents |  | | » Index | | |
| | |
| ||
| ||
You may want to test your software application for proper operation and improved performance by activating an additional core. The use of temporary capacity (TiCAP) or Instant Access Capacity (IAC) is required for activation of a core without usage rights for testing purposes. See Chapter 5 “Temporary Instant Capacity” for details.
The following testing guidelines are meant to be an aid to your test plan. You may need to get consulting help to develop a detailed test plan.
Test your applications for proper functionality and performance first by testing with the number of inactive cores equal to the number of cores without usage rights. (The system should already be configured this way.) Be sure to check measurement tools that monitor core usage.
Acquire temporary capacity for the necessary amount of core test activation.
Use temporary capacity to activate one or more inactive cores to be used while your applications are running.
Confirm that measurement tools, which monitor processing usage, account for the newly activated core(s).
Verify that applications are benefiting from the performance of the extra cores (as per your expectations for your applications). Note: some applications may need to be restarted or reconfigured to take advantage of the newly activated cores.
When you are finished with your testing, deactivate cores until the number of inactive cores again matches the number of cores without usage rights, thereby stopping the usage of temporary capacity.
Use icapstatus to verify that no cores are consuming temporary capacity.