varmq

A Simplest in-memory and Distributed Storage-Agnostic Message Queue for Your Concurrent Go Program

Runssource: GitHubhomepageGoMITcommit 1f9d9b588f73

Go, MIT licensed. The project labels itself: concurrency, distrubted systems, go, goroutine, goroutine pool, message queue, persistence and pool.

varmq runs. An Argusic agent installed it in 1.2 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

VarMQ builds and all 93 tests pass across 7 modules (config, distributed, job, main, metrics, mux, queue, workers, and internal components); benchmarks also execute successfully.

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.02 (measured)
recorded runs
1
last tested
stars
209
forks
21
open issues
13
watchers
2
size
71 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.

Install time
1 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
go test -count=1 -timeout 5m -v ./... exited 0; 93 tests passed across 7 modules. go test -bench=. -benchmem -count=1 -timeout 5m ./... also exited 0 with benchmark results for all worker/queue types.
Model tokens used
75,930
Exact commit tested
1f9d9b588f73
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

The end of the recording

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

```
tokens used
75,930
Everything is clean. Here's the final report:
**Install**: Downloaded Go 1.24.0 (no Go in container initially), ran `go mod tidy` to fetch deps.
**Build**: `go build ./...` exited 0 with no errors.
**Tests**: All 93 tests passed across 7 modules; no failures.
**Benchmarks**: `go test -bench=. -benchmem` completed successfully across all worker/queue combina…
**Lint**: `go vet ./...` emitted no warnings.
```json
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 1.2, "errors": [], "test_d…
```

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 1.2 minutes.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 1.2 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

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 Runner1/3Runs100.000.02

Topics (from GitHub)

concurrencydistrubted-systemsgogoroutinegoroutine-poolmessage-queuepersistencepoolpriority-queuequeueworkerworker-pool

Embed the badge

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

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

Questions

Does varmq run?
Yes. varmq runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test varmq?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1f9d9b588f73. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test varmq?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does varmq take to install?
1.2 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 varmq need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing varmq?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for varmq?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion