[DOC-14585][AI] Correct the Disk i/o optimized thread count - #4165
Draft
TimLFletcher wants to merge 1 commit into
Draft
TimLFletcher wants to merge 1 commit into
TimLFletcher wants to merge 1 commit into
Conversation
Data Settings stated that Disk i/o optimized allocates threads equal to the number of CPU cores on the node. It allocates twice that number. Reported by Daniel Owen against the 7.6 page, which carries the same claim in different wording. See the PR for the other affected branches. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This was referenced Sep 9, 2026
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
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.
Fixes DOC-14585.
@daniel Owen reported this, so he is the right person to confirm the number.
What changed
modules/manage/pages/manage-settings/general-settings.adoc:224, in Data Settings.Only occurrence of the claim on this branch.
Open questions for the reviewer
release/7.6? The ticket cites the 7.6 page, and 7.6 carries the same claim at line 181 ("The number of threads allocated is equal to the number of CPU cores for the node"). It is a different Server generation, so the allocation may genuinely have differed. If it is also 2x there, that branch needs the same change.release/8.5has the identical sentence to this branch and needs the same change. Happy to raise that PR on confirmation, or now if you would rather not wait.Affected branches
release/8.0release/8.5release/7.6Verification
The build confirms the page still renders. It cannot confirm the number, which is question 1.
🤖 Generated with Claude Code