Run Tests
Run the performance tests with the associated test schedules based on the workload(s) as defined in your workload
definition specification.
|
Monitor System Activities
If a particular transaction is too slow to meet your success criteria, then you must analyze why that is true and adjust
something in the application code, the database structure, or the communication to the database back-end server in order to
improve the transaction speed. There are always multiple solutions involving deploying more or faster hardware as
well as software changes to accomplish these improvements. Based on the objectives and constraints on the system
deployment plan and schedule, you may favor one solution over another. |
Update Performance Test Plan
Adjust the test plan dynamically based on the results of a given test run and based on the analysis of the response time
and resource utilization measurements made during the test. |
Update Performance Test Schedule
Your testing schedule may have to be deferred, extended, or canceled and rescheduled based on how quickly the system can
be re-fitted with the improvement. Once an improvement of this sort is in place, it may be totally transparent to the
user and the test or the test may have to be altered or even re-recorded due to the magnitude of the change. The test
schedule may have to be restarted at the beginning or more likely started from where you left off when you found the system
bottleneck. After getting a successful run at the 100% load point, you should be able to capture the test results and
complete the test plan. |
|