
Prioritizing Applications to be Tested
82
You need to make adjustments when you have less disk space or memory in the
test system. Scale down databases proportionally, while retaining the same data
distributions so optimizer decisions remain constant. Scale down memory to
ensure consistent I/O rates.
Reproduce data layout across available devices as closely as possible.
If you use fewer CPUs, adjust transaction arrival rates (that is, load) and
concurrent users proportionally.
Prioritizing Applications to be Tested
Since it may be difficult to test all application functions, gather user input to
identify the most critical transactions. Write tests for those functions using the
techniques described in the following sections. Functions not tested at this time
can be validated during user acceptance tests.
Establishing Performance Criteria
Depending on the migration plan you developed, you may want to meet or
exceed the performance you get with your current system. For example, you
might decide to apply guidelines like these:
•For parallel with replication:
• Be sure to measure the overhead of the replication mechanism. For
example, if the replication costs 10%, do not begin parallel operations
until release 12.5 is tuned to outperform by 10%.
• For an around-the-clock operation, you may decide that an initial goal
of breaking even is reasonable.
•For cutover without replication, gear the migration for equivalent
performance between the old and new systems. A goal of breaking even
the first week is reasonable.
Comentarios a estos manuales