Outcome 5: parallel/interleaved replication execution design#177
Open
DianaMeda wants to merge 1 commit into
Open
Outcome 5: parallel/interleaved replication execution design#177DianaMeda wants to merge 1 commit into
DianaMeda wants to merge 1 commit into
Conversation
Design deliverable for the parallel-execution challenge (Jumbo goal fa0394d4): a design doc, not implementation. - docs/parallel-replication-design.md: bounded worker-pool model with a --concurrency N knob and an order-independent runWithConcurrency primitive; resource-contention analysis for non-API agent harnesses (rate limits as the binding constraint) with a recommended default N=1; arm-interleaving go/no-go (GO, per-session alternation); decomposition into follow-on implementation goals; and resolution of GOAL.md's two open questions. Key finding: parallelism does not bias the measurement (all scored dimensions are artefact/count-based, not wall-clock; aggregateReplications is order-independent), so concurrency risks are operational, not statistical. Two decisions registered in Jumbo (default concurrency = 1; arm interleaving = GO). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The design for the parallel-execution challenge (GOAL.md Challenges) — a docs-only deliverable, no implementation. Branches off
main, independent of the open Outcome 4/5 code PRs.docs/parallel-replication-design.mdcovers:--concurrency Nknob and a pure, order-independentrunWithConcurrencyprimitive.aggregateReplicationsis order-independent. So concurrency risks are operational (rate limits, OOM, failures), not statistical.ab-runnerrefactor, orthogonal to the worker pool.Decisions
Registered in the evals Jumbo project (dogfooding): default replication concurrency = 1 (opt-in higher); arm interleaving = GO (independent goal).
Scope
Design only — the implementation goals it decomposes are follow-ons.
🤖 Generated with Claude Code