saq

Simple Async Queues

Runssource: GitHubhomepagePythonMITcommit 525acc9251c9

Python, MIT licensed. The project labels itself: asyncio, message queue, python, queue and redis.

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

SAQ installed in a venv with Redis built from source, all 122 runnable tests pass against the live Redis instance, and the CLI tool prints its help and runs health checks 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.10 (measured)
recorded runs
2
last tested
stars
901
forks
78
open issues
0
watchers
18
size
1 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 saq, 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.

  • Docker not available to start Redis and Postgres containers10 minutes
  • PostgreSQL library libpq not found, psycopg backend failed to load1 minute
  • pip install failed due to externally-managed-environment (PEP 668)1 minute
Install time
30 minutes
Cold machine to finish
13 minutes
Errors hit and fixed
3 hit, 3 fixed with no human help
How the result was proved
python -m unittest tests.test_utils tests.test_settings_import tests.test_migrations tests.test_runner tests.test_http_retry tests.test_queue.TestRedisQueue tests.test_job.TestJobRedisQueue tests.test_worker.TestWorkerRedisQueue tests.test_worker.TestHttpRedis - exited 0, 122 passed, 1 skipped; saq --help prints usage; redis-cli PONG confirmed; saq test_sett_mod.settings --check confirmed health check logic runs against live Redis
Model tokens used
186,765
Exact commit tested
525acc9251c9
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.

import time
start = time.time()
# The whole process start was at script invocation
# Let's measure from earliest reasonable start
print(start)
\"" in /work/repo
 succeeded in 0ms:
1795226251.8529415
The total process was well under 90 minutes. Let me clean up (leave Redis running) and report:
tokens used
186,765
The total process was well under 90 minutes. Let me clean up (leave Redis running) and report:

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.
  • Recovered from all 3 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 did not, or is not known

  • Took 30 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.

Of the 4 asyncio projects Argusic has installed and timed, saq was the 4th fastest to reach a running state, and 4 of 4 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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.10
Argusic Runner1/3Runs100.000.04

Topics (from GitHub)

asynciomessage-queuepythonqueueredis

Embed the badge

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

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

Questions

Does saq run?
Yes. saq runs. Argusic installed and launched it on a clean machine in 30 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test saq?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 525acc9251c9. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test saq?
The run that produced this verdict cost $0.10: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does saq take to install?
30 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 saq need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing saq?
3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does saq compare with the alternatives?
Of the 4 asyncio projects Argusic has installed and timed, saq was the 4th fastest to reach a running state, and 4 of 4 reached one at all.
Where is the evidence for saq?
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