Skip to main content

Developer Performance Reference

Metadata​

  • Owner: Origo Engineering
  • Last updated: 2026-04-16
  • Slice/version reference: S60

Purpose​

  • Developer reference for the whole-system performance registry, the path-scoped performance gate, and the recurring monthly load-proof home.
  • Governance authority remains in:
    • contracts/governance/performance-sla.json

Machine contracts​

  • contracts/governance/performance-sla.json
  • contracts/governance/ingest-throughput.json
  • contracts/governance/observability-as-proof.json
  • contracts/governance/observability-day-zero.json
  • contracts/governance/historical-surface.json
  • contracts/governance/platform-stack.json

Runtime and code anchors​

  • Registry loader and path matching:
    • origo/performance/registry.py
  • Path-scoped gate script:
    • scripts/validate_performance_scope.py
  • Gate workflow:
    • .github/workflows/performance-gate.yml
  • Monthly proof job:
    • control-plane/origo_control_plane/jobs/monthly_load_proof.py
  • Monthly proof implementation:
    • control-plane/origo_control_plane/performance/monthly_load_proof.py
  • Dagster definitions:
    • control-plane/origo_control_plane/definitions.py
  • Exchange-family runtime authority:
    • control-plane/origo_control_plane/backfill/s34_contract.py
    • control-plane/origo_control_plane/backfill/runtime_contract.py
    • control-plane/dagster.yaml
  • Shared exchange transport:
    • control-plane/origo_control_plane/utils/exchange_stage_transport.py

Key rules​

  • Numeric performance truth lives only in performance-sla.json.
  • ingest-throughput.json may contribute scoped ingest doctrine, but it must not remain a competing numeric authority.
  • Governed paths are keyed by runtime unit plus explicit measurement shape.
  • hard_sla requires a numeric budget.
  • evidence_building is first-class and mandatory when repeatable governed evidence is not yet sufficient.
  • Env and deploy capacity surfaces are first-class touched-path inputs, not incidental tuning.
  • The monthly proof job is Dagster-native and visible in Dagit.
  • The initial monthly proof is intentionally explicit about probe support:
    • supported probes run real measurements
    • unsupported paths are recorded as registry_audit_only
    • unsupported paths stay visible until future slices tighten them
  • Daily-file exchange performance is a shared family concern:
    • Binance, OKX, and Bybit each have their own governed path id
    • family membership authority lives in s34_contract.py
  • Shared exchange hot-path boundary starts only after source-specific parse, integrity, normalization, and proof-input construction.
  • Shared path duties are:
    • ClickHouse-native stage transport
    • set-based staged proof/write work
    • shared performance evidence collection
  • Source-specific proof identity construction remains source-specific unless a future slice proves a safe shared abstraction.
  • Python .to_list() materialization is forbidden on the exchange stage boundary.
  • Hidden HTTP/raw stage transport fallback is forbidden on the exchange hot path.
  • Operator-performance concurrency is distinct from source-safe concurrency:
    • source-safe stays in contracts/source-pressure-v1.json
    • performance-safe stays in s34_contract.py
    • Dagster user-facing exchange runs must honor the lower of the two