1- # MQTTLoader usage (v0.8.2 )
1+ # MQTTLoader usage (v0.8.3 )
22MQTTLoader is a load testing tool (client tool) for MQTT.
33It supports both MQTT v5.0 and v3.1.1.
44From v0.8.0, it supports TLS authentication.
@@ -13,7 +13,7 @@ Download the archive file (zip or tar) from: https://github.com/dist-sys/mqttloa
1313Below is an example of downloading by using curl command.
1414
1515```
16- $ curl -OL https://github.com/dist-sys/mqttloader/releases/download/v0.8.2 /mqttloader-0.8.2 .zip
16+ $ curl -OL https://github.com/dist-sys/mqttloader/releases/download/v0.8.3 /mqttloader-0.8.3 .zip
1717```
1818
1919By extracting it, you can get the following files.
@@ -197,24 +197,24 @@ MQTTLoader displays results like the following on standard output.
197197
198198```
199199-----Publisher-----
200- Maximum throughput[msg/s]: 18622
201- Average throughput[msg/s]: 16666.666666666668
200+ Maximum throughput [msg/s]: 18622
201+ Average throughput [msg/s]: 16666.666
202202Number of published messages: 100000
203- Per second throughput[msg/s]: 11955, 16427, 18430, 18030, 18622, 16536
203+ Per second throughput [msg/s]: 11955, 16427, 18430, 18030, 18622, 16536
204204
205205-----Subscriber-----
206- Maximum throughput[msg/s]: 18620
207- Average throughput[msg/s]: 16666.666666666668
206+ Maximum throughput [msg/s]: 18620
207+ Average throughput [msg/s]: 16666.666
208208Number of received messages: 100000
209- Per second throughput[msg/s]: 11218, 16414, 18426, 18026, 18620, 17296
210- Maximum latency[ms]: 81
211- Average latency[ms]: 42.23691
209+ Per second throughput [msg/s]: 11218, 16414, 18426, 18026, 18620, 17296
210+ Maximum latency [ms]: 81.838
211+ Average latency [ms]: 42.236
212212```
213213MQTTLoader counts the number of messages sent by publishers.
214214If QoS level is set to 1 or 2, counting is done when receiving PUBACK or PUBCOMP respectively.
215215
216216After completion, MQTTLoader calculates the maximum throughput, the average throughput, and the number of published messages.
217- ` Per second throughput[msg/s] ` is the time series of throughputs per second.
217+ ` Per second throughput [msg/s] ` is the time series of throughputs per second.
218218
219219By using the parameterse ` ramp_up ` and ` ramp_down ` , you can exclude the beginning and trailing data.
220220If you set the following parameter settings for example, the beginning one second and the trailing one second are excluded.
@@ -242,10 +242,10 @@ Note that if the specified directory doesn't exist, it is newly created.
242242The file ` mqttloader_xxxxxxxx-xxxxxx.csv ` has records like the following:
243243
244244```
245- 1599643916416 ,ml-EeiE-p-00001,S,
246- 1599643916416 ,ml-EeiE-p-00000,S,
247- 1599643916419 ,ml-EeiE-s-00000,R,3
248- 1599643916422 ,ml-EeiE-p-00001,S,
245+ 1599643916416823 ,ml-EeiE-p-00001,S,
246+ 1599643916416882 ,ml-EeiE-p-00000,S,
247+ 1599643916419123 ,ml-EeiE-s-00000,R,3165
248+ 1599643916422982 ,ml-EeiE-p-00001,S,
249249 :
250250 :
251251```
@@ -254,10 +254,11 @@ Each line, consists of comma-separeted values, indicates the following data.
254254In the case that the event type is ` R ` , latency data follows.
255255
256256```
257- timestamp (Unix time in milliseconds ), client ID, event type (S: send, R: receive), latency (in milliseconds )
257+ timestamp (Unix time in microseconds ), client ID, event type (S: send, R: receive), latency (in microseconds )
258258```
259259
260260Although MQTTLoader outputs the measurement result to the console, you can use the above .csv file for further analysis.
261+ Note that the latency in the above file is in microseconds, whereas that in the console is in milliseconds with three digits after the decimal point.
261262
262263---
263264---
0 commit comments