Skip to content

Wire v2: responsive connection reader and bounded single writer #172

Closed

Description

@jsam

Problem

A long request on a subscription connection must not block unrelated pushes, and concurrent requests must not race session/KG changes.

Evidence

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

Acceptance criteria

  • Use an owned reader, bounded in-flight execution set and single ordered writer; document barriers for KG/session mutations.
  • Block a query for 500 ms while an external writer changes subscribed rows; deltas still meet the measured delivery budget.
  • Test KG switch plus insert ordering, overload and disconnect cleanup with bounded tasks/queues.
  • Pass saturated mixed query/write/delta measurements in Performance: baseline and mandatory pre-PR regression pipeline #163.

Delivery

Plan item: W02. R2 - Atomic programs + wire protocol.

Dependencies / related work: #171.

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

    Delivered by #214 (per-connection pipelining with barriers; e2e agent_receives_deltas_while_its_own_long_query_runs); verified on main 4adce1e.

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