Labels

Monday, September 23, 2013

Resolution : Issue In Generating Flex Calls In VuGen 11

Here the response we received from HP for generating flex calls if your vugen is unable to capture/generate:

1. If the application JAR files are developed with JRE 1.6 or higher, you can follow below steps:
a.Starting with LoadRunner 11.* we have a option to specify the External JVM path and this is the recommended approach.
b.Go to Tools -> Recording Options-> Flex->Configuration and check the option Use ExternalJVM.
c.External JVM Path should point to the JRE 1.6 folder then.
d.Either of these workarounds should allow LR/PC Vugen to utilize the newer JRE directory and will resolve these errors.
e.The second work around will be navigate to the LR install directory and locate a directory named JRE. Rename this directory and move it to a different location on the same machine. Next, copy the jre 1.6 directory from the 1.6jdk and place it in the LR install directory. Now rename it from JRE 1.6 to just JRE (to match the name of the original JRE that was renamed above)

2.Large AMF Flex calls are not getting generated in the script. Please follow below points
a.Go to Vugen.ini file located in \config folder.
b.Add the following line on BodySize in the Web Recorder section as given below:
[WebRecorder]
BodySize=2048000
Save the file.
Close Vugen (if it is already open). Open Vugen . Then go to Tools --> Regenerate script --> add all the jar files ie. application jar files and Flexjar files needed.
Regenerate your script.
You will see all the amf flex calls in the script.
3.The latest version LR 11.5x has more enhancements for flex. So it is better to go with 11.5

Thursday, September 19, 2013

HP Loadrunner Aanlysis- All Graphs Revealed

HP Loadrunner Anlysis - All graphs revealed. Below are the graphs in HP Loadrunner analysis files with their description and importance to achieve something in Performance Engineernig.

Running Vusers - Displays the number of Vusers that executed Vuser scripts, and their status, during each second of a load test. This graph is useful for determining the Vuser load on your server at any given moment.
Vuser Summary- Displays the number of Vusers that completed their run successfully, stopped their run, or ended with errors.

Error Statistics (by description)- Displays the number of errors that accrued during the load test, grouped by error code and Error Message.
Errors per second( by description)- Displays the average number of errors that occurred during each second of the scenario run, grouped by error code and Error Message.
Error Statistics - Displays the number of errors that accrued during the load test, grouped by error code. Errors per second - Displays the average number of errors that occurred during each second of the scenario run, grouped by error code.
Total Errors per second - Displays the average number of errors that occurred during each second of the scenario run.

Average transaction Response Time - Displays the average time taken to perform transactions during each second of the load test. This graph helps you determine whether the performance of the server is within acceptable minimum and maximum transaction performance time ranges defined for your system.
Transactions Per second -Transactions Per second - Displays the number of completed transactions (both successful and unsuccessful) performed during each second of a load test. This graph helps you determine the actual transaction load on your system at any given moment.
Total Transactions Per second - Displays the total number of completed transactions (both successful and unsuccessful) performed during each second of a load test. This graph helps you determine the actual transaction load on your system at any given moment.
Transaction Summary - Displays the number of transactions that passed, failed, stopped, or ended with errors.
transaction Performance Summary - Displays the minimum, average, and maximum response time for all the transactions in the load test.
Transaction Performance Summary Under Load - Displays average transaction response times relative to the number of Vusers running at any given point during the load test. This graph helps you view the general impact of Vuser load on performance time and is most useful when analyzing a load test which is run with a gradual load.
Transaction Performance Summary( Percentile)- Displays the percentage of transactions that were performed within a given time range. This graph helps you determine the percentage of transactions that meet the performance criteria defined for your system.
Transaction Performance Summary( Distribution)- Displays the number of times a transaction was completed over a distribution of time ranges. Note that this graph only displays information for a single transaction at a time.



Hits per second - Displays the number of hits made on the Web server by Vusers during each second of the load test. This graph helps you evaluate the amount of load Vusers generate, in terms of the number of hits.
Throughput - Displays the amount of throughput (in bytes) on the Web server during the load test. Throughput represents the amount of data that the Vusers received from the server at any given second. This graph helps you to evaluate the amount of load Vusers generate, in terms of server throughput.
Throughput(in MB)-Throughput represents the amount of data that the Vusers received from the server at any given second.
HTTP status code summary - Displays the distribution of the various HTTP protocol status codes returned from the Web Server during the load test.
HTTP Responses Per Second - Displays the number of the different HTTP status codes returned from the Web server during each second of the load test.
Retries Per Second - Displays the number of attempted server connections during each second of the scenario run. A server connection is retried when the initial connection was unauthorized, when proxy authentication is required, when the initial connection was closed by the server, when the initial connection to the server could not be made, or when the server was initially unable to resolve the load generator's IP address.
Retries summary - Shows the number of attempted server connections during the scenario run, grouped by the cause of the retry. Use this graph together with the Retries per Second Graph to determine at what point during the scenario the server retries were attempted.
Connections - Displays the number of Connections
Connections Per Second - Displays the number of Connections per Second.


Windows Resources - Displays a summary of the System Resources usage for each Windows based host.