-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
why i get same number of threads,regardless i use 1 or 4 slave EC2 #91
Comments
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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 :
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...
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 =================================
===================================================================== 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...
Test Results: /home/kimo/Downloads/jm2/jmeter-bootstrap/jmeter-ec2/results/jmeter-ec2-1501776223-complete.jtl
The text was updated successfully, but these errors were encountered: