The document discusses best practices for performance testing including running repeatable benchmarks that change only the factor being tested, integrating tests into automated build processes, establishing realistic transaction volume models, considering the impact on related systems, and maintaining a performance "heartbeat" through continuous integrated testing to monitor trends over time.

1. FA
E
B
C D
Repeatability
Integrated
To enable us to show
a change in
performance we need
a repeatable
benchmark
Only change the one
thing we are testing
Early and Oftne
Quick feedback on
Performance means
quicker and cheaper
fixes
Integrated into
automatic build
processes where
applicable
Scientific
Change One Thing

2. CB
D
G
H I
Transaction Volume Model
Design Consider
Understand
Understand
What is the purpose
of the test?
Establish a
transaction volume
model and seek to
emulate it in test to
make the test as
realistic as possible
Attempt to make
everything involved in
the test as realistic as
possible
Consider the impact of your
change on other systems
Understand the impact.
Investigate and monitor the
environment, the application
Realistic

3. HG
I
A
F E
Heartbeat
By integrating your
performance test we can
keep a heartbeat of
performance on that
environment and look at
trends in data over a project