Escolar Documentos
Profissional Documentos
Cultura Documentos
Prepared by Sriraman K
Objectives
Performance Testing
What Why Need of Performance Testing How
Performance Testing
What is Performance Testing? Why performance testing required? What are the benefits and false notion? Various performance tool in the market Introduction to Silk Performer SP Architecture SP Course Content
Why - Performance
To ensure the defined standards are met To avoid
Design errors due to improper
Exception handling Coding for multiple user environment Database management
Silk Performer
To load your application, Silk Performer emulates an environment where multiple users work concurrently. While the application is under load, Silk Performer accurately measures, monitors, and analyzes a systems performance and functionality.
Architecture Overview
Client-Server Paradigm
Client Server applications deliver higher functionalities and power, but also introduce new risks:
Higher Performance risks due to large number of users accessing the system simultaneously. Impossible to manually simulate load on application
10
11
12
13
14
15
16
17
Silk Performer-Scenarios
Using Silk Performer, you divide your application performance testing requirements into scenarios. A Scenario could be running a Use Case. In ideal condition there may be 10-20 use cases /Scenarios in a AUT. A scenario defines the events that occur during each testing session. Thus, for example, a scenario defines and controls the number of users to emulate, the actions that they perform, and the machines on which they run their emulations.
18
VUsers
In the scenario, Silk Performer replaces human users with virtual users or Vusers. When you run a scenario, Vusers emulate the actions of human users submitting input to the server. While a workstation accommodates only a single human user, many Vusers can run concurrently on a single workstation. In fact, a scenario can contain tens, hundreds, or even thousands of Vusers.
19
Scripts
The actions that a Vuser performs during the scenario are described in a script. When you run a scenario, each Vuser executes a script. The scripts include functions that measure and record the performance of the server during the scenario.
20
Transactions
To measure the performance of the server, you define transactions. A transaction represents an action or a set of actions that you are interested in measuring. You define transactions within your script by enclosing the appropriate sections of the script with start and end transaction statements.
21
Measure Start
Measuring page times To measure the page times in the log, we can also use following to measure the time Measurestart (StringName) MeasureStop(StringName) MeasureGet MeasureStart Include file Kernel.bdh Syntax MeasureStart( in sMeasure : string ): boolean; Return value true if successful false otherwise Parameter sMeasure - Measure name used to identify the measure when calling additional measure functions and when analyzing the results written to both the results repository and individual result filesExample MeasureStart (<StringName>);
22
Measure Stop
MeasureStop Include file Kernel.bdh Syntax MeasureStop( in sMeasure : string in bIgnoreOnError : boolean optional ): number; Return value Final value of the custom time measure in 1/1000 secs. Parameter sMeasure - Measure name identifying the custom time measure to stopbIgnoreOnErrorWhen enabled, measured time is included in calculations if no error has occurred since the timer started (optional). The default value is false. Example MeasureStop(<StringName>)
23
Work Loads
You use the Silk Performer Work Loads to manage and maintain your scenarios. Using the Work Load, you control all the Vusers in a scenario from a single workstation. When you execute a scenario, the Silk Performer Work Load distributes each Vuser in the scenario to a host. The host is the machine that executes the Vuser script, enabling the Vuser to emulate the actions of a human user. Ideally, the Silk Performer Work Load must be installed in a separate system outside the test bed.
24
25
1. 2. 3. 4. 5. 6.
Silk Performer has various types of Vusers. Each type is designed to handle different aspects of todays system architectures. Vuser Types: E-business Vuser : For Web (HTTP,HTML), Corba-Java, GeneralJava, LDAP, POP3, COM/DCOM, Jolt, LDAP, POP3 and FTP protocols. Middleware Vuser : For Jolt, and Tuxedo(6.0, 6.3) protocols. ERP Vuser : For SAP, Baan, Oracle NCA, Peoplesoft (Tuxedo or Web) and Siebel protocols. Client/Server Vuser : For Informix, MSSQLServer, ODBC, Oracle (2-tier), Sybase Ctlib, Sybase Dblib, and Windows Sockets protocols. Legacy Vuser : For Terminal Emulation (RTE). General Vuser : For C template, Java template, and Windows Sockets type scripts.
26
27
Course Content
Preparing the Workbench
Projects
Protocols Profiles Scripts Include Files Data Files Agents Work Loads
Script
BDL (Benchmark Description Language Record
28
Course Content
Script Cont.
Replay Parameterization Correlation
Auto Manual
Work Load
Increasing Steady State Dynamic All Day Queuing Distributing Load
With same IP address With Different IP Address
Applying Transaction
29
Course Content
Work Load Cont. Analysis
Monitors Summary Transaction Response Time Hits per sec Throughput Errors Page break down
30
31
FeedbackPlease spend few minutes from your valuable time to provide your feedback.