[SERVER-73460] Ticket adjustment algorithm based on maximizing throughput Created: 30/Jan/23  Updated: 29/Oct/23  Resolved: 09/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-73312 Periodic task for ticket adjustment Closed
is depended on by SERVER-73710 Smarter throughput probing step size Closed
is depended on by SERVER-73713 Throughput probing interval size calc... Closed
is depended on by SERVER-73715 Investigate counting immediate priori... Closed
is depended on by SERVER-73716 Compatibility between concurrency adj... Closed
is depended on by SERVER-73764 Adjust throughput probing logging Closed
is depended on by SERVER-73775 Determine how to proportion read/writ... Closed
is depended on by SERVER-73824 Unit tests for throughput probing Closed
Duplicate
is duplicated by SERVER-71708 Dynamically adjust maximum number of ... Closed
is duplicated by SERVER-71709 Dynamically adjust maximum number of ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2023-02-20, Execution Team 2023-02-06
Participants:

 Description   

One idea for an algorithm to adjust the level of storage engine concurrency is to probe the value being used in order to maximize throughput.



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

Author:

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

Message: SERVER-73460 Probe throughput to adjust storage engine concurrency
Branch: master
https://github.com/mongodb/mongo/commit/dbee863b94f9da85fe5144153a1168af8e32f37d

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