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

I0923

Cold start and endpoint cost are benchmark targets like everything else

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
6
Waiting on
I0930
Holds back
I0932
Behind it in all
1
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 I0923

majordomus plan verify I0923

majordomus plan done I0923

What it is

Objective
Measure the cold start of the container and the cost of the cheap endpoints through the benchmark infrastructure the repository already has, and record them as baselines.
Why
A profile with no minimum running machines means every idle period ends with a cold start that a user pays for. A number nobody measured cannot be improved and cannot be defended.
Now
The benchmark command derives its targets from the command registry and holds a committed baseline. Nothing measures a container or an HTTP endpoint under deployment conditions.
Wanted
Process start to listening, process start to readiness and container start to readiness are recorded, the cheap endpoints have latency distributions under the constrained profile, and both are baselines the regression check knows about.
Done when
unknown: the record declares no `completion`
Risk
Container timings on a laptop and on a hosted machine differ enough that one cannot be a baseline for the other. The environment is part of the record.

Acceptance

  • Process start to listening, process start to readiness and container start to readiness are each measured separately
  • The cheap endpoints are benchmarked under the constrained resource profile with distributions rather than a single number
  • The measurements are recorded as artifacts through the existing benchmark infrastructure with the environment they were taken on
  • No cold-start guarantee is stated that the repeatability of the measurement does not support
Validation
majordomus bench --check
Evidence required
coldstart_measuredendpoint_benchbaseline_recorded
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
.ai/repo/benchmarks/rustapps/majordomus-cli/src/bench
Not
A load-testing frameworkA throughput claim derived from one machinePromising a cold-start guarantee from an unrepeatable measurement
Depends on
I0930
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.