Highlighted
Absent Member.
Absent Member.
322 views

Inconsistent results when running vusers from Controller (localhost) and remote VUGEN machine

We are getting inconsistent results when running our vusers on the localhost (i.e. machine with the controller) and a different remote VUGEN machine. Is this meant to be the case?
The particular issue we are having is that response times are longer on the remote VUGEN machine. Is this meant to be the case and if so, why?
One suspicion we have is that on the remote VUGEN, connecting to google analytics (part of the script) takes longer. The machines (localhost and remote VUGEN machine) are on the same network.
0 Likes
5 Replies
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Inconsistent results when running vusers from Controller (localhost) and remote VUGEN machine

Hi Adnan,

Firstly,where exactly is vugen and Controller placed?

There could be a difference in the response time of vugen and Controller, in case vugen is sitting in India and controller in UK while your Application server is also in UK.
The latency could be due to network.

How many users are you running in the controller ?
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Inconsistent results when running vusers from Controller (localhost) and remote VUGEN machine

Thanks for the reply SSP.
Everything is sitting in the same place. The controller, VUGEN and the application server.
The controller and VUGEN machine are also on the same subnet whilst the application server is on a different one.
We are connecting via host files on both the controller machine and the VUGEN.
0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Inconsistent results when running vusers from Controller (localhost) and remote VUGEN machine

Ok.
Have you tried running a single user in controller and verify the response time with that of Vugen user log.

How significant is the difference between either results?
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Inconsistent results when running vusers from Controller (localhost) and remote VUGEN machine

SSP,
The difference really seems to be when our script tries to connect to google analytics. On the controller, it fails to connect and exits in hundreths of seconds. In the VUGEN, it takes a whole second to timeout. After a number of iterations, this ends up with a significant difference.
We suspect that there are some differences in the VUGEN and controller machine set ups.
What are the main differences in the machines that would cause such issues? I am assuming, by right, there should be no differences in response times as it should be measuring responses from the server.
0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

Re: Inconsistent results when running vusers from Controller (localhost) and remote VUGEN machine

A few things worth checking are
1. version of vugen and Controller(the patch level information should also match)
2. check the host file on the controller.
3. Ping the desired website from CMD(controller machine) to check if the packets get routed.
4. check the extended logs for both vugen and controller.
5. For the above run single user with single iteration on vugen and then single user single iteration on Controller.
6. Verify the error message

0 Likes
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.