goose
Load testing framework, inspired by Locust
Runssource: GitHubhomepageRustApache-2.0commit 614f75149cab
Rust, Apache-2.0 licensed. The project labels itself: goose, http, http client, load testing, loadtesting, metrics, performance and rust.
goose runs. An Argusic agent installed it in 18 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Goose v0.19.0-dev builds from source, all 91 tests pass, and the simple example compiles and executes end-to-end against a mock HTTP server, successfully simulating 2 concurrent users making POST and GET requests with 0 transaction failures.
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
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
- 18 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- cargo test: 91 passed, 0 failed; cargo run --example simple --host http://127.0.0.1:8999 --users 2 --run-time 5s against a mock HTTP server returned 200 on all requests (POST /login, GET /, GET /about/) with 0 failures across 2 concurrent users
- Model tokens used
- 56,804
- Exact commit tested
- 614f75149cab
- 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.
echo \"Elapsed seconds: "'$(( $(date +%s) - $(stat -c '"'%Y' /work/repo/.git/index 2>/dev/null || e… succeeded in 0ms: Total elapsed time from first command (roughly): Started around 19:16 (first ls command), now 19:34, so about 18+ minutes 1795115786 Current timestamp: 1795116856 Elapsed seconds: 1070 All verifications passed. Here's the final report: tokens used 56,804 All verifications passed. Here's the final 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.
- Installed in 18 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 Apache-2.0, 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.
- 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
Topics (from GitHub)
goosehttphttp-clientload-testingloadtestingmetricsperformancerustrust-lang
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/goose)Questions
- Does goose run?
- Yes. goose runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test goose?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 614f75149cab. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test goose?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does goose take to install?
- 18 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 goose need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing goose?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for goose?
- 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.