[SERVER-73710] Smarter throughput probing step size Created: 07/Feb/23  Updated: 29/Oct/23  Resolved: 15/Feb/23

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

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

Issue Links:
Depends
depends on SERVER-73460 Ticket adjustment algorithm based on ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2023-02-20
Participants:

 Description   

For the initial implementation of the throughput-probing algorithm for execution control, the step size is always 4. We should look into smarter ways of choosing this step size, for instance based on a multiplication factor of the current number of tickets.



 Comments   
Comment by Githook User [ 15/Feb/23 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-73710 Determine throughput probing step size based on current concurrency level
Branch: master
https://github.com/mongodb/mongo/commit/d60f8a46afe5b5c87e2af9fd2498d08cd60558f9

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