[SERVER-73713] Throughput probing interval size calculation Created: 07/Feb/23  Updated: 29/Oct/23  Resolved: 02/May/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc1

Type: Task Priority: Major - P3
Reporter: Gregory Noma Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
depends on SERVER-73460 Ticket adjustment algorithm based on ... Closed
Documented
is documented by DOCS-16092 [SERVER] serverStatus metric renamed Closed
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0
Sprint: Execution Team 2023-02-20, Execution Team 2023-03-20, Execution Team 2023-05-01, Execution Team 2023-05-15
Participants:
Linked BF Score: 105

 Description   

For the initial implementation of the execution control throughput probing algorithm in SERVER-73460, the interval used in the throughput calculation is simply the number that was provided upon construction. However the actual interval may vary a bit based on scheduling delays etc, so we should consider using the actual amount of time instead.



 Comments   
Comment by Githook User [ 29/Apr/23 ]

Author:

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

Message: SERVER-73713 Calculate throughput interval based on actual time spent
Branch: v7.0
https://github.com/mongodb/mongo/commit/49af4d57fcb9e8a6579ed7c681a34f569104da89

Comment by Githook User [ 28/Apr/23 ]

Author:

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

Message: SERVER-73713 Calculate throughput interval based on actual time spent
Branch: master
https://github.com/mongodb/mongo/commit/4516323478dee93400bba87e18aff64c48173fbc

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