0

We are running a load test with one Web/HTTP script and 25 user load. The response times for all the transactions gradually increases from 5 seconds during ramp up to 90+ seconds during steady state. But the resource utilization at Application layer is below 10% and Load generator is below 20%. There is no saturation observed in CPU, Memory, Disk and Threads utilization.

During steady state when we run the Vugen script in Load generator machine, the response time is below 5 seconds. Also, When we manually run the workflow in browser, the response time is below 5 seconds. logging is disabled in script. Think times are initialized outside transactions. Pacing is set to 30 seconds.

Based on above observations we think the issue with the Load Generator.

We found 2 solutions to resolve the issue:

1) Changing the multithreading option from Thread to Process in script run time settings. The issue still occurs when we set it to Process but the probability is 20%. When option is set to Thread, the issue occurs all the time.

2) Use of two load generators instead of one. But the issue still occurs with a 10%-20% probability when we use this option.

We are still not able to figure out the exact root cause of the issue. Please let me know for more information.

Vugen version: 12.55 Build 0911

HPE PC: 12.55 Build 12.55.3489.0

Load Generator config: VM based. Windows Server 2012 R2 64 bit, Xeon V2 4 CPU at 2.8 GHZ, 16 GB Memory.

Thanks in advance.

coder
  • 8,346
  • 16
  • 39
  • 53
jaysel
  • 1
  • 1
  • I think that SO is not the best place to ask this kind of a question. Your best options are to start a thread at the official forum - https://community.softwaregrp.com/t5/LoadRunner-Performance-Center/ct-p/sws-LoadRunner or to open a support ticket. – Buzzy May 07 '18 at 04:49
  • Do you have any think time or pacing in your test virtual user? – James Pulley May 07 '18 at 12:34
  • If you are in a virtual machine, then you have a virtual CPU and the RAM that the VM provides. You would not have full access to the host. Virtual CPUs are not Xeons – James Pulley May 08 '18 at 12:29
  • @Buzzy: Thanks for your response Buzzy. We already raised a support ticket. It's been three months of analysis by Microfocus team. The ticket is still open. – jaysel May 09 '18 at 00:32
  • @James: Thanks James. Yes you are correct, the LG configuration is 4 vCPU at 2.8 GHz. Think times configured in the test are 5 seconds at the start of each transactions (total six transactions) and pacing is set to 30 second – jaysel May 09 '18 at 00:56
  • @jaysel I am sure they are doing whatever they can to diagnose it. If you give me the ticket ID i will try to check where it stands. – Buzzy May 09 '18 at 08:51

0 Answers0