4 Points to note for Scenario Execution!

Posted: April 21st, 2008 | Author: TnT Admin | Filed under: Concepts | Tags: , , | No Comments »

Points to note prior or during the scenario execution. This will save you unnecessary trouble looking at logs and reconfiguring the environment

1. First, ensure the environment for load testing is consistent for all participating machines (ie. Controller and Load Generators). As the scripts are sent to the Load Generator to be executed, it must have the same environmental settings of the recorded scripts (in VuGen). For example, if the script was recorded in RMI-Java, JDK 1.4 exists on the machine that performed the recording. In the same context, the Load Generator will also require the JDK 1.4 to be installed on it for the script to execute properly. Therefore, ensure JDK versions are installed and similar to the recording machine. Read the rest of this entry »

What happens when the scenario is executed?

Posted: April 21st, 2008 | Author: TnT Admin | Filed under: Concepts | Tags: , | 6 Comments »

Here, we’ll discuss the basic overview of LoadRunner when the scenario starts execution, during and till the end. Prior to the scenario execution, the Load Generators, amount of Vusers, designated monitoring machine, ramp up timing, so on so forth should be already defined, and we will skip the discussion for it.

When the scenario starts executing, the Controller dispatches the Vusers (scripts) to the Load Generators for execution. The Vusers are then executed on the Load Generator in memory with the pre-defined amount on behalf of the Controller. These vusers in terms generate the network traffic towards the application. Read the rest of this entry »