[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: 12/Jul/19  Updated: 29/Oct/23  Resolved: 08/Aug/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Gabriel Villasana (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-42226 Use the maxValidateMBperSec server pa... Closed
Documented
is documented by DOCS-12958 Investigate changes in SERVER-42224: ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2019-08-12
Participants:

 Description   

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.



 Comments   
Comment by Githook User [ 08/Aug/19 ]

Author:

{'name': 'Gabe Villasana', 'email': 'villagab4@gmail.com', 'username': 'villagab4'}

Message: SERVER-42224 Add a server parameter maxValidateMBperSec to specify max validate throughput per validate command in order to limit I/O and CPU usage
Branch: master
https://github.com/mongodb/mongo/commit/321201823455e1c648b7c6bd4ae0a59d1b7115b8

Comment by Dianna Hohensee (Inactive) [ 26/Jul/19 ]

Leaning towards using loadRelaxed(), but TBD.

Comment by Dianna Hohensee (Inactive) [ 12/Jul/19 ]

Would calling <atomic_server_param_variable>.load() for every collection/index document we load be a perf hit?

Comment by Geert Bosch [ 12/Jul/19 ]

1. There should be no default: if the parameter is not specified, we go as fast as we can.
2. Yes, that's why it is a parameter. The idea is that if an ongoing validation is causing operational issues (timeouts, cache pressure, etc.), the parameter can be changed to throttle down the validation.

Comment by Dianna Hohensee (Inactive) [ 12/Jul/19 ]

geert.bosch, two questions:
1. do you have a recommendation on a default value?
2. should a user be able to change maxValidateMBperSec while a validation command is running and expect the already in-progress validation command to obey the new maxValidateMBperSec value, or keep using the value is found when starting the command?

Generated at Thu Feb 08 04:59:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.