Performance Test Results Template

Test Goals

Please specify the goals of the test. Its important to layout the Entry and Exit criteria in this section.

Success Criteria : [To include overall throughput goal. This also needs to account for server stats and fanout]

Test Parameters

  • Test Scenario [e.g. Top pages/Pulse or a new test that needs to be written]
    • Expected throughput.
    • Initial topology
    • Staging – Production scaledown
  • List of Service(s) under Test (SUT) : [This needs to come from the initial load test and a fanout report]

Result Summary:

  • Performance Statistics : *
  • Any capacity addition or config change in production MUST be called out.

Report results as below

foreach service in the fanout report [including all frontends]
  Throughput achieved for each service; Incremental or total
  Cores required for throughput CPU Utilization
  Memory required
  GC Settings needed
  Healthcheck Stats reviewed and signed off threadpool,connectionpool, memcached setting, DB connection pool
  Comparison with production capacity planning. Specify any incremental capacity addition needed
  Production/Staging capacity boost recommendation if needed.

Test Result Link :

[Hudson link to test result]

This contains the details given below

Throughput :

Server Stats :

CPU Utilization in the Service(s) under test ( good to include related components as well )

GC Stats :

GC Stats for Service(s) under test ( and related components if necessary )

Full GC count –

GC failure count –

GC Throughput(%) –

Container Stats :

Average thread pool count :

Memcached stats [Optional / if necessary ] :

Test Setup :

List number of cores in test environment for each Service Under test :

List number of Max threads in container for each Service Under test :

Test Setup – Prod Setup Mapping :

Services running on the box running SUT
number of servers running SUT
Configuration of Servers running SUT
Number of Max Threads on Container running SUT

<!– –>

Labels parameters

Leave a comment

Filed under J-testing, JMeter, performance

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s