1
votes

I configured my test in this way (in windows 7):

  • 1 Virtual machine is master, that run all vm slaves with the command for a distribuited testing (from command line) and show in jmeter GUI some graphs (for example jp@gc Active thread over time , hits/sec, response time, etc..).
  • 3 Virtual machine are slave, to execute the testing;

When master run the "start" to 3 slave, the test works (each slave run 6 thread), and in the GUI on master, there are only 6 thread in the graph (jp@gc - Active Threads Over Time), but in reality are 18 (6 thread for slaves, with 3 slaves).

So my question is: how can I see the total data for all slaves?

jp@gc - Active Threads Over Time = to see 18 thread (thread slave1 +thread slave2+thread slave3) jp@gc - Hits per Second = Hits slave 1 +Hits slave 2+ Hits slave 3

and so on...

2

2 Answers

1
votes

You need to add __machineName or __machineIP function so the listeners could distinguish results coming from different nodes.

Also be aware of mode property which is configured to send results from slave machines each 100 results or each minute (whatever comes the first) so you might want to amend it, i.e. add mode=Standard line to user.properties file on each slave node.

# Remote batching support
# Since JMeter 2.9, default is MODE_STRIPPED_BATCH, which returns samples in
# batch mode (every 100 samples or every minute by default)
# Note also that MODE_STRIPPED_BATCH strips response data from SampleResult, so if you need it change to
# another mode
# Hold retains samples until end of test (may need lots of memory)
# Batch returns samples in batches
# Statistical returns sample summary statistics
# hold_samples was originally defined as a separate property,
# but can now also be defined using mode=Hold
# mode can also be the class name of an implementation of org.apache.jmeter.samplers.SampleSender
#mode=Standard
#mode=Batch
#mode=Hold
#mode=Statistical

See Apache JMeter Properties Customization Guide for more information on working with JMeter properties.

Be aware that sending results in case of severe load may cause network IO overhead so it might be a good idea to consider Backend Listener instead

0
votes

Add the Machine Info function to the thread group name area as shown below:

enter image description here