Performance Test Planning Part 3

1
Performance Test Planning Part 3
CS 4803 EPR
Distributed Computing Performance Engineering
2
Lecture Overview

• Performance Test Planning Part 3
• Scenarios
• Workloads
• System
• Enterprise
• Test environments
• Assumptions
• Risks
• Case Studies and White Papers
• Student Presentations 4

3
Scenarios

• Performance vernacular
• Different than UML definition
• Combination of scripts
• Tool-specific paradigm
• Other vernacular
• Scenario sometimes analogous to Test Cases (i.e.
  UPS)

4
Scenarios (contd)

• Scenario analogous to a particular experiment
  or test run

5
Workload

• Two types of Workload Distributions
• System
• Distribution of component workloads
• Scope limited to components of an autonomous
  system
• Enterprise
• Distribution of system workloads

6
Workload (contd)
7
Test Environments

• Detail technology stack
• Detail HW configurations
• Production environment diagram
• Performance environment diagram
• Machine names
• IP addresses
• Interfaces

8
Assumptions

• List all Assumptions!
• For example

• All performance testing will be done by ISS in an
  environment that supports LP production
  configuration and volume levels.
• LP breakpoint testing, which determines EDS
  maximum throughput, is separate testing conducted
  outside of the project performance testing and is
  not within the scope of performance testing
  detailed in this test plan.
• LP.com, LP Inside, LP Classic and System-System
  all share a common Framework for credit services.
  The common Framework will be tested at volume
  levels that support concurrent transactions from
  all LP products.
• Performance tests will include submissions to an
  EDS credit engine that returns an LP Feedback
  Certificate (i.e., submission cannot result in a
  processing error).
• Distribution of File Import versus Macro Import
  (One-way) is 70/30, based on market share
  analysis.
• Mortgagebot will not be doing performance testing
  with us so we will need to find a way to stub
  the pricing transactions to simulate a response
  from Mortgagebot.
• The pricing call transactions should be a mix of
  price and lock transactions.

9
Risks

• List all issues that present any potential
  jeopardy to the performance project, i.e.