[DOCS-12958] Investigate changes in SERVER-42224: Add a server parameter maxValidateMBPerSec to specify max validate throughput per validate command in order to limit I/O and CPU usage Created: 15/Aug/19  Updated: 13/Nov/23  Due: 09/Mar/20  Resolved: 05/Mar/20

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 4.3.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-42224 Add a server parameter maxValidateMBP... Closed
Related
related to DOCS-13681 Undocument background : true Closed
is related to DOCS-13157 Investigate changes in SERVER-30357: ... Closed
Participants:
Days since reply: 3 years, 33 weeks, 1 day ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

New server parameter that can be set at startup or runtime called 'maxValidateMBperSec' which takes an int.

The parameter ensures that while running the 'validate' command, each 'validate' command running at that time will limit the amount of data processed to maxValidateMBperSec in order to limit I/O and CPU usage.

Defaults to 0, which turns off throttling.

Description of Linked Ticket

This task should add the new server parameter that can be set via the server startup command line invocation and dynamically while the server is running.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 23/Jun/20 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: Revert "DOCS-12958: 4.4 maxValidateMBPerSec parameter" per DOCS-13681

This reverts commit 629d83a63c897333a593c7d01eec571539dae647.
Branch: master
https://github.com/mongodb/docs/commit/06fedf93df3b00bdf8f0ace5aae99f339a4450a7

Comment by Kay Kim (Inactive) [ 23/Jun/20 ]

Will revert pert DOCS-13681

Comment by Githook User [ 05/Mar/20 ]

Author:

{'name': 'Kay Kim', 'username': 'kay-kim', 'email': 'kay.kim@10gen.com'}

Message: DOCS-12958: 4.4 maxValidateMBPerSec parameter
Branch: master
https://github.com/mongodb/docs/commit/629d83a63c897333a593c7d01eec571539dae647

Comment by Dianna Hohensee (Inactive) [ 21/Oct/19 ]

Expanding on the downstream summary:

maxValidateMBPerSec only affects validate cmds running with [background:true} specified. maxValidateMBPerSec defaults to 0, which is interpreted as off and no throttling will occur. Each validate cmd will obey maxValidateMBPerSec separately. They do not share throttling. So, if maxValidateMBPerSec is set to 5, three concurrently running validate w/ {background:true} cmds will throttle at 15 MB per sec, each staying below 5 MB for itself.

maxValidateMBPerSec is a startup and runtime server parameter. Already running validate cmds will pick up on a change to maxValidateMBPerSec and act accordingly – so if a background validate cmd is causing too much performance degradation, the user can set maxValidateMBPerSec such that validation uses less resources.

maxValidateMBPerSec will have no affect on validate cmds where {background:true} is not specified.

Generated at Thu Feb 08 08:06:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.