1. 11 11月, 2015 1 次提交
  2. 10 11月, 2015 3 次提交
  3. 09 11月, 2015 2 次提交
    • P
      update Gemfile.lock · ddd3dd72
      Pirate Praveen 提交于
      ddd3dd72
    • Y
      Added Sherlock, a custom profiling tool for GitLab · dec3e4ce
      Yorick Peterse 提交于
      Sherlock will be a new GitLab specific tool for measuring the
      performance of Rails requests (and SideKiq jobs at some point). Some of
      the things that are currently tracked:
      
      * SQL queries along with their timings, backtraces and query plans
        (using "EXPLAIN ANALYZE" for PostgreSQL and regular "EXPLAIN" for
        MySQL)
      * Timings of application files (including views) on a per line basis
      * Some meta data such as the request method, path, total duration, etc
      
      More tracking (e.g. Rugged or gitlab-shell timings) might be added in
      the future.
      
      Sherlock will replace any existing tools we have used so far (e.g.
      active_record_query_trace and rack-mini-profiler), hence the
      corresponding Gems have been removed from the Gemfile.
      
      Sherlock can be enabled by starting Rails as following:
      
          ENABLE_SHERLOCK=1 bundle exec rails s
      
      Recorded transactions can be found at `/sherlock/transactions`.
      dec3e4ce
  4. 04 11月, 2015 2 次提交
  5. 26 10月, 2015 2 次提交
  6. 16 10月, 2015 1 次提交
  7. 15 10月, 2015 4 次提交
    • Y
      Added rack-lineprof for development · d4832b03
      Yorick Peterse 提交于
      This can be used to measure the time (roughly) spent on a per line
      basis. This can also be used to measure timings for views, for example
      by adding the following to a URL:
      
         ?lineprof=app/views/projects/notes/_note
      
      rack-lineprof is only enabled when:
      
      1. The application runs in development mode
      2. The used Ruby is MRI
      3. The environment variable ENABLE_LINEPROF is set to a non-empty value
      d4832b03
    • Y
      Added active_record_query_trace · 7971ed5d
      Yorick Peterse 提交于
      This can be used to track down where queries originate from, regardless
      of whether they're caused by N+1 problems or not. This can be enabled by
      setting the environment variable ENABLE_QUERY_TRACE to a non-empty value
      (e.g. "true").
      7971ed5d
    • Y
      Added Bullet to the Gemfile · fa3d7db3
      Yorick Peterse 提交于
      This can be used to resolve N+1 query problems. Bullet is disabled by
      default and can be enabled by starting Rails with the environment
      variable ENABLE_BULLET set to a non empty value (e.g. "true").
      fa3d7db3
    • J
      Update gitlab_git to 7.2.19 · 83f04853
      Jacob Vosmaer 提交于
      83f04853
  8. 14 10月, 2015 1 次提交
  9. 13 10月, 2015 1 次提交
  10. 12 10月, 2015 1 次提交
  11. 09 10月, 2015 3 次提交
  12. 08 10月, 2015 5 次提交
  13. 07 10月, 2015 4 次提交
  14. 02 10月, 2015 1 次提交
  15. 01 10月, 2015 1 次提交
  16. 25 9月, 2015 1 次提交
  17. 24 9月, 2015 3 次提交
  18. 20 9月, 2015 2 次提交
  19. 18 9月, 2015 1 次提交
  20. 16 9月, 2015 1 次提交