I am doing load testing for Web application for 2000 VUsers with Load Runner on 5 Load Gen machines . But after 250 VU I am getting memory error for Web_set_max_html....
The configuration for Load Gen is Pentium IV 3.00Ghz, 2 GB RAM and 80 GB HDD.
Could any please tell me, How many Vusers should be handled by one Load Gen?
Web_set_max_html has nothing to do with memory of load generator! have you monitored the memory of Load Generator during the test?
however you can
Refer "Memory footprint" on Mercury support site for nos. of user handled by Load Generator .
Sets the maximum length of any HTML string that can be retrieved and saved as a parameter.
int web_set_max_html_param_len (const char *length );
length The maximum length of any HTML string that can be retrieved.
The web_set_max_html_param_len function is a Service function that is used when correlating HTML statements. It is recorded only when correlation during recording is enabled (see Vugen's Recording Options).
The web_set_max_html_param_len function sets the maximum length of any HTML string which VuGen can retrieve and save in a parameter. The default value for the maximum length of a parameter that can be captured during correlation is 256 characters (see web_reg_save_param). To retrieve a string longer than 256 characters, use web_set_max_html_param_len to increase the maximum valid length. If you try to retrieve a string whose length exceeds the maximum length, the function fails.
This function is supported for all Web Vusers and for WAP Vusers running in HTTP mode or Wireless Session Protocol (WSP) replay mode.
<font size="2" face="Verdana, Arial, Helvetica">Quite plainly, the number of VUsers on a particular box is not the root of your problem. [img]images/icons/smile.gif[/img]
As far as I know, 1 vuser consumes 2 MB of system memory, and you have to leave 8 MB for the system itself... so for a system with 2 GB (2048 MB) memory, after deducting 8 MB for system, you have 2040 MB so you should be able to run atleas 1000 vusers (ideally 1020) without any trouble. I don't know what the problem could be in your case though...
Memory usage per vuser depends also on whether you chose thread or process per vuser in the runtime settings. Process takes more memory. There is a KB article (10291) with a spreadsheet showing memory usage for vusers for the different protocols. The sheets show per process and thread as well as first instance and next instance sizes.