Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It only takes a minute to sign up.
Sign up to join this community
I am running a test plan with 8,000 concurrent users in a Distributed Environment(20 Slaves and One Master) on Jmeter.
A few (approx 20-30) requests are not getting any response for a long time (approx an hour). I waited for a long time to allow the pending requests to complete, but Jmeter threw an exception with "Socket.timeout".
Can any one help me in understanding what the problem is. Am I lagging somewhere to understand the possible reason?
When you are doing a load test on an application, there is a lot that you have to take into consideration,
Not just the server's CPU and RAM but its network and disk I/O are also important. You also need to see what amount of requests choke up the port that your application is using for communication. CPU and RAM will be utilized if the request reaches them for execution. What if the port is not able to handle the amount of load you are hitting it with? In that case it will throw errors like socket timeouts. Each request has a certain execution life time (connection timeout) within which if the response is not received, you are bound to get a timeout error. So check your port capacity and the disk and network I/O.
This is a network constraint over which you may not have any control. Do you know after what time you get this error? You could play with Timeouts section on HTTP Request Sample and keep it higher than the time which causes timeout error.
This might be because some of application requests are taking too long to execute, holding the application server’s threads busy, and not allowing the resources to be used by incoming requests.
Try the running the test with 4000 concurrent users, then 6000 users and so on. Check at number of request you are getting this error.You must verify Apache logs or IIS logs and look for errors in the error and access logs. Monitor CPU and memory utilization and try to find bottleneck and fine tune to obtain desired results.
