[SERVER-82559] Add coverage for different amounts of rate limiting Created: 30/Oct/23 Updated: 06/Nov/23 Resolved: 06/Nov/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Erin Zhu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
While discussing the rollout plan for query stats, we considered different levels of rate limiting. We don't have great data on this. To help make decisions like this in the future, it would be great to run our high value benchmarks on a couple different rate limit variants, so we can summarize the expected impact better. As a start/guess, maybe we should have: 1, 10, 100, 1000, 10000? 100 already exists. |
| Comments |
| Comment by Githook User [ 06/Nov/23 ] |
|
Author: {'name': 'Erin Zhu', 'email': 'erin.zhu@mongodb.com', 'username': 'erinzhu001'}Message: |