HP explains why Instant Script-Free Performance Testing is a poor hoax

1. 7/31/2014 The Protocol ComplexityMatrixand what it means f... - HP Enterprise Business Community
http://h30499.www3.hp.com/t5/HP-LoadRunner-and-Performance/The-Protocol-Complexity-Matrix-and-what-it-means-for-your-load/ba-p/6559424#.U9ng-fmSwsw 1/3
 For Home For Work Support
Community Home > Software > ApplicationLifecycle Management > HP LoadRunnerandPerformance CenterBlog >
The ProtocolComplexity Matrix andwhat it meansf...
Article Options
1
Post a Comment
The Protocol Complexity Matrix and what it means
for your load testing
Craig_Drummond | July 30, 2014
As a general rule, the more complex a protocol is to script, the more the protocol relies on monitoring the network stream
and the less that it needs to understand the actual application under test’s user interface. It also tends to be true that with
this type of protocol, the more virtual users of that protocol type will run on any specific load generator.
This has led to the development of the Protocol Complexity Matrix and can be visualized by the graphic below.
This is a representation of common results and you may find that your individual use of a protocol may provide more or
less virtual users than indicated. This diagram shows you that if you want to make the job of scripting easier, it comes at
the cost of memory. Using more memory makes the protocol less scalable up to the point that you reach the GUI protocol,
which out of the box has a 1:1 ratio between virtual user and load generator.
The goal of any organization is to find the right balance. Nearly any application can be scripted with the Winsock protocol,
regardless of technology used by the application under test. However, working with raw socket commutations can be
difficult to learn and requires a great deal more time to develop and test; thus making the solution impractical for many
projects. This is why higher-level protocols have been developed, to save time.
What is not easily represented in the matrix is another fact; the more reliant you are to the network stream, the more
susceptible your scripts are to changes in that stream. So the application that is scripted with QTP can undergo massive
changes in the background and the scripts for that application can still function without modification. But these same
changes to an application recorded with the Winsock protocol could render the entire script useless and a throw away. This
fact brings me to my next question:
How many users can my Load Generator run?
In previous versions of LoadRunner and Performance Center, a protocol footprint spreadsheet was distributed by HP to
provide a guideline for how much memory a script of a particular protocol would consume. The problem was recipients of
the footprint spreadsheet thought of it as definitive rather than prescriptive. It is much better to use a repeatable process
and a formula to mathematically estimate the total number of users a load generator can run on a per-script basis. The
process and formula outlined below should be used for every script that you intend to use in load testing, and every load
generator that will participate in the test as well.
Here are the steps you should take these scripts that you intend to use in a load test:
1) Develop your script and ensure that it will run with multiple users, multiple iterations. This is the normal development
of the script of any protocol.
2) Create a load test using the script that you want to examine with one virtual user and execute the test. Use a delay of
My Community
Register Now
Log in
Quick Links
Search
Go
About the Author
Follow Us
Top Kudoed Posts
Getting Started
Join the Conversation
Already a member?
Craig_Drummond
I have been working in the computer
software industry since 1989. I
started out in customer support then
software testing where I was a ver...
Working with
HP
LoadRunner
and HP
Network
Virtuali...
10
LoadRunner
licenses now
available on
Pronq.com
3
The Protocol
Complexity
Matrix and
what it
means f...
1
You are
invited to a
party in the
cloud, a
1
Discussion Boards Blogs Community Knowledge Base English
More
Search HP Forum
Blog
Search HP.com

2. 7/31/2014 The Protocol ComplexityMatrixand what it means f... - HP Enterprise Business Community
http://h30499.www3.hp.com/t5/HP-LoadRunner-and-Performance/The-Protocol-Complexity-Matrix-and-what-it-means-for-your-load/ba-p/6559424#.U9ng-fmSwsw 2/3
Everyone's Tags:
Application Load Testin… GUI protocol LoadRunner memory Performance Center
View All (9)
a few minutes in starting the script and monitor the load generators available MB of RAM and note any decrease when the
virtual user starts. This is the “First VUser Memory”.
3) Modify the load test to use five – ten virtual users and execute the test again. Keep the same delay for the start and
have each user start one minute apart. Monitor the load generators available MB of RAM and note the drop in RAM as each
user starts. Average the amount of RAM that the second virtual user on up uses and this is the “Each Additional VUser
Memory”
4) Determine the total RAM available on the load generator This is the “TOTAL LG RAM”
5) Subtract 700 – 750 MB of RAM for the OS
6) Determine what is 75 percent of the remaining available RAM
7) Subtract the “First Vuser Memory”
8) Divide what is left by the “Each Additional Vuser Memory”.
9) Add one and you have the “Total Virtual Users that will run on that load generator”
10) Repeat this process and formula for each script and every load generator that has a different level of memory.
The equation will look something like this:
This equation will work for all but a handful of protocols. These are the protocols that this equation may not work: Citrix,
RDP, any protocol with the term GUI in it, and QTPUFT scripts. That is because these scripts can further be limited due to
GDI resources. These are graphical resources that are an attribute of the video card installed on the computer.
GDI resources are not able to be monitored and they cannot be adjusted without replacing the video card. When GDI
resources are consumed any virtual user that attempts to run on that LG will fail.
To learn more about LoadRunner and Performance Center and how to estimate the total number of users a load generator
can run on a per-script basis visit the product homepages here.
Tags: Application Load Testing| GUI protocol| LoadRunner| memory| Performance Center| View All (9)
Labels: Load Testing
Labels: Load Testing
Post a Comment Permalink 1
http://
*Name
*Email
Website (optional)
Leave a Comment
We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours
To ensure your comment is published, be sure to follow the Community Guidelines.
View All
Latest Articles
Latest Comments
Archives
public ...
Big news! HP
LoadRunner
and
Performance
Center 12....
1
The Protocol Complexity Matrix and
what it means f...
You are invited to a party in the cloud,
a public ...
StormRunner Load bringing you fast
and simple perf...
Working with HP LoadRunner and HP
Network Virtuali...
Big news! HP LoadRunner and
Performance Center 12....
LoadRunner licenses now available on
Pronq.com
Overcome the Top 5 DevTestOps
Challenges: Mobile, ...
What happens in Vegas… HP Discover
and performance...
Application performance that wins
customers: the m...
Discover how HP Service Virtualiza
tion drove Darde...
RichardMJBishop on: Working with HP
LoadRunner and HP Network Virtuali..
.
Brandon Williams(anon) on: Anticipate
your load with burst testing with
Perfo...
boba kim(anon) on: Async.
Communications: The WebSocket
protocol made...
Dan Belfer(anon) on: LoadRunner
12.00’s new network profiles make it
ea...
jasonjing on: Virtual Table Server
Enhancements in LoadRunner 12...
Dhondi Kranti(anon) on: Converting
TruClient scripts to Web-protocol
scrip...
Managed Services Dallas(anon) on:
Step-by-step instructions to Provision
Load Genera...
SilviaS on: Announcing HP
LoadRunner and HP Performance
Center...
Speedmaster on: Times, timing and
timeouts in TruClient
Guy_Rosenthal on: TruClient -
Breaking down client times
July 2014
June 2014
May 2014
Font family Font size
QuoteRich Text Preview

3. 7/31/2014 The Protocol ComplexityMatrixand what it means f... - HP Enterprise Business Community
http://h30499.www3.hp.com/t5/HP-LoadRunner-and-Performance/The-Protocol-Complexity-Matrix-and-what-it-means-for-your-load/ba-p/6559424#.U9ng-fmSwsw 3/3
Get a new challenge Get a sound challenge Help with word verification
*Word verification by reCAPTCHA
Post Your CommentCancel
April 2014
View Complete Archives
The opinionsexpressedabove are the personalopinionsof the authors, not of HP. By usingthissite, youaccept the Termsof Use andRulesof Participation
About HP
Contact us
Newsroom
Investor relations
Living Progress
Accessibility
HP Labs
Jobs
Social Media
Consumer support forum
Enterprise business community
Corporate blogs
HP Partners
Become a partner
Find a reseller
PartnerOne
Customer Support
Download drivers
Register your product
Authorized service providers
Training & certification
Product recycling
Home | Email sign-up | Site map | Privacy | Cookies & ad choices | Terms of use | Recalls
© 2014 Hewlett-Packard Development Company, L.P.
View mobile site
United States
Events