If you have been following my ongoing video tutorials on jmeter performance testing then you may have wondered what server side statistics should be gathered during performance testing. We have not yet looked in to specific statistics which we should gather for server side monitoring. In this post we would have a look at useful linux commands which can be used to gather several important performance statistics. We would use these commands in future performance testing tutorials to gather server side performance statistics. Most of the description of these commands is from command "man"ual. So lets begin -
Distributed Testing with JMeter When one JMeter client is not able to offer amount of threads required for load testing then distributed testing is used. In distributed testing - One instance of JMeter client can control number of JMeter instances and collect data from them Test plan does not need to be copied to each server, the client sends it to all servers note - JMeter will run all the threads on all the servers, hence 100 threads on 5 JMeter server would pump 500 threads in total. If many server instances are used, the client JMeter can become overloaded and so the client network connection. This has been improved in latest versions of JMeter by switching to Stripped modes, but you should always check that your client is not overloaded When Client (master) and Server (slave) nodes are on same network (no SSH required) Configure Client Node Herein client is referred as the machine controlling test execution on other JMeter nodes. This is also referred