docs(fusillade): drop stale serial-discovery claim from archive README - #1722
Open
detail-app[bot] wants to merge 2 commits into
Open
detail-app[bot] wants to merge 2 commits into
detail-app[bot] wants to merge 2 commits into
Conversation
Deploying control-layer with
|
| Latest commit: |
2426481
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://827fc111.control-layer.pages.dev |
| Branch Preview URL: | https://detail-fix-docs-docs-fusilla.control-layer.pages.dev |
…rial-discovery-claim-f-80f8d0
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.
Removed the sentence "Discovery stays serial (one index probe per
candidate), so scaling flattens well past the recommended range" from
the batchless-archive drain recipe in fusillade/README.md. The paged
discovery change (one probe returning up to max_groups+1 candidates)
made this claim stale; serial per-candidate probing no longer bounds
the pass's scaling.
An operator sizing the drain for content past retention would read
this and wrongly assume adding backfill concurrency yields no
throughput past the recommended range, when the actual bottleneck is
now the write path (already documented in the same section).
Introduced by commit 79c549b (@pjb157, #1716)
Doc Drift PRs can be configured here.