- 09 Feb, 2017 1 commit
-
-
Filipa Lacerda authored
-
- 31 Dec, 2016 2 commits
-
-
Kushal Pandya authored
-
Kushal Pandya authored
-
- 06 Jun, 2016 1 commit
-
-
Alejandro Rodríguez authored
Remember to configure your `better_errors` editor to point to your program of preference
-
- 04 May, 2016 1 commit
-
-
Annabel Dunstone authored
-
- 18 Jan, 2016 1 commit
-
-
Yorick Peterse authored
-
- 13 Jan, 2016 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 24 Nov, 2015 1 commit
-
-
Yorick Peterse authored
This makes it easier to see if a problem is caused by slow queries or slow Ruby code (unrelated to any SQL queries that might be used).
-
- 09 Nov, 2015 3 commits
-
-
Yorick Peterse authored
This ensures that long URLs don't completely mess up the layout of the table.
-
Yorick Peterse authored
-
Yorick Peterse authored
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`.
-