Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-80006

Investigate best lock for holding the rate limiter mutex

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Query Integration

    Description

      We are still discussing if we want to continue to use the current sliding window rate limiter or reconfigure to use sharding's queryAnalysis token bucket rate limiter. If we indeed continue to use the former, we should investigate which type of lock gives the best performance. We should use the google micro benchmark (rate_limiting_bm.cpp) and also flamegraphs to determine the performance of stdx::unique_lock, stdx::lock_guard or something lock free (William's idea).

      Attachments

        Activity

          People

            backlog-query-integration Backlog - Query Integration
            maddie.zechar@mongodb.com Maddie Zechar
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: