Note: Please see the loadrunner help file for more details. The following table describes the system requirements for each platform supported by Mercury for LoadRunner UNIX Vusers. Note that LoadRunner supports all X Servers.
Platform Hardware Version
Solaris Ultra Sparc Solaris 2.8 or higher
HP HP 9000 series 700, 800, HP-UX 11.x or higher
IBM IBM RS/6000 AIX 4.3.3 or higher
Linux PC i486 Red Hat 9.0 or higher
System Resources:The following describes the system resources required for each platform or operating system. The actual resources may vary depending on the number of Vuser licenses purchased. The resources for Vusers listed below apply to each virtual user. If you are installing multiple virtual users, you must multiply the figure by the number of virtual users. Disk Space required for program installation 22 MB (34 for Linux) Memory Space each Vuser if run as thread 300 KB (at least). This amount may vary, depending on the operating system and platform, and does not include the memory used by the process. Memory Space each Vuser if run as process 1.5 MB (2.5 MB for Solaris) Swap Space approximately 1:7 memory/swap ration Free Process Entries each Vuser if run as process 1 File Descriptors each Vuser if run as thread 2 (see below) The Memory Space above describes a general C-Vuser type. Other types may take up more memory space. For example, each Web Vuser uses at least 500 KB.
1. 14 file descriptors for the LoadRunner launch service
2. 20 file descriptors for the LoadRunner agent
3. 30 file descriptors for each Vuser driver. By default, there is a driver for every 50 Vusers.
- Open Vugen
- Choose a protocol depending on your application
- Record the scenario you have identified
- Enhance / Edit the script
- Configure the run time settings
- Run the script for single iteration
- Integrate the Vuser script in the controller to the scenario
Lets go in detail on all these steps:
1. Open VUgen
2. Click on the New button 3. Select web (HTTP/HTML) from the list of single protocol
4.Click ok button
5. Start record window is displayed. Provide the URL you want to record on, for now keep the settings as shown below
6. Click ok button
7.New IE page opens with http://www.perfload.com/8. Enter name in the search field
9. Stop recording
10.Script is generated
11.Click on the run button or F5This is a high level picture of recording and running a basic Web Protocol script.You might have observed in the above script there are 3 sections in the script as follows:
- Vuser_init
- action
- Vuser_end
Lets analyze the importance of each one and when we have to use it:
Vuser_Init:This section is mostly used to record the login part of your application. This section is executed only one during the run irrespective of the number of iterations you choose in the run time settings. In simple words no matter how many times you execute the script this section runs only once. This section is executed when Vuser is initialized Action:This section is used to record all the activities you perform once you login to the application. This section is executed multiple times. it depends on the run time settings. In simple words this will run as many numbers of times you want provided you make the specific changes in the run time settings.This section is executed when Vuser is in running status Note: There can be multiple actions in the script. Use multiple actions according to your needs. Vuser_end:This section is used to record your logout part of the application. This runs only once like Vuser_init. This is executed when Vuser finishes/stopped. Example: If you consider logging into your mail account, checking mails, sending mails and logging out then : Vuser_init : Logging into mail Action : Checking mails, sending mails Vuser_end : Logging out
No comments:
Post a Comment