Skip to content

Scheduling: fair bounded admission for interactive, write and background work #176

Closed

Description

@jsam

Problem

Query, write, proof and subscription workloads need bounded admission without starving final subscription state or writers under sustained load.

Evidence

Source: 5c1f313379a5cb2995a43a66ddba0b5cc9798b7f (inspected 2026-10-03). These are source findings; the acceptance scenarios below still need implementation and execution.

Acceptance criteria

  • Reuse one admission policy with configurable measured lane sizes, bounded queues and deadlines; avoid a new global evaluator lock.
  • Saturate each workload class and demonstrate bounded waits, background progress, no writer starvation and no lost final subscription state.
  • Return honest overload/timeout errors and release counters on cancellation or disconnect.
  • Run mixed cheap queries, writes, refreshes and proofs through Performance: baseline and mandatory pre-PR regression pipeline #163.

Delivery

Plan item: E02. R3 - Streaming SDK subscriptions.

Dependencies / related work: #173, #175.

Contributes to #132; completing this slice alone does not close the broader issue.

Activity

  1. added
    backendBackend/server related
    P1Required next for reliable reactive delivery and operations
    on Oct 3, 2026
  2. jsam commented on Oct 4, 2026

    @jsam
    ContributorAuthor

    Moved to the Engine production readiness milestone, the current focus (tracker #199). EN-14: fair bounded admission, so reads and bulk writes inside one engine cannot starve each other.

    Roadmap per the neurosymbolic decision layer plan: engine production readiness first, then gateway neural integration with Jev, CLM and Laya (#266).

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

    P1Required next for reliable reactive delivery and operationsbackendBackend/server related

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions