krylovsk / mqtt-benchmark Goto Github PK

Add CI:

• golint
• go vet
• tests (TBD, but perhaps integration tests with https://github.com/ory/dockertest)
• build docker image

I am subscribed to the topic I am benchmarking.
with --count 30000 and --clients 1 the benchmark finishes almost instantly and the subscribing client sees one message come through the pipe.

The documents show the default being 100 messages. Removing --count all together still shows only one message coming through the broker to subscribers.

Side note, any benchmarking with more than one client results in: Msg time std (ms): NaN

When I try to connect to the broker, the error error connecting to the broker: Identifier rejected is thrown

I'm using Windows 10 and PowerShell

No idea what this is. I can successfully connect programmatically using a node.js script with the same parameters...
What's wrong?

./mqtt-benchmark --broker "tcp://staging.broker.aritronix.com:8883" --clients 1 --qos 1 --count 50 --username *** --password "***"
2021/06/30 10:31:23 Starting client  0
2021/06/30 10:31:24 CLIENT 0 had error connecting to the broker: Network Error : %!s(<nil>)

Thanks.

Sorry, I'm not a Go developer and the most basic instructions do not work.
On Mac, I ran:

- brew install go
- go install github.com/krylovsk/mqtt-benchmark@main
- ./mqtt-benchmark -h

There is no such file as mqtt-benchmark in this folder. Where is it?

Thanks.

2020/01/10 10:30:45 Starting client 252
2020/01/10 10:30:45 Starting client 253
2020/01/10 10:30:45 Starting client 254
2020/01/10 10:30:45 Starting client 255
2020/01/10 10:30:45 CLIENT 177 had error connecting to the broker: Network Error : dial tcp 52.221.235.39:1883: socket: too many open files
2020/01/10 10:30:45 CLIENT 176 had error connecting to the broker: Network Error : dial tcp 52.221.235.39:1883: socket: too many open files
2020/01/10 10:30:45 CLIENT 178 had error connecting to the broker: Network Error : dial tcp 52.221.235.39:1883: socket: too many open files
2020/01/10 10:30:45 CLIENT 175 had error connecting to the broker: Network Error : dial tcp 52.221.235.39:1883: socket: too many open files

It would be very cool if this project had binaries for different platforms available

i tried to modify the following cmd:
mqtt-benchmark --broker tcp://myhost:1883 --count 100 --size 100 --clients 100 --qos 2 --format text

to:
mqtt-benchmark --broker ws://myhost:8083 --count 100 --size 100 --clients 100 --qos 2 --format text

but got errors like:
2020/08/09 02:13:35 Starting client 95
2020/08/09 02:13:35 Starting client 96
2020/08/09 02:13:35 Starting client 97
2020/08/09 02:13:35 Starting client 98
2020/08/09 02:13:35 Starting client 99
2020/08/09 02:13:36 CLIENT 48 had error connecting to the broker: Network Error : websocket: bad handshake
2020/08/09 02:13:36 CLIENT 55 had error connecting to the broker: Network Error : websocket: bad handshake
2020/08/09 02:13:36 CLIENT 98 had error connecting to the broker: Network Error : websocket: bad handshake
2020/08/09 02:13:36 CLIENT 30 had error connecting to the broker: Network Error : websocket: bad handshake
2020/08/09 02:13:36 CLIENT 31 had error connecting to the broker: Network Error : websocket: bad handshake
2020/08/09 02:13:36 CLIENT 72 had error connecting to the broker: Network Error : websocket: bad handshake
......

so, i was wondering hot to make a successful websocket test?

Would it be possible to add a new command-line argument to the mqtt-benchmark tool, like:

mqtt-benchmark --connection-duration 10000

When specified, mqtt-benchmark would keep the connections open for all clients for the specified duration, in this case, 10 seconds. This would allow users to customize the connection duration for benchmarking purposes and better understand how the MQTT broker performs under different connection durations.

Can I send custom payload messages?Includes strings and hexadecimal types

It would be handy to have placeholders in the topic field.
For example "/topic/%i" become "/topic/1" when connected by a client with ID 1.

Client ID would be one field. A random unique number would be also nice.

When --clients 1 is activated no json is displayed

I want to subscribe the topic. Does it support?

Hello,

2021/03/12 19:19:32 CLIENT 2524 had error connecting to the broker: Network Error : dial tcp mymqttip:1883: socket: too many open files

Tryin to run with 10k connections and i start to get this pretty quick, any ideas what I need to do ?

running on mac os big sur 11.2

JSON not showing result but it publishes mqtt payload.
Txt result work perfectly

compiling from github source