Business white paper

Load factor:
performance
testing for
Web
applications
Table of contents

3 A look at load testing

3 In the pursuit of predictability
4 Put your apps through the paces
5 Traits of an automated load testing tool
5 Walking through the process of automated load testing
5 Step 1: Planning the performance testing
6 Step 2: Capturing business process to be tested
7 Step 3: Defining user behavior
8 Step 4: Defining the performance test scenario
9 Step 5: Running the load test scenario and monitor the performance.
10 Step 6: Analyzing results
11 HP LoadRunner software: getting the picture of application performance testing
12 Performance testing and best practices
For an online business to be successful, it has to In the pursuit of predictability
be available at a click of a button— without long The advancement of Web and Mobile applications has changed
wait times, delays, errors, or service interruptions. the way companies promote, market, and sell their products. It
also helped automate key business processes, making it faster
and easier to enter orders, process payments, track data, or even
entertainment. The large volumes of information gathered by Web
applications can help companies define more precise marketing
A look at load testing strategies, target specific customers, as well as offer better, more
personalized service to their clients.
It’s hard to imagine today’s world without the Internet. Websites
bring us news stories and entertainment, help us connect with But the more companies rely on Web applications for running their
people, boost productivity, and provide a convenient storefront for business and generating revenue, the greater the risk of failure
online purchases— anytime, from anywhere in the world, from any due to the complexity behind the Internet. At the early age of
computer or mobile device. Companies increasingly rely on Web online commerce, most companies didn’t invest any time in pre-
applications to automate their core business functions as production performance testing, or at the very best performed
well as enable them to offer more products and services through manual testing—hoping that their infrastructure would support
their websites. the user load after the application went live. Not surprisingly, it
was common to see a website go down right after go live, a big
But for an online business to be successful it has to be available upgrade, or following a promotional campaign and a subsequent
at a click of a button—without long wait times, delays, errors, or increase in traffic. But today’s businesses can’t afford even short-
service interruptions. term interruptions, and the new generation of online-savvy
consumers expects reliable service and timely response at all
Websites must be able to handle sudden increases in traffic or times. If a site cannot accept an order or is taking too long to display
operation volume without compromising the user experience or product selection, customers won’t hesitate to take their business
a company’s ability to quickly and accurately process elsewhere. Tough competition and uncertain economic climate
business transactions. demand that companies pay closer attention to quality, reliability,
availability, and performance of their online applications.
In this paper, we will discuss the importance of measuring
application performance, and explore best practices for load and Today’s Web applications are also more complex than ever before.
performance testing. We will also examine various components Scaling a multifaceted, integrated infrastructure from end to end
of a successful performance testing process as well as look at the means managing the performance and capacities of individual
attributes of a reliable performance testing software solution. With components within each tier—as well as measuring the overall
that, we’ll provide an overview of HP LoadRunner software, the transaction response times of the entire system.
industry-leading performance validation tool.

Figure 1: An example of a complex Web infrastructure

Internet

Clients Routers Switches Web servers Internet Load Application Database servers
firewall balancers servers and other
and Applications database servers
connecting
with external
applications

3
Figure 2
The VuGen allows you to emulate production workloads on an entire system.

Controller Simulated users Internet/WAN Web server Application servers Database

This complexity triggers many uncertainties about the integrity Manual testing is also not the most practical option because in order
and performance capabilities of a Web application. Will it provide to accurately diagnose problems, you must repeat tests multiple
consistently fast response times for all users—regardless of where times: first to identify performance problems, tune the system, and
they are coming from or what type of connection they are using? then retest to verify that tuning has had a positive impact. Manual
Can an application sustain a large user volume? Will it remain fast testing is a option for business failure.
and reliable after a sudden increase in the number of users? Is there
sufficient hardware on each tier to handle high traffic volumes? With automated performance testing tools, you can automatically
Can all the interoperable pieces of the system work reliably run tests and measure results. You can also easily and cost-
together? What is the maximum capacity of the application? To effectively create and maintain scripts and scenarios to maximize
answer these questions, you must be able to predict how your Web reuse between test runs and accurately compare results. Automated
applications will behave in a production environment before going testing tools help reduce the risk of human error during testing. As
live, and continue to measure and monitor your system throughout a result, automated performance testing has become the preferred
its lifecycle. choice for companies of all types and sizes for performance testing
of their business critical applications. Automated testing tools
typically use three major components to execute a test:
Put your apps through the paces. • A control console that organizes, drives, and manages the load
and use behavior
A typical response to growing traffic on your website is to add
more hardware to each component of the system. However, • Virtual users (Vusers)—processes used to imitate a real user
such random attempts to improve performance often lead to performing a business process on a client application
overbuying hardware—and not necessarily to better performance • Load servers (used to run the Vusers)
and scalability since many times the application was not designed
to be elastic. The only way to accurately predict system behavior Using these components, automated load testing tools can:
is to execute performance testing in your applications end to end, • Replace manual testers with automated Vusers
measure response times from the end-user perspective, and • Simultaneously run many Vusers on a single load generating
diagnose and remedy any performance issues prior to going live. machine from a unique location or from multiple locations around
the globe
Application performance testing is the way to measure your
Web application’s ability to conduct multiple transactions • Automatically measure transaction response times and monitor
simultaneously while maintaining adequate response times. the infrastructure components
It also helps you isolate bottlenecks in any component of the • Easily repeat load scenarios to validate any changes you make to
network infrastructure to accurately pinpoint potential problems. optimize performance
Two common approaches to performance testing methods are
manual and automated testing. Unfortunately, manual testing This advanced functionality definitely allows you to save time
has several inherent challenges, such as: and resources.
• Difficulty emulating the behavior of thousands of concurrent users
• Coordinating user operations
• Accurately measuring response times
• Comparing results between test runs, scenarios, and iterations.

4
Table 1
Accuracy and scalability are key attributes of an automated performance testing solution.

Accuracy Scalability and Capacity Management

Record load testing scripts against a real client application. Generate more Vusers that can be run on a single machine before exceeding its capacity.

Capture protocol-level communication between the client application and the Generate more hits per second against a Web server.
rest of the system.

Provide flexibility and the ability to define configurations for user behavior (for Manage thousands of Vusers.
example, think times, connection speeds, cache settings, iterations).

Verify that the requested content returns to the browser to facilitate a Increase the number of Vusers in a controlled manner.
successful transaction.

Show detailed performance results that can be easily understood and analyzed to Simulate the effect of scaling out to remote locations over wireless area networks (WANs).
identify the source of the problem.

Measure end-to-end response times.

Use real-life data.

Synchronize Vusers to generate peak loads.

Monitor different tiers of the system with less intrusion.

Traits of an automated performance Step 1: Planning the performance testing

testing tool This step is critical to interpreting your testing needs and is used
to determine whether the system can scale and perform to your
The primary goal of load testing tools is to accurately predict specifications. At this stage, you need to translate your user
system performance and isolate performance issues. To identify requirements into performance testing objectives. A thorough
performance problems, performance testing tools monitor key evaluation of the requirements before beginning load testing can
system-level components and find bottlenecks during the test run. help provide realistic test goals and conditions.
Accuracy is defined by how closely an automated tool can emulate
real-user behavior. A scalable tool is able to simulate a greater load • Identify your key performance goals.
using fewer resources. These may include determining which processes and transactions
to test, which system components to use in the test, and the
Walking through the process of number of concurrent connections and hits per second to expect
against the application. You also want to look at the overall end-
automated performance testing to-end business processes to clarify which ones need to be tested.
For example, an online book retailer may flag the “buy book”
With a disciplined approach to performance testing, you can
transaction for the purposes of a test. The overall transaction can
optimize resources, better predict hardware, software, and network
include browsing the book selection, choosing a book to purchase,
requirements, and set performance expectations to meet customer
entering payment and shipping information, and completing the
service level agreements (SLAs). You also must be able to repeat
purchase. By clearly defining the load testing objectives, you can
the testing process regularly in order to verify that application
provide a concise outline of the SLAs and mark the goals to be
or infrastructure changes did not negatively impact system
achieved with testing.
performance. Outlined below is a step-by-step overview of the
automated performance testing process: • Defining the Data for testing
You need to define what input data is going to be used for testing.
This data can be created dynamically or sourced from existing
lists—such as a customer database. By using realistic data, you
can create more accurate load tests and better predict system
performance in production.

5
 • Defining testing approach
You must determine the appropriate strategy for testing
applications. You can choose one or more types of performance
testing: load testing, stress testing, and capacity testing. Load
testing is typically used to gauge how an application will perform
under a specific user load. Your goal is to determine whether your
Web application can sustain this requested number of users with
acceptable response times. Stress testing is the way to validate
an application’s stability and reliability by applying a load for an
extended period of time. Capacity testing helps you determine
the maximum number of users who can access your application
simultaneously before experiencing system failure.

• Review Infrastructure for Application under test and test

execution.
You need to cultivate a solid understanding of your system’s
architecture, including:
−− Defining the types of routers and network connectivity you’re
using in the network setup
−− Determining whether you’re using multiple servers
−− Establishing whether you’re using load balancers as part of your
IP network
−− Determining which servers are configured into the system (Web,
application, and database) reducing scripting time and maintenance by up to 80 percent.
These scripts are also easier to maintain, allowing you to easily
You must also know which resources are available to run the Vusers visualize what is happening in each statement, and focus on the
by deciding whether you have sufficient numbers of load generators elements that need to be modified for another test.
or test machines to run the appropriate number of Vusers. You
must also determine whether the testing tool has multi- threading Once the script has been generated, you can add logic
capabilities and can increase the number of Vusers being run. and intelligence to make it more realistic imitating a real
Ultimately, your goal is to reduce your consumption of system user interacting with an application. Logic can be added
resources while increasing the number of Vusers. at the transaction level, as well as using verification and
parameterization techniques.
Step 2: Capturing business process to be tested
−− Transactions: Transactions represent a series of operations
Use a script recorder to capture all the business processes into that must be measured under load conditions. A transaction
test scripts, which are often referred to as Vuser scripts or Vusers. can be a single operation by a customer or a complete business
A Vuser emulates the real user by interacting with the application process leading through several screens, such as the end-to-
as a client. You must identify and record all the various business end process of selecting, comparing, and purchasing a product
processes from start to finish. This can help you determine the online.
amount of time you need to measure the performance of a
business process. −− Verification: VuGen allows you to insert verification checkpoints
using ContentCheck, which verifies that the application
• Creating virtual user script with HP LoadRunner functions as expected by analyzing the returned page. If the
To create a Vuser script, you can record a business processes verification fails, HP LoadRunner can log the error and highlight
with HP LoadRunner Virtual User Generator (VuGen). VuGen the reasons for the failure (for example, broken link, missing
is a component that runs on a client desktop to capture the images, erroneous text, and so on).
communication between the client application and the server. Parameterization: To accurately simulate real-user
VuGen can emulate the exact behavior of a real browser by behavior, HP LoadRunner Vusers use varying sets of
sending various protocol requests to the server. data during load testing that replace constant values in
HP LoadRunner’s Click and Script technology helps you easily the script with variables or parameters. The Vuser can
record scripts at the user-interface level. HP LoadRunner substitute the parameters with values from a data source,
automatically captures the most valuable scripting information such as flat files, random numbers, date/time, and so on.
to create succinct, visually intuitive, easy to understand scripts, This allows you to test a business process with varied sets
of data.

6
Figure 3 Figure 4
This generic graph shows application performance under load. In this This generic graph shows transactions that passed or failed. In this example,
example, the application response times increase sharply once the number transaction number two failed approximately one-third of the time.
of concurrent users reaches 7,500. Depending on how critical this transaction is, such high failure rate is likely
not acceptable for the business.

16
120

Number of transactions
14
100
Response time (sec)

12
80
10
60
8
40
6
20
4
0
2
1 2 3 4 5 6
0
1 2 3 4 5 6 7 8 9 10 Business transaction
Number of users (thousands)
Pass Fail

Step 3: Define user behavior. −− Emulate cache: Emulates a user browsing with a specific cache
Run-time settings define the way the script runs in order to size. Caching can be turned off based on server requirements.
accurately emulate real users. Settings can configure think times, −− Browser emulation: Enables you to specify which browser the
connection speeds, and error handling rules. Think times can Vuser simulates.
vary depending on your customer’s actions and complexity of a −− Number of connections: Allows the Vuser to control the number
transaction. For example, a customer can move quickly through the of connections to a server.
account information update page, while taking longer comparing
−− IP spoofing: Tests the performance impact of IP-dependent
product options or entering payment information.
components by assigning Vusers their own IP addresses from
Your system’s response times will also vary depending on the users’ the same physical machine.
connection speed. WAN emulation accurately imitates a variety of −− Iterations: Commands repetition of Vuser scripts and paces
connection options at varying network bandwidth and latencies. Vusers, instructing how long to wait between intervals. Iterative
This can help you determine how the underlying network affects testing defines the amount of work a user does based on the
application response times. Because errors can arise throughout number of times a process is performed using varying data.
a scenario and impede testing, you also need to configure error −− Error handling: Regulates how a Vuser handles errors during
handling. You can configure Vusers to handle these errors so you can script execution. HP LoadRunner can enable the continue on
run the tests uninterrupted. Network communications errors can error feature when the Vuser encounters an error during replay.
also profoundly influence application response times. You can also
−− Log files: Stores information about a Vuser’s server
configure WAN emulation to introduce underlying network errors to
communication. Standard logging maps all transactions,
understand their impact and measure the application’s tolerance
rendezvous, and output messages. Extended logging also
for them.
tracks warnings and other messages.
• Creating user behavior with HP LoadRunner
HP LoadRunner provides comprehensive run-time settings to
configure scripts that emulate the behavior of real users. Below
are some examples of run-time settings:
−− Think time: Controls the speed at which the Vuser interacts
with the system by including pauses of think times during test
execution.
−− Connection speed: Simulates a user connected to the system
from different network speeds.

7
Figure 5
How HP LoadRunner works

Real-time monitors capture

2 Hundreds of virtual users 3 performance data across all
perform real-life
tiers, servers and network
transactions to simulate
resources and display
production traffic
information on the Controller

4 Results are stored in a

database repository
allowing users to
generate reports and
1 The Controller is a perform analysis
central console from
which the load tests are
managed and monitored

Step 4: Defining the performance tests scenarios multiuser load test scenarios. Using five easy-to-follow screens,
The performance test scenario contains information about the the scenario wizard leads you through a process of selecting the
groups of Vusers that can run the scripts and the load machines workstations that can host the Vusers, as well as the test scripts
on which the groups are running. To run a successful scenario, you to run.
must first categorize your customers into groups based on their
During this step-by-step process, you also create simulation
transactions. Then, you need to define and distribute the total
groups of Vusers. The HP LoadRunner scheduler is used to ramp
number of Vusers. You can assign a varying number of Vusers to
Vuser numbers up or down in order to position Vusers in both the
individual business processes to emulate user groups performing
ready state and the running state. For example, you may want to
multiple transactions. One group may be searching for a book, while
gradually increase the number of customers logging onto your site
the second and third groups are entering payment information or
with a fixed batch size. This is referred to as the ready state. This
shipping addresses. After Vuser groups have been assigned, you
method helps avoid unnecessary strain on the system.
must determine which load-generating machines the Vusers can
run on. You can add load generator machines to the client side of The scheduler also manages scheduling and features an
the system architecture to run additional Vusers. Finally, you need automated process that allows the user to run the script without
to specify how the scenario will run. You can run the Vuser groups being present. In real time, this would be similar to running a script
either in staggered or parallel formation. Staggering the Vusers during off-peak hours—such as 6 p.m. to 6 a.m. To schedule a test,
allows you to examine a gradual increase of the user load to a peak. you simply click the Run Scenario button and enter the desired
• Creating load testing scenarios with HP LoadRunner starting time.
HP LoadRunner Controller is used to create scenarios, providing • Create network impact tests.
you with complete visibility of the tests and the Vusers from a The network test uses information about where the groups of
single point of control. The Controller facilitates the process of Vusers can be located relative to the server. During the test, only
creating a load test scenario by allowing you to: the network characteristics—such as bandwidth availability,
−− Assign scripts to individual groups contention, latency, errors, and jitter—can change; the
−− Define the total number of Vusers needed to run the tests number of Vusers in this test remains constant. By staggering
the decreases in network bandwidth or increases in latency,
−− Define the host machines on which Vusers are running
errors, and jitter, you can understand their relative influence
In addition, HP LoadRunner offers a scenario wizard, a scheduler on application behavior. This data can be used to set network
and TurboLoad to enhance your experience during testing. The requirements for the application when it is deployed. You can
HP LoadRunner scenario wizard allows you to quickly compose conduct this kind of testing directly over the network to remote

8
Figure 6
The VuGen allows you to capture business processes to create Vusers.

Business process

Browser

Application

VuGen recorder Scripts

locations, but for testing purposes it is generally more practical to • Run the load test scenario and monitor the performance
emulate the network where you can easily establish a variety of with HP LoadRunner
conditions using WAN emulation. This can allow you to predict the Once the scenario is built, you are ready to run the test. The HP
performance for remote users. LoadRunner controller provides a suite of performance monitors
that can monitor each component of a multi-tier system during the
• Defining Load Testing per locations with HP LoadRunner load test. By capturing performance data over the entire system,
HP LoadRunner has the ability to handle WAN emulation, so you can correlate this information with the end-user loads and
you can use the same virtual-user scripts used in the previous response times to identify bottlenecks. HP LoadRunner provides
steps for network impact tests. Network characteristics such performance monitors for all parts of the system under test—
as connection speed, latency, and error rates are modified for including Web servers, application servers, databases, ERP and
groups of Vusers that are simultaneously emulated during a CRM systems, firewalls, and load balancers. HP LoadRunner can
single test run. You can then accurately determine the impact of identify hardware limitations and software configuration issues
the network on response time on the different groups, as well as that might otherwise go undetected. All performance monitors
the sensitivities of the application to the network. You can record are non-intrusive and hardware and OS independent, so they do
expected response time data and network requirement set for use not require that agents be installed on the remotely monitored
later when the application goes live. servers. To look deeper into each transaction—from end-user
response time all the way down to the application method level—
Step 5: Running the load test scenario and monitor the you can use HP Diagnostics software. During a performance test,
performance. HP Diagnostics traces business processes from the client side
You can view the application’s performance at any time during the across all tiers of the infrastructure, and then breaks down each
test using real-time monitoring. Every component of the system transaction response time into time spent in the various tiers and
requires monitoring: the clients, the network, the Web server, the within individual components. HP Diagnostics provides:
application server, the database, and all server hardware. You can −− An intuitive, easy-to-use view of how individual tiers,
detect performance bottlenecks early during testing using real- components, memory, and SQL statements impact overall
time monitoring. You then have the ability to view the performance performance of a business process under load conditions.
of every single tier, server, and component of the system during
−− The ability to more easily find components relevant to a specific
testing. As a result, you can instantly identify performance
business process under test.
bottlenecks during load testing. This can allow you to accelerate the
test process and achieve a more stable application. −− The ability to triage and find problems effectively with business
context, enabling teams to focus on problems impacting
business processes.

9
 Figure 7
HP LoadRunner and HP Diagnostics allow you to monitor system performance during tests, diagnose performance bottlenecks as they occur, and identify root
cause of the issues.

Step 6: Analyzing results. bottlenecks. In addition, HP LoadRunner analysis uses a series

Collecting and processing test data is an essential step in isolating of sophisticated graphs and reports that help you answer such
and resolving performance bottlenecks. The analysis can produce questions as: What was the Web server’s CPU memory when the
a series of graphs and reports that help summarize and present the system was under a load of 5,000 simultaneous users? How many
end-to-end test results. total transactions passed or failed after the completion of the
load test? How many hits per second can the Web server uphold?
• Analyzing the results with HP LoadRunner Analytics What were the average transactions times for each Vuser? Figures
Analyzing results is possibly the most important step in the load 8 and 9 show examples of HP LoadRunner analysis graphs. HP
testing process. Until this point, you have been able to precisely LoadRunner provides a variety of performance graphs, such as the
record and play back the actions of a real user and look into ones listed below:
potential bottlenecks using performance-monitoring features.
Now, you can take steps to fix any problems that have been −− Percentile: analyzes percentage of transactions that were
identified during testing. performed within a given time range

First, a network specialist (such as a database administrator or −− Performance under load: indicates transaction times relative
consultant) can make the necessary adjustments to the system. to the number of Vusers running at any given point during the
Then you need to rerun the scripts to verify that the changes have scenario
taken place. −− Transaction performance: displays the average time taken to
perform transactions during each second of the scenario run
Finally, you can measure the amount of improvement the −− Transaction performance summary: displays the minimum,
system has undergone by comparing results from before and maximum and average performance times for all the
after testing. transactions in the scenario
The HP LoadRunner analysis component provides a single −− Transaction performance by Vuser: displays the time taken by
integration environment that collectively gathers all the data an individual Vuser to perform transactions during the scenario
generated throughout the testing cycle. HP LoadRunner analysis
−− Transaction distribution: displays the distribution of the time
provides advanced capabilities that let you compare results
taken to perform a transaction
across scenarios and drill down into network layers to identify

10
Figure 8 Figure 9
This sample activity graph displays the number of completed transactions This graph displays the number of transactions that passed, failed, aborted,
(successful and unsuccessful) performed during each second of a load test. or ended with errors. For example, these results show the “Submit Search”
This graph helps you determine the actual transaction load on your system business process passed all its transactions at a rate of approximately 96
at any given moment. The results show that after six minutes an application percent.
is under a load of 200 transactions per second.

HP LoadRunner also offers two types of Web graphs: Using minimal hardware resources, HP LoadRunner emulates
−− Connections per second: shows the number of connections hundreds or thousands of concurrent users to apply production
made to the Web server by Vusers during each second of the workloads to almost any application platform or environment. HP
scenario run LoadRunner stresses an application from end-to-end—applying
consistent, measurable, and repeatable loads—then uses the data
−− Throughput: shows the amount of throughput on the server to identify scalability issues that can affect real users in production.
during each second of the scenario run HP LoadRunner analysis
includes a correlation of results feature to enhance the user As it drives load against the system, HP LoadRunner captures
analysis process for the data. This allows you to custom design a end-user response times for business processes and transactions.
graph beyond the basics using any two metrics. As a result, you Non-intrusive, real-time performance monitors obtain and display
can identify and troubleshoot performance problems performance data from every tier, server, and system component.
more quickly. Strong analysis capabilities help isolate performance bottlenecks
quickly and efficiently.
HP LoadRunner software: getting the
picture of application performance
HP LoadRunner software is the industry-standard solution for
application performance testing. Because HP LoadRunner is
extremely flexible customers can design the performance testing
based as their own specific project requirements. HP LoadRunner
helps you obtain an accurate picture of end-to-end system
performance before going live. It helps:
• Verify that new or upgraded applications meet specified
performance requirements
• Identify and reduce performance bottlenecks during the
development lifecycle
• Pinpoint end-user, system-level, and code-level bottlenecks
rapidly and with ease

11
Test against a broad range of HP LoadRunner Key features and benefits
applications and protocols • Supports performance testing of new technologies together
with your existing, legacy applications
HP LoadRunner supports performance testing for a wide range
• Accurately tests a mix of mobile and Internet users
of application environments and protocols, including Ajax, Flex,
Microsoft ® Silverlight, Web, SOA, Web services, RDP, Database, • Decreases the risk of deploying systems that do not meet
Terminal, Citrix, Java, .NET, Oracle, and SAP. An updated and performance requirements
easy-to-use scripting and debugging engine leverages data • Reduces hardware and software costs by accurately predicting
format extensions and correlation studio to make scripting application scalability and capacity
faster and easier. • Helps you establish intelligent service-level agreements before
applications go live
To enable load testing earlier in the application lifecycle, HP
LoadRunner integrates with the leading J2EE, Microsoft ® Visual • Shortens test cycles to accelerate delivery of high‑quality
Studio, and Microsoft .NET environments. This integration lets you applications
create HP LoadRunner scripts directly within the IDE, so developers • Pinpoints end-user, system-level, and code-level bottlenecks
can participate in the performance testing efforts earlier. rapidly and with ease
• Reduces the cost of defects by testing earlier in the
As part of the lifecycle approach to application testing,
application lifecycle
HP LoadRunner is also integrated with HP QuickTest Professional,
HP Quality Center, and HP Application Performance Center
(APM) software. To discover how you can measure application
Leveraging these complementary solutions together with HP
performance using load testing software from HP,
LoadRunner provides a comprehensive approach for managing the please visit hp.com/go/loadrunner.
overall testing process, measuring release risk, and increasing the
reuse of testing assets from pre-release to production.

Performance testing and best practices For more information

You can’t afford to take chances with your Web application To generate real-life loads and identify and diagnose problems, visit
performance and reliability. Your company’s success, revenue, and hp.com/go/performancevalidation.
reputation often depend on the IT applications’ ability to accurately
support business processes and deliver positive experience for all Connect with peers and HP Software experts
users at all times. at hp.com/go/performancecommunity.

The intricacy of today’s Web technologies, high traffic volumes, For an overview of HP software services, visit
complexity of transactions, and frequent changes demand that managementsoftware.hp.com/service.
you take a lifecycle approach to performance testing. Make it a
To access technical interactive support, visit Software Support
part of the delivery process for all applications. By following the
Online at hp.com/managementsoftware/services.
best practices and using the right tools for planning, building,
maintaining, and reusing your performance testing assets, you will To learn more about HP Software Customer Connection, a one-stop
greatly reduce the risk of failure and enable that your applications information and learning portal for software products and services,
remain scalable and reliable throughout the lifecycle. visit hp.com/go/swcustomerconnection.

Get connected
hp.com/go/getconnected
Get the insider view on tech trends,
support alerts, and HP solutions

© Copyright 2007, 2010, 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and
services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors
or omissions contained herein.

Microsoft is a U.S. registered trademark of Microsoft Corporation. Oracle and Java are trademarks of Oracle and/or its affiliates.

4AA1-3944ENW, Created August 2007; Updated June 2012, Rev. 2