Performance Studio Introduction

1
PerformanceStudioIntroduction

• Rational Performance Studio Application
  TrainingNoblestar Systems

2
Agenda

• Performance Studio Overview
• Terminology
• Testing Process
• Recording Concepts
• VU Scripting
• Q A

3
Performance Studio Overview

• Performance Studio is an automated load test
  delivery system
• Runs thousands of simulated users (called Virtual
  Users) against web, application, and database
  servers.
• Tests performance, capacity, and stress
  capabilities of applications.
• Can test functionality and ensure the performance
  and accuracy of the System Under Test (SUT)
  during load.
• Tests developed to simulate actual user load.

4
Performance Studio Overview

• Pros
• Minimizes test cycles
• Improves test validity
• Improves test repeatability
• Maximizes test reliability
• Maximizes test coverage
• Automatically generates standardized reports

• Cons
• Requires detailed test planning
• Test scripts must be debugged
• Higher start-up cost

5
Terminology

• Workload set of activities performed on the
  System Under Test (SUT)
• Capture process of recording a user-scenario
  into a test script
• Playback submitting a test script to the SUT
• .wch File raw data recorded during the capture
  process
• .s File test script comprised of VUc commands
  that drive user activity
• Schedule set of user groups and scenarios that
  define a workload
• User Groups a number of users that perform
  similar activities
• Scenario a set of actions to be taken by a user

6
Testing Process

• Test Planning
• Test Design
• Test Script Implementation Debugging
• Test Execution
• Test Analysis

7
Testing Process

• Test Planning
• Work closely with Business Analysts and Client.
• Conduct usage research and identify potential
  traffic patterns.
• Conduct analysis of performance tests with regard
  to site architecture/flow.
• Construct the Performance Test Plan.
• Identify required test data for workload
  scenarios.
• Identify server metrics to be monitored by
  hosting facility.

8
Testing Process

• Test Design
• Design performance tests with regard to site
  architecture/flow.
• Define all Performance Scripts to be recorded.
• Construct the Performance Workload Model.
• Review before test script implementation.
• Configure Performance lab.

9
Testing Process

• Test Script Implementation Debugging
• Record, Customize and Debug Identified Scripts
• Add logic for conditional execution, looping,
  etc.
• Add workload information for multi-user testing
• Add datapools and variables
• Baseline each script individually.

10
Testing Process

• Test Execution
• Create Schedule to represent Workload Model.
• Incrementally scale total VUs up to client
  target.
• Stay in continual contact with client, system
  administrators, DBAs, and/or developers to
  informally report on findings throughout the
  test.
• Regression test when changes are made to the SUT.
  
• Modify tests / scripts as necessary when changes
  are made to the SUT.

11
Testing Process

• Test Analysis
• Analyze as you go.
• Report to Client at least weekly, more if the SUT
  is not responding IAW expectations.
• Use Performance Studio Reports as a place to
  start.
• Research, research, research.
• Final written report contains NO new information.

12
Recording Concepts

• Methods
• API
• Network
• Proxy

• Protocol
• TCP/IP
• HTTP/HTTPS
• SQL
• Tuxedo
• Jolt

13
Recording Concepts

• API Recording
• Preferred method, records Windows Messaging
  between the browser and the operating system.
• Only records activity on the Master station.
• Works with HTTP and HTTPS.
• Works with Internet Explorer 4.0 and up or
  Netscape 4.7.

À
PS
14
Recording Concepts

• Network Recording
• Records broadcast network packets from any
  station to any station.
• Cannot parse out HTTPS from encryption.
• Cannot work across any form of gateway (bridges,
  routers, switches).

À
PS
15
Recording Concepts

• Proxy Recording
• Performance Studio acts as proxy server to SUT
  during recording.
• Works across any network configuration.
• May require modification of application code.

Gateway
À


PS
16
VU Scripting

• Scripts are initially recorded in Rational Robot
  nearly identically to Automated Functional Test
  Scripts.
• Scripts are recorded in VUc
• VUc is based on C with custom function libraries
  designed to create load test scripts.
• VUc supports datapools and variables, looping,
  conditional branching and many other advanced
  scripting topics.
• Scripts may call header files and external C
  files.
• VUc scripting will be covered in detail in
  another class.

17
Q A
Any Questions???