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

I0910

The release profile is chosen by measurement, not by folklore

Where it stands

devtask.issue
Readiness
blocked 1 of its dependencies is not DONE
Status
BLOCKED
Can start
not now
Milestone
fly-deployment
Milestone status
ACTIVE
Wave
4
Waiting on
I0909
Holds back
I0921
Behind it in all
3
Evidence
0 of 2
In the waySubjectDetail
issueI0909I0909 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 I0910

majordomus plan verify I0910

majordomus plan done I0910

What it is

Objective
Measure the size, startup, memory and latency consequences of the candidate release configurations and select the smallest one that does not regress runtime behaviour materially, recording the decision and the numbers.
Why
Every list of Cargo size flags on the internet is asserted rather than measured, and several of them trade startup or throughput for megabytes. The repository already refuses claims without evidence.
Now
The workspace has its existing release profile and no deployment-specific profile. No size or startup numbers exist for any configuration.
Wanted
A deployment profile exists if and only if it is justified by measurement, the existing release semantics are unchanged for everyone else, and the numbers behind the decision are recorded.
Done when
unknown: the record declares no `completion`
Risk
panic=abort changes observable behaviour for a process that currently unwinds. If any test or capability depends on unwinding, the flag costs correctness rather than bytes.

Acceptance

  • Binary size, container size, startup to readiness, resident memory and endpoint latency are measured for the existing release profile and for each candidate configuration
  • The chosen configuration is the smallest that does not regress runtime behaviour materially, and the threshold for material is stated
  • The measurements are recorded as artifacts through the existing benchmark infrastructure rather than pasted into prose
  • The decision is captured where a reader can find the reasoning, and the existing release profile stays valid for local builds
Validation
cargo test --workspace --all-featuresmajordomus bench --check
Evidence required
profile_measuredprofile_chosen
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
Cargo.toml.ai/repo/benchmarks/rust
Not
Profile-guided optimisationAny target-cpu setting that assumes the build host's processorChanging the existing release profile's semantics for local development
Depends on
I0909
Priority
p1
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-09-06
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.