Skip to content

[BUG]: saving state stalls the orchestration loop each iteration #226

Description

@gjanco
    • claimed: 50-200ms per iteration (orchestrator.rs:3439-3452)

Activity

  1. Shearerbeard commented on Jul 17, 2026

    @Shearerbeard
    Collaborator

    Vetted 2026-07-17 against an instrumented main build. The drain await is real (run_iteration blocks on persistence.drain once per iteration, orchestrator.rs:3724) but measured cost was 0ms in all nine sampled iterations. The fast path returns immediately when no writes are in flight, and the worst case is capped by persistence_drain_timeout_ms (default 2000ms). The 50-200ms estimate has no support in practice. Closing. If large-artifact workloads ever show drain time in a profile, #218's instrumentation is the way to see it.

  2. changed the title [-]Persistence drain barrier[/-] [+][BUG]: saving state stalls the orchestration loop each iteration[/+] on Jul 17, 2026
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

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions