[SERVER-73456] Evaluate feasibility of rate limiting mutex Created: 30/Jan/23 Updated: 14/Sep/23 Resolved: 30/Aug/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Joshua Lapacik (Inactive) | Assignee: | Backlog - Query Integration |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Query Integration
|
||||||||||||||||||||
| Sprint: | QO 2023-06-26 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Currently all queries contend for the same rate limiting mutex. We will need to run some performance evaluations to determine if this is feasible or if we need to take alternative approach. |
| Comments |
| Comment by Charlie Swanson [ 30/Aug/23 ] |
|
After investigating this and merging |
| Comment by Davis Haupt (Inactive) [ 26/Jun/23 ] |
|
Some conclusions from initial investigations:
|
| Comment by Charlie Swanson [ 16/Jun/23 ] |
|
Got some perf dashboards up related to this topic. Left to explore: Can we improve it at all, and how close to the full "capacity" of ops/sec can we get before we have a notable impact? davis.haupt@mongodb.com I'm going to assign this to you for now as the person who might look at this more while I'm out next week. I'll also assign you |
| Comment by Charlie Swanson [ 26/Apr/23 ] |
|
Now that PERF-3974 has landed we should be able to see this in the dashboards. The answer might not be obvious until we've seen it run a couple times though. |