Updates serverStatus.mem.virtual #972
Closed
Conversation
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
Since journalling is on by default, rewording the serverStatus.mem.virtual section is needed. Removed the term "gigabytes", as this is subjective - a mem-map of 1MB shouldn't have 1GB as Virtual memory... But for 200GB, 1GB wouldn't be anything to worry about. A ratio of (for example) thrice mem-map, is better.
|
merged! |
jeff-allen-mongo
pushed a commit
that referenced
this pull request
Apr 18, 2022
* DOCS-15210 add readConcern mention * writeConcern -> write concern * CR 1 Feedback * update verbiage * remove duplicate your * remove ref * update
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.
Since journalling is on by default, rewording the serverStatus.mem.virtual section is needed.
Removed the term "gigabytes", as this is subjective - a mem-map of 1MB shouldn't have 1GB as Virtual memory... But for 200GB, 1GB wouldn't be anything to worry about. A ratio of (for example) thrice mem-map, is better.