Introduction of the LoadRunner Solution

• LoadRunner reduces the personnel requirements by replacing human users with virtual users
or Vusers. These Vusers emulate the behavior of real users– operating real applications.

• Because numerous Vusers can run on a single computer, LoadRunner reduces the hardware
requirements.

• The LoadRunner Controller allows you to easily and effectively control all the Vusers–from a
single point of control.

• LoadRunner automatically records the performance of the client/server system during a test.
You can choose from a wide variety of graphs and reports how you want to view the
performance data.

• LoadRunner checks where performance delays occur: network or client delays, CPU
performance, I/O delays, database locking, or other issues at the database server.
LoadRunner monitors the network and server resources to help you improve performance.

• Because LoadRunner tests are fully automated, you can easily repeat them as often as you
need.

How to Use LoadRunner

Using LoadRunner, you divide your client/server performance testing requirements into scenarios.

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.

In the scenario, LoadRunner 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.

To emulate conditions of heavy user load, you create a large number of Vusers that perform a series of tasks. For example, you can observe how a server behaves when one hundred Vusers simultaneously withdraw cash from the bank ATMs. To accomplish this, you create 100 Vusers, and each Vuser:

• enters an account number into an ATM

• enters the amount of cash to withdraw

• withdraws cash from the account

• checks the balance of the account

• repeats the process numerous times

Introduction of LoadRunner Vuser Technology

The actions that a Vuser performs during the scenario are described in a Vuser script. When you run a scenario, each Vuser executes a Vuser script. The Vuser scripts include functions that measure and record the performance of the server during the scenario.

To measure the performance of the server, you define transactions. Transactions measure the time that it takes for the server to respond to tasks submitted by Vusers. For instance, you can define a transaction that measures the time it takes for the server to process a request to view the balance of an account and for the information to be displayed at the ATM.

Insert rendezvous points into Vuser scripts to emulate heavy user load on the server. Rendezvous points instruct multiple Vusers to perform tasks at exactly the same time. For example, to emulate peak load on the bank server, you insert a rendezvous point to instruct 100 Vusers to simultaneously deposit cash into their accounts.

You use the LoadRunner Controller to manage and maintain your scenarios. Using the Controller, you control all the Vusers in a scenario from a single workstation.

When you execute a scenario, the LoadRunner Controller 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

Vuser Types

LoadRunner has various types of Vusers. Each type is designed to handle different aspects of today’s client/server architectures. You can use the Vuser types in any combination in a scenario in order to create a comprehensive client/server test.

The following Vuser types are available:

• GUI (Windows and UNIX)

• RTE (Windows and UNIX)

• Database *(CtLib, DbLib, Informix, Oracle, and ODBC)

• Web*

• TUXEDO*

• APPC*

• Windows Sockets*

• Baan

• Java

• DCOM

• PeopleSoft

Difference Between Static and Dynamic Webpages

Difference between Static and Dynamic webpages:-

1.static Web pages contain the same prebuilt content each time the page is loaded, while the content of dynamic Web pages can be generated on-the-fly.

2. static webpages include HTML….but Dynamic webpages include Java,JSP

3.Dynamic pages contain “server-side” code, which allows the server to generate unique content each time the page is loaded.
For example:- the server may display the current time and date on the Web page

4. We can easily identify Static and Dynamic webpages through their File extensions in the url
Static WebPages contains extension== “.htm” or “.html,”
Dynamic WebPages Contains extension==”.php,” “.asp,” or “.jsp,”

Introduction of Static Pages

Most of these advantages and disadvantages apply to normal HTML pages in particular.

Advantages

• Quick and easy to put together, even by someone who doesn’t have much experience.
• Ideal for demonstrating how a site will look.
• Cache friendly, one copy can be shown to many people.
•

Disadvantages

• Difficult to maintain when a site gets large.
• Difficult to keep consistent and up to date.
• Offers little visitor personalization (all would have to be client side).