Skip to content

[EPIC] Performance #206

Description

@gjanco

Outcome

AURA performance is measured against real workloads, and actionable runtime bottlenecks improve without correctness or observability regressions.

Scope

  • Scheduling delays between ready tasks.
  • Long periods without useful streaming output.
  • Remaining measured session, trace-loading, filesystem, and synchronization costs.
  • Performance attribution using the metrics owned by [EPIC] Data Accuracy & Eval Readiness #205.

Earlier investigation closed #226, #227, and #228 after measurement showed no actionable production blocker. Benchmark wall time must not be attributed to AURA when it is owned by the harness.

Complete when

  • Performance claims use instrumented, reproducible workloads.
  • Material AURA-owned bottlenecks have thresholds and regression coverage.
  • Reports separate AURA, model/provider, tool, and harness contributions where possible.
  • Optimizations preserve output correctness and trace fidelity.

Activity

  1. added theissue type on Jun 10, 2026
  2. changed the title [-]Performance[/-] [+][EPIC] Performance[/+] on Jun 10, 2026
  3. Shearerbeard commented on Jul 17, 2026

    @Shearerbeard
    Collaborator

    Vetting pass 2026-07-17: all five child mechanisms exist in code, and measurement closed three of them: #226 (drain measured 0ms in practice), #227 (rebuild sub-5ms on all three providers), #228 (clone bounded and necessary). #224 and #225 stay open, both rescoped by evidence, both gated on #205/#218 instrumentation for real magnitudes. The terminalbench 3.8x note should be read against the newer S8/S26 finding that ~63% of bench wall-clock is harness blind-sleep, not orchestration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions