[DOC-14585][AI] Correct the Disk i/o optimized thread count (release/7.6) - #4167
Draft
TimLFletcher wants to merge 1 commit into
Draft
TimLFletcher wants to merge 1 commit into
TimLFletcher wants to merge 1 commit into
Conversation
…7.6) Same correction as PR #4165, applied to release/7.6. This is the page and the wording the ticket actually quotes. Whether the 2x allocation holds for 7.6 as well as 8.x is not established by the ticket. See the PR. Co-Authored-By: Claude Opus 5 <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.
Companion to #4165 and #4166. This is the branch whose page DOC-14585 actually quotes.
What changed
modules/manage/pages/manage-settings/general-settings.adoc:181, in Data Settings.The wording here differs from 8.x, so the edit is worded to match this branch rather than copied from #4165.
Open question for the reviewer, specific to this branch
Does the 2x allocation hold for 7.6, or only for 8.x?
@daniel Owen quoted this page, so the report is against 7.6 directly, which is the reason this PR exists. But the ticket does not say whether the behaviour is version-specific, and thread allocation is the kind of thing that changes between generations. If 7.6 really did allocate one thread per core, this PR should be closed and only #4165 and #4166 land.
Answering this needs someone who knows the 7.6 KV behaviour, not just the current behaviour.
The set
release/8.0release/8.5release/7.6Verification
🤖 Generated with Claude Code