Performance testing - 200 Concurrent Users Test in Jmeter is failing with 8 Machines

0
votes

I have tried running a test with 150 users & 6 machines in jmeter and it ran fine with no errors. But when i increased the number of users & number of machines to 200 users and 8 machines respectively, it started throwing "java.net.socketexception: connection reset" error

Previously i was facing this error when i tried running for 150 users with 4 machines. But, after increasing the machines by 2, the 150 user test was successful. Need help in this.

I tried accessing the application manually during the execution and i was able to access the application normally.

2
testingjmeterperformance-testingload-testingjmeter-5.0

2 Answers

0
votes

Are you absolutely sure you're talking about 150 and 200 users? I'm asking because you mentioned that you tried "150 users with 4 machines" which doesn't give whole number of users if the load is split.

  • 150 users and 6 machines give you 900 users in total
  • 200 users and 8 machines give you 1800 users in total

  1. So if you really want "200 users with 8 machines" make sure to have 25 users in Thread Group as each JMeter slave is executing the same test plan independently so if you have 25 users in thread group and 1 slave - it will be 25 users, 2 slaves - 50 users, 3 slaves - 75 users, etc.

  2. Make sure that your application is not overloaded and has enough headroom to operate in terms of CPU, RAM, Network sockets, etc. It be done with JMeter PerfMon Plugin

  3. Check your application logs as it might indicate the problem on the application side. If you're absolutely sure that application behaves correctly you might want to apply instructions from JMeterSocketClosed wiki page

0
votes

Why do you need 6 machines to run 200 Users ? 1 single machine should be good enough to handle smoothly such test.

Are you using a protocol (3rd party plugin) that explains this ?

Did you try running the test on your machine and see how CPU and memory were behaving before switching to distributed testing ?

Check this blog to ensure you're using best-practices.