The test result includes documentation of the tests and test schedules that represented the workload used in measuring
the system performance results. Also the result includes the system performance measurements especially the
transaction rates and page response times as well as the functional validation of getting proper system operation
during the workload.
You must also capture the system under test configuration and environmental settings as well as any documentation or
programs used to reset the system state at the beginning of the test run.
Finally, you should analyze the system resource measurements for both the load producing systems (the drivers) as well
as the system under test. This should include CPU utilization, memory size information, paging and swapping
rates, disk and network I/O utilizations as well as any application server monitoring data.
This data should be used to confirm that the test interval maintained a steady state for long enough to achieve the
needed response time and transaction rate test measurements. Based on these measurements and the nature of the
performance testing goals set out at the beginning of the test, you should be able to draw conclusions about whether
the system under test can achieve the expected performance and make recommendations about the next steps to be done in
the development or deployment of the system.
|