Highlighted
Contributor.
Contributor.
404 views

Controller and Load generator

Jump to solution

Dear Team,

Please clarify my below question.

(a) There is web application (HTTP/HTML protocol) which is used by only 35 users. Is it logical to perform Load testing. This application is only use for generating the reports.

(b) If we are going to perform the Load testing 1hr for  35 vuser then one controller and one LG is fine.

(b)  In General, Load testing for any web application of any protocol. What is the minimum vusers required to perform the load testing.

(c) How can we define the number of controller and LG for any load testing.

Thanks

Abhinav

0 Likes
1 Solution

Accepted Solutions
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: Controller and Load generator

Jump to solution

@abhien011Hi Abhinav,

(a) Is it logical to perform Load testing.
It depends on a number of things:
- what do you want to validate / test: server performance / server resource consumption / server stability (duration test for a month) / impact on network bandwidth / performance regression testing / only one time prove / ...
- the expected concurrency: when users are rarly using the reports concurrently and your conclusion is that you have at most 2 or 3 users concurrent at a day, you can consider manual testing with three users and observe the backend, but humans are hard to control, esp. when they are not trained testers.

(b/c) Is then one controller and one LG is fine?.
This depends highly on recording protocol. When you stick with HTML/HTTP, you are fine with simple LG server. But keep in mind to add to your script human related think times. When you develop your script run it as one user with Controller/LG and measure CPU / memory / NW / Disk resource consumption. This is a guideline for the size of your final LG server. Due to hyperthreading issues, take only 50% of the CPU capacity as usefull of your LG.

When you decide to record with TruClient as @lb1 pointed out, you need much more capacity. Also the remark of @lb1 about disabling most logging during load testing is important.

(b) What is the minimum vusers required to perform the load testing.
See answer at (a)

Success,

Erik

Signature:
Reward community members who take time to respond and help.

View solution in original post

2 Replies
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: Controller and Load generator

Jump to solution

Hi Abhinav, 

my answer is based on the personal experience of the product. For TruClient protocol, since that is based on user experience via browser, I set a maximum of 4/5 Vusers per generator; otherwise in case of Web HTTP-HTML or Web Service protocols, usually you can set a greater number of virtual users, such as 40/50 Vusers per generator. In add, you have to pay attention on log verbosity: if the application (web service or web navigation) needs some logs (you can check log level from "Runtime Settings" window, both from VuGen or Controller) or LR catches many data during the load test, I suggest to scale the distribution of Vusers along the generators, so as not to incur on "CPU usage" error messages, that can compromise test performance.

Tell me if the response can help you, 

Lorenzo

0 Likes
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: Controller and Load generator

Jump to solution

@abhien011Hi Abhinav,

(a) Is it logical to perform Load testing.
It depends on a number of things:
- what do you want to validate / test: server performance / server resource consumption / server stability (duration test for a month) / impact on network bandwidth / performance regression testing / only one time prove / ...
- the expected concurrency: when users are rarly using the reports concurrently and your conclusion is that you have at most 2 or 3 users concurrent at a day, you can consider manual testing with three users and observe the backend, but humans are hard to control, esp. when they are not trained testers.

(b/c) Is then one controller and one LG is fine?.
This depends highly on recording protocol. When you stick with HTML/HTTP, you are fine with simple LG server. But keep in mind to add to your script human related think times. When you develop your script run it as one user with Controller/LG and measure CPU / memory / NW / Disk resource consumption. This is a guideline for the size of your final LG server. Due to hyperthreading issues, take only 50% of the CPU capacity as usefull of your LG.

When you decide to record with TruClient as @lb1 pointed out, you need much more capacity. Also the remark of @lb1 about disabling most logging during load testing is important.

(b) What is the minimum vusers required to perform the load testing.
See answer at (a)

Success,

Erik

Signature:
Reward community members who take time to respond and help.

View solution in original post

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.