We already have the DataThrottle class that together with the ThrottleCursors used in collection validate enforce 'maxValidateMBperSec' per validate cmd.
We could add something to keep track of MB/sec in general to DataThrottle; then we'd need to attach the information regularly to the curOp output.
- is documented by
-
DOCS-13165 Investigate changes in SERVER-43815: Validate cmd should report MB of I/O per second in curOp so that users can make more informed use of throttling via the 'maxValidateMBperSec' server parameter
- Closed
- mentioned in
-
Page Loading...