rmqtt

MQTT Server/MQTT Broker - Scalable Distributed MQTT Message Broker for IoT in the 5G Era

Runssource: GitHubhomepageRustMITcommit f57d95ec10d1

Rust, MIT licensed. The project labels itself: 5g, broker, cluster server, ecosystem, hivemq, iot, iot broker and iot middleware.

rmqtt runs. An Argusic agent installed it in 9 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

RMQTT broker v0.25.0 builds from source and runs: MQTT pub/sub roundtrip verified on port 1883, HTTP API returns 200 on /api/v1/stats, 53 unit/doc tests pass, mqtt_harness test binary builds.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.14 (measured)
recorded runs
2
last tested
stars
1,069
forks
141
open issues
24
watchers
20
size
14 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing rmqtt, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • protoc (protobuf compiler) was not pre-installed, required by handy-grpc and pulsar build scripts1 minute
  • Rust toolchain not pre-installed1 minute
  • rmqtt.toml default log.dir=/var/log/rmqtt requires root0.5 minutes
  • rmqtt-http-api redb storage path defaults to /var/log/rmqtt/.cache/ which requires root
Install time
9 minutes
Cold machine to finish
20 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
paho-mqtt Python client connected to 127.0.0.1:1883, published Hello RMQTT! to test/topic, subscribed to same topic, received the message back (publish rc=0, subscribe received payload=Hello RMQTT!). HTTP GET http://127.0.0.1:6060/api/v1/stats returned HTTP 200 with valid node stats JSON. cargo test -p rmqtt-codec: 39 unit + 3 doc tests passed. cargo test --workspace --lib: 11 utils tests passed.
Model tokens used
391,896
Exact commit tested
f57d95ec10d1
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**Launch**: The broker started successfully, listening on all configured ports (MQTT/TCP 1883, MQTT…
**Verification**:
- MQTT publish/subscribe roundtrip tested with paho-mqtt Python client - succeeded
- HTTP API `/api/v1/stats` returned `200` with valid JSON stats
- Unit tests: 39 codec tests + 3 doc tests + 11 utils tests all passed
- `mqtt_harness` test binary builds and runs
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 9…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 9, "errors": [{"msg": "pro…
tokens used
391,896

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 9 minutes.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 9 minutes after the clone.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.14
Argusic Runner1/3Runs100.000.19

Topics (from GitHub)

5gbrokercluster-serverecosystemhivemqiotiot-brokeriot-middlewareiot-servermessage-brokermessage-busmessage-queuemessagingmqttpublisherpubsubrustsubscribertokio

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/rmqtt.svg)](https://argusic.com/subject/rmqtt)

Questions

Does rmqtt run?
Yes. rmqtt runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test rmqtt?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f57d95ec10d1. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test rmqtt?
The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does rmqtt take to install?
9 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does rmqtt need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing rmqtt?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for rmqtt?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion