Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0922

The memory hypothesis is tested, not asserted

Where it stands

devtask.issue
Readiness
cancelled withdrawn
Status
CANCELLED
Can start
not now
Milestone
fly-deployment
Milestone status
ACTIVE
Wave
6
Waiting on
I0930
Holds back
I0931
Behind it in all
3
Evidence
0 of 3
In the waySubjectDetail
issueI0930I0930 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0922

majordomus plan verify I0922

majordomus plan done I0922

What it is

Objective
Run the production image under the intended memory limit, measure resident memory through a representative request sequence, and let the evidence decide the memory the deployment declares.
Why
The cheap profile rests on a guess about memory. Raising it because a run failed once is how a hosting bill quadruples; keeping it because it looks tidy is how a Machine gets killed under load. Only a measurement settles it.
Now
The canonical object states a memory hypothesis. Nothing has been run under any limit.
Wanted
Resident memory is measured at startup and after each representative request, the high-water mark is recorded, and the declared memory is the smallest value the evidence supports.
Done when
Cancelled 2026-10-14 on master e28daccd9b: the 256 MB limit it measures against is a Fly Machine size, and nothing reads the object's resources any more. The owner disconnected Fly.io on 2026-10-12; this repository deploys release binaries, the GHCR image and GitHub Pages (commit 9af3fa65a4 removed fly.toml).
Risk
A single machine's measurement is not a guarantee on another host. The high-water mark needs headroom, and the headroom needs to be stated.

Acceptance

  • The image runs under the declared limit and stays alive through the whole representative sequence
  • Resident memory is measured after startup and after a landing, documentation, API, OpenAPI and cockpit request, and the high-water mark is recorded
  • If the declared limit does not hold, the cause is diagnosed and the waste addressed before the limit is raised, and the raise is recorded with its evidence
  • The measurement is recorded through the existing benchmark infrastructure and becomes a regression budget
Validation
majordomus bench --checkbash test/run.sh
Evidence required
rss_measuredruns_at_limitbudget_recorded
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
.ai/repo/benchmarks/rust
Not
Raising the limit before diagnosing what consumed the memoryA load test; this is a resource envelope, not a throughput study
Depends on
I0930
Priority
p0
Profile
implementation
Parallel safe
true
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-09-06
Updated
2026-10-14
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.