[SERVER-37864] Implement write op rate calculation mechanism Created: 01/Nov/18 Updated: 06/Dec/22 Resolved: 20/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Maria van Keulen | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Sprint: | Storage NYC 2018-12-03 | ||||||||
| Participants: | |||||||||
| Description |
|
The Replica Set Flow Control project is planned to add Additive Increase Multiplicative Decrease based throttling. AIMD based throttling operates based off of the current rate of operations. Since there is no present way to determine the current rate of operations directly, implement a new rate calculation mechanism as part of its own thread (separate from the location where the throttling is added). |
| Comments |
| Comment by Maria van Keulen [ 20/Feb/19 ] |
|
Closing this ticket, since it is specific to a flow control implementation that we chose not to pursue. |
| Comment by Maria van Keulen [ 01/Nov/18 ] |
|
The rate calculation should be separate from the location where throttling occurs, which is currently at the global lock level, before the global lock is acquired. We also want to calculate it periodically, and we discussed the best way to do this was via a periodic runner thread. |
| Comment by Andy Schwerin [ 01/Nov/18 ] |
|
Why as part of a separate thread? Separate from what? |