[SERVER-44145] Validate cmd throughput throttle only throttles when the limit (maxValidateMBperSec) is exceeded Created: 22/Oct/19  Updated: 29/Oct/23  Resolved: 26/Aug/20

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

Type: Improvement Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: intern_validate_improvements
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2020-09-07
Participants:

 Description   

For example, maxValidateMBperSec is set to 1 MB and we load a 5 MB document. We only wait 1 second, not 5 seconds.



 Comments   
Comment by Githook User [ 26/Aug/20 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-44145 Validate throttle cursor should wait longer when data limit is exceeded

When validate reads a document that exceeds maxValidateMBperSec, wait a period
of time propotional to how much extra data we read, rather than just 1 second.
Branch: master
https://github.com/mongodb/mongo/commit/cef5fedff77cc1719470310bf765f358396ba017

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