Load-bearing test by JMeter

Tram Ho

Preamble

With each execution load 10,000 requests / sec when running each jmeter single unit, the load capacity cannot be tested so I recommend to you how to test by Jmeter Cluster configuration Refer to the following content to know how to run Test Jmeter local, creating basic jmeter file is not covered in this article. Test Jmeter on local Basic environment to test the load

Overview of Cluster configuration

Running with infrastructure including master server, slave server (multiple machines). I will put the setting file on the Master server and then run it, the Slave server will synthesize the result log etc. to the Master server. So the SLave server side just needs to start Jmeter.

Setup Master server

If you weaken it, yes

  1. install jmeter
  2. decompression
  3. setting Slave server

Install jmeter

at / home / ec2-user

Decompression

Setting Slave server

Editing property. go to the bin entry in apache-jmeter-5.1.1, open the property with vim, enter the DNS name of the Slave server in the remote host box. Note that if you enter the IP address, you will get an error so you must enter the correct value. If you want to set up multiple Slave servers, then write them separated by commas, that’s fine.

Setup Slaver server

  1. install jmeter
  2. decompression
  3. start up Jmeter

Start jmeter

Check that it has not been started before the check process:

Launch:

check the process again to see that jmeter has been started.

Load-bearing test

When the Jmeter is successfully started by the Slave server, it will switch to pending command from the Master Server side, so the load-bearing test will be performed. To check the process this time so a while ago after command /home/ec2-user/apache-jmeter-5.1.1/bin/jmeter-server & I have already /home/ec2-user/apache-jmeter-5.1.1/bin/jmeter-server & , but normally just let it be started. so.

This place needs to be sudo. The boot command is /home/ec2-user/apache-jmeter-5.1.1/bin/jmeter , -n is to boot in CUI mode, -t is the option to specify the setting file. In addition, the setting file is required to be specified with an absolute path.

Occasionally there will appear Error in NonGUIDriver java.lang.RuntimeException, in this case something has happened on the Slaver server, just restart Jmeter. If you can’t reboot, then kill the process, kill the bottom of the 3 processes.

Then reboot

Go back to the Master server, run again

When there is a Waiting for show, the load test has been successful !!!

Refer

Use SpotInstance and JMeter to test the load of 4,000,000 req / min

Share the news now

Source : Viblo