Skip to content

runtime: measure and reduce image and idle-memory footprint #107

Description

@RatulMaharaj

Problem

The project intentionally ships a minimal runtime, but image size and idle RSS are not enforced product budgets. Plan 11 proposes measurement, caps, a compiled slim image, and a hermetic distroless option.

Scope

  • Add image-size and idle-RSS measurement to CI.
  • Surface RSS in health/status.
  • Establish documented memory limits in generated deployments.
  • Evaluate compiled slim and hermetic distroless images with measured tradeoffs.
  • Add an explicit image-size regression budget.
  • Investigate MCP idle-disconnect or equivalent resident-memory control.

Acceptance criteria

Each release publishes measurable image and idle-memory characteristics, and regressions fail or require an explicit budget update.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Fields

    No fields configured for Task.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions