How to calculate doc download time in LoadRunner

Lets says that we have a document in one of the pages that we record in VuGen and we have to capture the time it takes to download only that file, then Use the below steps after the step which downloads the file.
Note that the RecContentType=application/pdf for the step
 
web_url("BCAction.do",
        "URL={url}//BCAction.do?choice=display&ctno=1234567890",
        "Resource=1",
        "RecContentType=application/pdf",
        "Referer=",
        "Snapshot=t24.inf",
        LAST);
 time = web_get_int_property(HTTP_INFO_DOWNLOAD_TIME);      
 lr_output_message("The time in ms to download CSS PDF is: %d",time);

Some more information about Web_get_int_property
The web_get_int_property function returns specific information about the previous HTTP request. 

The meaning of the return value depends on the HttpInfoType argument. HttpInfoType can be any of the following options. The first constant in each pair (HTTP_*) is for C, the second (object.HTTP_*) is for object oriented languages(Java scripts).

HTTP_INFO_RETURN_CODE or object.HTTP_INFO_RETURN_CODE
The return code in HTTP response header. 

HTTP_INFO_DOWNLOAD_SIZE or object.HTTP_INFO_DOWNLOAD_SIZE
The size (in bytes) of the last download, including the header, body, and communications overhead (for example, NTLM negotiation).

HTTP_INFO_DOWNLOAD_TIME or object.HTTP_INFO_DOWNLOAD_TIME
The time in (milliseconds) of the last download.

HTTP_INFO_TOTAL_REQUEST_STAT or object.HTTP_INFO_TOTAL_REQUEST_STAT
Returns the accumulated size of all headers and bodies since the first time web_get_int_property was issued with HTTP_INFO_TOTAL_REQUEST_STAT.

HTTP_INFO_TOTAL_RESPONSE_STAT or object.HTTP_INFO_TOTAL_RESPONSE_STAT
Returns the accumulated size, including header and body, of all responses since the first time web_get_int_property was issued with HTTP_INFO_TOTAL_RESPONSE_STAT

This function is supported for all Web scripts, and for WAP scripts running in HTTP mode only. It is not supported for WAP scripts running in Wireless Session Protocol (WSP) replay mode

How to correlate a value with dynamic boundaries in VuGen

If you are checking this post, seems the left and right boundaries are killing your time. Lets check how to deals with those dynamic boundaries using the text flags of VuGen.

You can use one of the following flags after the text, preceded by a forward slash: /IC to ignore the case. /DIG to interpret the pound sign (#) as a wildcard for a single digit. /ALNUM to interpret the caret sign (^) as a wildcard for a single US-ASCII alphanumeric character. There are three syntaxes: ALNUMIC to ignore case, ALNUMLC to match only lower case, and ALNUMUC to match only upper case.
eg: email\u003d\"notification+mkuw__3d@facebookmail.com In the above server response if you have to capture the highlighted part(in RED), the left and right boundaries have some alphanumeric chars and if they are dynamic then you have to follow the below approach.
web_reg_save_param("account_notify",
        "LB/DIG=email\u00#d\\"",
        "RB/DIG=__#d@facebookmail.com",
        "Ord=1",
        "Search=Body",
        LAST);
and for instance lets say that "u003d" in the left boundary itself is dynamic, then below will be our approach.
web_reg_save_param("account_notify",
        "LB/ALNUMIC=email\^^^^^\\"",
        "RB/DIG=__#d@facebookmail.com",
        "Ord=1",
        "Search=Body",
        LAST);
ALNUMIC means the boundary is an alphanumeric and IC asks it to ignore the case(upper or lower)

Different Performance tests including Peak Performance and Stability

Peak performance test:-
This test is done to analyze the application peak performance. To achieve peak performance we have to slowly ramp up the users and see the response times and TPS with increase in users. At a certain point TPS will stay flat and response times increase and in some cases TPS decreases and thus increases response time with increase in users.
The point where TPS starts staying flat is the peak performance point and this is how we do peak performance test.


Break point test :-
We do break point test in the same line as peak performance but we don’t stop the test once we reach peak point, we continue to increase users and see when the application breaks, that means we see the errors per sec graph along with vusers and transaction response time and transaction per sec graphs.
As we increase load on the application beyond peak performance, application cannot handle it anymore and at some point it starts throwing errors and you see a spike in the errors per sec and that's the break point for that application for the given test conditions.

Typical reasons for the application to reach breakpoint:- 
1. Queue length is increasing and the wait time at that queues for new request reach max wait time and thus will throw error
2. No Connections available to take new requests
3. Threads are busy and are waiting for other system resources
4. Concurrency of the objects being instantiated reached its limit
5. DB connections are full
6. JVM heap memory is not sufficient.


Stability test:-
We have to know the peak performance point to perform stability. Once we are done with peak performance test and know the max number of user’s app supports we run stability test for an hour or 2 at the peak point or 5-20% more load than peak point. Note that we assume break point does not come immediately after peak performance point.
eg - if peak performance is at 90 users and break point is 100 users then we can run stability at 95 or 90

As part of performance testing, other tests we do are Regression, Load, Stress, Soak/Endurance

Microsoft IIS Monitoring Through LoadRunner

This Web Server Resource monitor displays statistics about the resource usage on the Microsoft Internet Information Server (IIS) during the scenario run.

To obtain data for this graph, you need to configure the MS IIS online monitor (from the Controller) and select the measurements you want to display, before running the scenario. You select measurements for the Microsoft IIS Server monitor using the MS IIS dialog box.

Note: To monitor an IIS server through a firewall, use TCP, port .

•  Adding a Machine to Monitor on page
• Configuring the Microsoft IIS Monitor 
• Microsoft IIS Performance Counters 

 

Adding a Machine to Monitor

In order to monitor the Microsoft_IIS server from the Controller, you need  to add the machine and the measurements you want to monitor.

To add a machine to the Controller:

1. Click the MS IIS graph in the graph tree, and drag it into the right pane of the Run view.

2. Right-click the graph and select Add Measurements, or click anywhere on  the graph and choose Monitors > Add Measurements. The MS IIS dialog box opens.In the Monitored Server Machines section, click Add. The Add Machine dialog box opens.

3. Enter the server name or IP address of the machine you want to monitor.

Select the platform on which the machine runs, and click OK.

4.In the Resource Measurements on: section of the MS-IIS dialog box, the default measurements are displayed.

•  To delete a measurement from the default list, select the measurement and click Delete.
• To select additional measurements, click Add. A dialog box opens displaying all the available measurements.

Note: To change the default counters for the Microsoft IIS Server monitor, see “Changing a Monitor’s Default Counters”.

5.Continue with Configuring the Microsoft IIS Monitor below.

Configuring the Microsoft IIS Monitor:

After you have added the machine that you are monitoring, you configure the monitor by choosing which objects to monitor on the machine.

1. When you click Add to add a measurement, the MS IIS dialog box opens displaying the Web Service object, its counters, and instances opens.





For each measurement, select an object, counter, and instance, and then  click Add, as described in “Understanding the MS IIS Dialog Box” on.

Note: To change the default counters for the Microsoft IIS Server monitor,  see “Changing a Monitor’s Default Counters”.

2. Add all the desired resources to the list, and click Close.
3. Click OK in the MS IIS dialog box to activate the monitor.

Understanding the MS IIS Dialog Box

The MS IIS dialog box lets you select the items to monitor on the MS IIS  server.

•  Object: Select the object being monitored on the specified machine.
•  Counters: Select a resource counter to monitor. Select multiple counters using the CTRL key. For an explanation of each counter, click Explain. 
• Instances:If multiple instances of the selected counter are running, select one or more instances to monitor for the selected counter.

Creating a Basic Script from Server Traffic (Web-Services) in Load runner

While dealing with web-services based application(s), sometimes it is not possible to capture the user actions using Vugen. This might be due to application nature or something else. In this case there is an utility to create a basic LR script by using "analyze traffic" feature of web-services based script.

The actions needed for this are as follows:

1. Create a network capture file
2. Open a new web-services script in Vugen and import the WSDL.
3. Use the analyze traffic option to generate the script.

Create the capture file:

You can obtain a capture file using the command line utility or any existing
capture tool.
There is a utility in Vugen's bin directory called as "lrtcpdump.exe"which can be used to create the network traffic capture file.

To create a capture file on a Windows platform follow the steps

1.Choose Start > Run, type cmd and click OK to open a command window.
2. Drag in or enter the full path of the lrtcpdump.exe program located in the product’s bin directory.
3. Provide a file name for the capture file using the following syntax: lrtcpdump -f
4. lrtcpdump prompts you to select a network card. If there are multiple interface cards, it lists all of them. Type in the number of the interface card (1, 2, 3 etc.) and click Enter.
5. Perform typical actions within your application.
6.Return to the command window and click Enter to end the capture session.

Use the analyze traffice option to generate the script.

1.Choose File > New and click New Single Protocol Script in the left pane.
2.Select the Web Services protocol and click OK.
3.Click the Analyze Traffic button or choose Vuser > Analyze Traffic. The wizard opens.
4.Add the WSDL file location/URL and select next (optional)
5.On the next page provide the capture file information and click Finish

This will generate your basic web-services script for the action(s) performed. Then you can do your customization (parametrization and correlation) to the script.

Note: Please make sure that while making the capture file, all other TCP application(s) are closed. Only the application under test should be opened.

How to specify the number of iterations when executing a VuGen script from the command line

Use lr_get_attrib_string() to read the command line argument

VuGen has an -infiniteiterations option to specify the script to run infinite times. There is not currently a command line option available to specify the exact number of iterations.

1. In VuGen, select Run-Time Settings -> Additional attributes.
2. Create an argument name (for example, "iter"), and give a default argument value of 2.
3. Use a for loop in the Action item, and repeat the action "iter" number of times.

Example:

Action()
{
int iterations, i;
iterations = atoi(lr_get_attrib_string("iter"));

for (i = 1; i <= iterations; i++)
lr_output_message("This is a test, iteration is %s", lr_get_attrib_string("iter"));
return 0;
}

Note:
If you have any parameters declared in the script that are set to change values for each iteration, you may want to change them to each occurence so it takes a different value for each time it runs.

From the command line you can now run the script as

"LoadRunner install dir" \bin\mmdrv.exe -usr "path to .usr file" -out "path_to_output_directory" -iter "no_of_iters"

If Controller crashes in load runner ?

Here i am presenting you that what are the steps that we have to take when the controller crashes.

Make sure that you login as a local administrator

Login to the Controller machine with a local administrator account. Using domain account may cause unexpected behaviors.

Make sure that there are sufficient Disk Space
Make sure that you have enough disk space available on the controller and load generators. During scenario execution, the events are written onto the Load Generator machines and are saved locally until the scenario finished; where results are send back to the Controller. If the machine does not have enough disk space, it can cause problem.

Make Sure that the Temp directory is outside the User’s default Temp directory.

Make sure that there are sufficient memory available

To check available memory on a machine:
Right-click the status bar, and select Task Manager. Select the Performance tab to check the physical memory available. Select the Processes tab to check which processes have high memory consumption in the CPU column.

To free up memory: 

1.Close any unnecessary processes running on the machine, and try running the scenario again.
2.Restart your computer.
3.If the problem persists, reduce the number of virtual users that you are running on the same machine.

To enlarge the size of your virtual memory: 

1. Click Start -> Settings -> Control Panel -> System.

• For Windows 2000, select the Advanced tab, and click Performance Options. 
• For Windows NT, select the Performance tab. 

2. In the Virtual memory section, click Change. 

3. In the Drive list, click the drive that contains the paging file you want to change.
Under Paging file size for selected drive, type a new paging file size in megabytes in the Maximum size (MB) box, and then click Set.

To boost performance, and allow more Virtual Users to run on the load generator machine:
On Windows 2000 machines, select Start -> Settings -> Control Panel -> System -> Advanced -> Performance Options, and select the Background Services option.
On Windows NT machines, select Start -> Settings -> Control Panel -> System Properties > Application Performance. Set Performance boost to "None."
Check if the size of the output.mdb file in the results folder is more than 2 GB
If the output.mdb file becomes greater than 2GB during a load test, Controller is unable to write into it anymore and cause a crash.

Run the Controller’s batch files to register DLLs

Sometimes, DLLs can become unregistered or the registry can become corrupted to a point where a program's DLLs cannot be found. The purpose of batch files is to reregister them into the system's registry so that the programs can locate them. Use the following steps to do this:

 Shut down the Controller.

1. Navigate to the \bin directory, and look for the following files:

• register_controller.bat 
• set_mon.bat

   3. Create a duplicate copy of the file, in the same location.
   4. Open up the duplicated file. In it, you should see several entries like the following:
 regsvr32 /s webbrwsr.dll
Remove the "/s" from each of these statements, but leave a space between the "regsvr32" and the DLL name.
  5. Save the changes.
  6. Double click on the batch file to run it. You should get several pop-up messages.

Try to recreate the Controller’s initialization file

Sometimes, the initialization files can become corrupted (e.g. after a crashed). You will have problem in launching or using the Controller after that. Use the following steps to do delete the initialization file so that a new copy will be created:
1. Shut the Controller.
2. Navigate to the C:\Winnt ( or C:\Windows for Windows XP machine )
3. Delete all files that begin with wlrun*. For example,
wlrun.ini, wlrun5.ini, wlrun7.dft, wlrun7.hst, wlrun7.ini

Check the temporary environment variables

Unlike the earlier window’s versions, Window 2000 and Window XP have the default environment set to c:\Document and Settings\\Local Settings\Temp instead of c:\Windows\temp. This long path with a space can cause several problems on LoadRunner. To resolve the issue, change to a directory without empty spaces

Reboot the system

When programs crash, they leave the system in an unstable state. This can cause many other problems that seem to have no apparent reason for happening or has not happened before. When the system is rebooted, it resets the system into a more stable state. This should be done after any program crashes.
Verify the information in the event viewer
Sometimes, if a program crashes, it does not give any clues for what had happened. By using the Windows event viewer, it may be possible to find some clue as to what happened when the crash occurred. The event viewer can be launched from Start -> Programs -> Administrative Tools -> Event Viewer.


Verify other programs are interfering with Controller

To find out whether hooked DLLs are possibly causing a problem, you can use a third party utility call "Process Explorer." This utility has the ability to view the DLLs loaded by an application. It can be downloaded free of charge from the following link:
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

This can be used to see if LoadRunner loaded any other program's DLLs. 

Use the following steps to do this:

1. Unzip the .zip file, which was downloaded from the above URL, into a directory where you wish to install Process Explorer.
2. Start the Controller.
3. Run the Process Explorer (procexp.exe) from the directory into which you unzipped it (step a).
4. Select wlrun.exe (Controller) from the top section of Process Explorer.

5. The bottom section should be displaying a list of DLLs. If it is showing handles for the application, go to the "View" menu and select "DLLs."
6. Search through the list to see if any other program's DLLs are loaded. Normally, only DLLs from the \bin directory and standard Microsoft directories are loaded. For example, if you see wbhook32.dll (McAfee VirusScan hooking DLL) loaded by LoadRunner, then you would want to shut down the anti-virus software.


Disable the Anti-virus software what ever it present

It is known that anti-virus software is intrusive when they are set to look for viruses. However, in searching for viruses, the software can interfere with a program's proper execution. This could cause problems and sometimes crashes. This is why, for debugging purposes, it is recommended to turn off the anti-virus software.