why i get same number of threads,regardless i use 1 or 4 slave EC2

[kimo23]

I've setup my JMeter Master-Slave like this: Master: Local Ubunto (on vmware) 4 Slave EC2 (Ubunto), my Master starts the tests on all of the slave, i have a Testplan with 400 threads, but my target get the same amount of request regardless if i use only one slave or all of them together.

I don't understand why the threads number is 400 when i use 4 slave ( should be 4*400 =1600)

here my Ubuntu terminal after testrun :

---

   jmeter-ec2 Automation Script - Running jmeter-ec2.jmx over 4 predefined host(s)

---

copying verify.sh to 4 server(s)... [##################################################] 100.00% - (4 of 4) - Done.

running verify.sh on 4 server(s)... [##################################################] 100.00% - (4 of 4) - Done.

editing thread counts...

• jmeter-ec2.jmx has 1 threadgroup(s) - [inc. those disabled]
• There are 10 threads in the test plan, this test is set to execute 100 percent of these, so will run using 10 threads

thread counts updated

copying test files to 4 server(s)...jmx files..done....jmeter.properties..done....system.properties..done....jmeter execution file...done....all files uploaded

starting jmeter on: ec2-35-158-211-233.eu-central-1.compute.amazonaws.com ec2-35-158-149-34.eu-central-1.compute.amazonaws.com ec2-35-157-214-139.eu-central-1.compute.amazonaws.com ec2-52-59-146-132.eu-central-1.compute.amazonaws.com

JMeter started at Thu Aug 3 18:03:53 CEST 2017 ====================== START OF JMETER-EC2 TEST =================================

[updates: every 15 seconds | running total: every 45 seconds]

waiting for the test to start...to stop the test while it is running, press CTRL-C (standard_in) 2: syntax error (standard_in) 1: syntax error (standard_in) 1: syntax error (standard_in) 1: syntax error

18:04:08: [FINAL RESULTS] total count: 10, overall avg: 384 (ms), overall tps: 3.0 (p/sec), recent tps: (p/sec), errors: 0

===================================================================== END OF JMETER-EC2 TEST ==================================================================================

downloading results from ec2-35-158-211-233.eu-central-1.compute.amazonaws.com.../home/kimo/Downloads/jm2/jmeter-bootstrap/jmeter-ec2/jmeter-ec2-1501776223-0.jtl complete downloading results from ec2-35-158-149-34.eu-central-1.compute.amazonaws.com.../home/kimo/Downloads/jm2/jmeter-bootstrap/jmeter-ec2/jmeter-ec2-1501776223-1.jtl complete downloading results from ec2-35-157-214-139.eu-central-1.compute.amazonaws.com.../home/kimo/Downloads/jm2/jmeter-bootstrap/jmeter-ec2/jmeter-ec2-1501776223-2.jtl complete downloading results from ec2-52-59-146-132.eu-central-1.compute.amazonaws.com.../home/kimo/Downloads/jm2/jmeter-bootstrap/jmeter-ec2/jmeter-ec2-1501776223-3.jtl complete

processing results...

              jmeter-ec2 Automation Script - COMPLETE

Test Results: /home/kimo/Downloads/jm2/jmeter-bootstrap/jmeter-ec2/results/jmeter-ec2-1501776223-complete.jtl

[oliverlloyd]

This is by design. If your testplan has 400 and you choose to run the test using 4 slaves then the script automatically distributes the threads over all slaves so in this case each would run using 100.