Skip to content

Verify bounded streaming and preserve confirmed throughput evidence - #10

Merged
liran merged 1 commit into
mainfrom
randy/bounded-stream-execution
Oct 4, 2026
Merged

liran merged 1 commit into
mainfrom
randy/bounded-stream-execution

Conversation

@liran

@liran liran commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

The blackbox suite now verifies bounded bidirectional execution against fixed SDK/protocol releases and an immutable merged Weir source. It checks confirmed prefixes after stream failures and single-RPC reads of 64 MiB and 256 MiB across distinct documents, including result credits and sampled server RSS. Throughput evidence uses Execute counters, preserves confirmed successes and configures the workload's declared maximum read size so conservative reservations do not introduce an artificial admission bottleneck.

Independent review, offline race tests, vet and dependency/script checks pass. Real MongoDB and Elasticsearch multi-node integration and the Lua comparison smoke pass locally; CI runs the locked-source blackbox suite and independent single-record saturation matrices for reads, mixed traffic and writes.

@liran liran self-assigned this Oct 4, 2026
@liran
liran merged commit 3cc78d2 into main Oct 4, 2026
5 checks passed
@liran
liran deleted the randy/bounded-stream-execution branch October 4, 2026 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant