https://github.com/jeffallen/mqtt

MQTT Clients and Servers in Go
https://github.com/jeffallen/mqtt

Last synced: 4 days ago
JSON representation

MQTT Clients and Servers in Go

• Host: GitHub
• URL: https://github.com/jeffallen/mqtt
• Owner: jeffallen
• License: other
• Created: 2013-12-05T10:48:10.000Z (about 11 years ago)
• Default Branch: master
• Last Pushed: 2023-12-08T08:18:28.000Z (about 1 year ago)
• Last Synced: 2025-02-09T16:04:38.717Z (11 days ago)
• Language: Go
• Size: 61.5 KB
• Stars: 825
• Watchers: 64
• Forks: 139
• Open Issues: 4
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
mqtt

====

MQTT Clients, Servers and Load Testers in Go

For docs, see: http://godoc.org/github.com/jeffallen/mqtt

For a little discussion of this code see: http://blog.nella.org/mqtt-code-golf

Limitations

-----------

At this time, the following limitations apply:

 * QoS level 0 only; messages are only stored in RAM

 * Retain works, but at QoS level 0. Retained messages are lost on server restart.

 * Last will messages are not implemented.

 * Keepalive and timeouts are not implemented.

Servers

-------

The example MQTT servers are in directories mqttsrv and smqttsrv (secured with TLS).

Benchmarking Tools

------------------

To use the benchmarking tools, cd into pingtest, loadtest, or many and type "go build". The tools have reasonable defaults, but you'll also want to use the -help flag to find out what can be tuned.

All benchmarks suck, and these three suck in different ways.

pingtest simulates a number of pairs of clients who are bouncing messages between them as fast as possible. It aims to measure latency of messages through the system when under load.

loadtest simulates a number of pairs of clients where one is sending as fast as possible to the other. Realistically, this ends up testing the ability of the system to decode and queue messages, because any slight inbalance in scheduling of readers causes a pile up of messages from the writer slamming them down the throat of the server.

many simulates a large number of clients who send a low transaction rate. The goal is to eventually use this to achieve 1 million (and more?) concurrent, active MQTT sessions in one server. So far, mqttsrv has survived a load of 40k concurrent connections from many.