An error occurred fetching the project authors.
  1. 21 Nov, 2017 2 commits
  2. 20 Nov, 2017 1 commit
    • Stan Hu's avatar
      Optimize read-only middleware so that it does not consume as much CPU · 3c52e2f0
      Stan Hu authored
      In !15082, we changed the behavior of the middleware to call
      `Rails.application.routes.recognize_path` whenever a new route arrived.
      However, this can be a CPU-intensive task because Rails needs to allocate
      memory and compile 850+ different regular expressions, which are complicated
      in GitLab.
      
      As a short-term fix, we can do a lightweight string match before
      we do the heavier comparison.
      
      Closes #40185, gitlab-com/infrastructure#3240
      3c52e2f0
  3. 07 Nov, 2017 1 commit
  4. 02 Nov, 2017 1 commit
  5. 06 Oct, 2017 1 commit
    • Toon Claes's avatar
      Create idea of read-only database · d1366971
      Toon Claes authored
      In GitLab EE, a GitLab instance can be read-only (e.g. when it's a Geo
      secondary node). But in GitLab CE it also might be useful to have the
      "read-only" idea around. So port it back to GitLab CE.
      
      Also having the principle of read-only in GitLab CE would hopefully
      lead to less errors introduced, doing write operations when there
      aren't allowed for read-only calls.
      
      Closes gitlab-org/gitlab-ce#37534.
      d1366971