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
| broker | Yes | (none) | Broker's IP address or FQDN. <br>Ex. `broker = 127.0.0.1`|
72
72
| broker_port | No | 1883 (non-TLS)<br>8883 (TLS) | Broker's port number. <br>Ex. `broker_port = 1883`|
73
-
| mqtt_version | No | 5 | MQTT version. `3` for MQTT v3.1.1, and `5` for MQTT v5.0. |
73
+
| mqtt_version | No | 5 | MQTT version. 3 for MQTT v3.1.1, and 5 for MQTT v5.0. |
74
74
| num_publishers | No | 1 | The number of publishers. All publishers send messages to a same topic. |
75
75
| num_subscribers | No | 1 | The number of subscribers. All subscribers are subscribe to a same topic. |
76
76
| qos_publisher | No | 0 | QoS level of publishers. <br>Valid values are 0/1/2. |
@@ -82,10 +82,10 @@ The following table shows the parameters which can be set in *mqttloader.conf*.
82
82
| num_messages | No | 100 | The number of messages sent by **each** publisher. |
83
83
| ramp_up | No | 0 | Ramp-up time in seconds. <br>See **4. How to read the results** for details. |
84
84
| ramp_down | No | 0 | Ramp-down time in seconds. <br>See **4. How to read the results** for details. |
85
-
| interval | No | 0 | Publish interval in microseconds. |
85
+
| interval | No | 0 | Publish interval in microseconds.<br>Regardless of num_publishers, each publisher sends messages at this interval. In addition, the gap between multiple publishers' sending is adjusted to be interval/num_publishers as far as possible.|
86
86
| subscriber_timeout | No | 5 | Timeout for receiving messages by subscribers in seconds. |
87
87
| exec_time | No | 60 | Maximum execution time for measurement in seconds. |
88
-
| log_level | No | INFO | Log level. <br>Valid values are `SEVERE`/`WARNING`/`INFO`/`ALL`. |
88
+
| log_level | No | INFO | Log level. <br>Valid values are SEVERE/WARNING/INFO/ALL. |
89
89
| ntp | No | (none) | NTP server's IP address or FQDN. By setting this, throughput and latency are calculated based on the NTP server's time.<br>It should be set when running multiple MQTTLoader on different machines.<br>Ex. `ntp = ntp.nict.jp`|
90
90
| output <sup>**\*1 \*2**</sup> | No | (none) | Directory path to write out measurement record. If not set, MQTTLoader runs by in-memory mode. <br>Ex. `output = /home/testuser`|
91
91
| user_name | No | (none) | User name. Required if the broker has the configuration of password authentication. |
@@ -213,7 +213,7 @@ If QoS level is set to 1 or 2, counting is done when receiving PUBACK or PUBCOMP
213
213
After completion, MQTTLoader calculates the maximum throughput, the average throughput, and the number of published messages.
214
214
`Per second throughput [msg/s]` is the time series of throughputs per second.
215
215
216
-
By using the parameterse`ramp_up` and `ramp_down`, you can exclude the beginning and trailing data.
216
+
By using the parameters`ramp_up` and `ramp_down`, you can exclude the beginning and trailing data.
217
217
If you set the following parameter settings for example, the beginning one second and the trailing one second are excluded.
218
218
219
219
```
@@ -239,6 +239,7 @@ Note that if the specified directory doesn't exist, it is newly created.
239
239
The file `mqttloader_xxxxxxxx-xxxxxx.csv` has records like the following:
240
240
241
241
```
242
+
1599643916401359,,,
242
243
1599643916416823,ml-EeiE-p-00001,S,
243
244
1599643916416882,ml-EeiE-p-00000,S,
244
245
1599643916419123,ml-EeiE-s-00000,R,3165
@@ -248,6 +249,7 @@ The file `mqttloader_xxxxxxxx-xxxxxx.csv` has records like the following:
248
249
```
249
250
250
251
Each line, consists of comma-separeted values, indicates the following data.
252
+
The first line indicates the measurement start time.
251
253
In the case that the event type is `R`, latency data follows.
252
254
253
255
```
@@ -256,6 +258,7 @@ timestamp (Unix time in microseconds), client ID, event type (S: send, R: receiv
256
258
257
259
Although MQTTLoader outputs the measurement result to the console, you can use the above .csv file for further analysis.
258
260
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.
261
+
the parameters `ramp_up` and `ramp_down` do not affect this file.
0 commit comments