1. You can choose how many threads will be started for this or that slave
machine by setting the number of threads in Thread Group
<http://jmeter.apache.org/usermanual/component_reference.html#Thread_Group>
(s) using __P() function
<https://jmeter.apache.org/usermanual/functions.html#__P> like
> ${__P(threads)}
Once done you can define the desired number of threads on each slave in
/user.properties/ file , i.e. on 1st slave:
> threads=15
on 2nd slave
> threads=25
2. You can switch code execution lines depending on slave machine using If
Controller
<http://jmeter.apache.org/usermanual/component_reference.html#If_Controller>
and __machineName()
<https://jmeter.apache.org/usermanual/functions.html#__machineName> or
__machineIP()
<https://jmeter.apache.org/usermanual/functions.html#__machineIP>
functions combination like:
> - If Controller, condition: "${__machineIP()}" == "10.10.10.11"
> - requests for slave with IP address 10.10.10.11
3. You can set *mode=Standard* property for all slaves, this way they will
send full results to master as soon as they will be generated. This way you
will be able to "normally" analyse the .JTL results file in the realtime.
See Using a different sample sender
<http://jmeter.apache.org/usermanual/remote-test.html#sendermode> for more
details.
Reference material:
1. Remote Testing <http://jmeter.apache.org/usermanual/remote-test.html>
2. How to Perform Distributed Testing in JMeter
<https://www.blazemeter.com/blog/how-to-perform-distributed-testing-in-jmeter>
3. JMeter Distributed Testing Step-by-step
<https://jmeter.apache.org/usermanual/jmeter_distributed_testing_step_by_step.pdf>
--
Sent from: http://www.jmeter-archive.org/JMeter-User-f512775.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
