[SERVER-73715] Investigate counting immediate priority operations in throughput probing algorithm Created: 07/Feb/23  Updated: 28/Mar/23  Resolved: 28/Mar/23

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

Type: Task Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Noma
Resolution: Won't Do 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
Sprint: Execution Team 2023-02-20, Execution Team 2023-03-06, Execution Team 2023-03-20, Execution Team 2023-04-03
Participants:

 Description   

The throughput probing algorithm for execution control currently doesn't not take into consideration any operations with immediate priority when calculating throughput.



 Comments   
Comment by Gregory Noma [ 28/Mar/23 ]

Because immediate-priority operations don't take tickets, we shouldn't consider them as a part of the throughput calculation. It doesn't make sense for an input to the the function to be something that isn't controlled by its output. Even without counting immediate-priority operations the algorithm should still behave as intended; if there are are large number of immediate-priority operations impacting the performance of non-immediate-priority operations, the throughput of those operations will go down and the algorithm will react appropriately.

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