You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can run MQTTLoader on multiple machines, e.g., run publishers and subscribers separately on different machines.
50
+
You can run MQTTLoader on multiple machines.
51
+
Running both publishers and subscribers on a single machine may cause mutual influence, e.g., the subscribers' receiving load lowers the publishers' throughput.
52
+
By running publishers and subscribers separately on different machines, you can avoid such mutual influence.
53
+
51
54
For example, on a host A, you can run MQTTLoader as follows:
@@ -98,6 +101,9 @@ MQTTLoader starts to terminate when all of the following conditions are met.
98
101
MQTTLoader also starts to terminate when the time specified by the parameter `-et` elapses, even if there are in-flight messages.
99
102
Thus, `-et` should be long sufficiently.
100
103
104
+
If you want to do measurement with fixed time period, you can set the measurement time by the parameter `-et`.
105
+
Note that you need to set sufficiently large value to the parameter `-m`.
106
+
101
107
By setting the parameter `-n`, MQTTLoader obtains the offset time from the specified NTP server and reflects it to calculate throughput and latency.
102
108
It might be useful for running multiple MQTTLoader on different machines.
103
109
@@ -121,6 +127,8 @@ Maximum latency[ms]: 81
121
127
Average latency[ms]: 42.23691
122
128
```
123
129
For each publisher, MQTTLoader counts the number of messages sent for each second.
130
+
If QoS level is set to 1 or 2, counting is done when receiving PUBACK or PUBCOMP respectively.
131
+
124
132
After completion, MQTTLoader collects the counted numbers from all publishers and calculates the maximum throughput, the average throughput, and the number of published messages.
125
133
`Throughput[msg/s]` is the list of throughputs, which are the sum of each second for all publishers.
126
134
Note that these calculation exclude the beginning and trailing seconds that have 0 messages.
@@ -159,6 +167,8 @@ Thus, when running multiple MQTTLoader on different machines (e.g., publishers o
159
167
By specifying the file name with `-tf` parameter, you can obtain throughput data like the following.
0 commit comments