background image
<< Implementing Performance Tests | Number of Virtual Testers Supported Under Normal Conditions >>
<< Implementing Performance Tests | Number of Virtual Testers Supported Under Normal Conditions >>

Examples of Performance Tests

Examples of Performance Tests
255
Examples of Performance Tests
This section summarizes some typical performance tests. Each test objective is
accompanied by a table that lists the key elements to consider when defining such a
test. The tables are intended only as a guide; they do not attempt to define all of the
possible elements you can include in your performance tests.
Number of Virtual Testers Supported Under Normal Conditions
Suppose you want to determine the number of virtual testers that a server can
support, to ensure that the system can meet your scalability requirements. How many
virtual testers can the system support before the response is unacceptable?
For example, you estimate that a database system supports 500 virtual testers. You
could plan to run the test with 300, 400, 500, 600, and 700 virtual testers concurrently
performing multiple tasks. The following table shows the key elements you might
include when designing the test:
Incrementally Increasing Virtual Testers
A common requirement in performance testing is to model what happens across a
span of time while different virtual testers perform their work. For example, suppose
you want to test how your server performs early in the morning when people are
starting their day. You also want to know how the server handles an increasing
workload during the day and particularly at times of peak workload.
Test Scripts
Suite
Reports
A test script to initialize
the database.
A test script to log virtual
testers in.
A test script for each
virtual tester task:
s
adding records
s
deleting records
s
querying the database
s
running payroll reports
A fixed user group with one
virtual tester. This virtual
tester logs in, initializes the
database, and sets an event
indicating that the database
is initialized.
A scalable user group with
many virtual testers. This
group logs in and waits until
the event is set. It then
executes the scenario.
A scenario that contains:
s
a selector to randomly
select a test script
s
a test script for each
virtual tester task
A test log to show whether
all virtual testers in the
suite successfully ran to
completion.
A Command Status report
to show whether the
server completed its
requests successfully.
Performance reports for
each suite run: 300, 400,
500, 600, and 700 virtual
testers.
A Compare Performance
report comparing the
output of all five
Performance reports.