Add coverage for different amounts of rate limiting

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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. 

            Assignee:
            Erin Zhu
            Reporter:
            Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: