summaryrefslogtreecommitdiff
path: root/spec/lib/gitlab/profiler_spec.rb
Commit message (Collapse)AuthorAgeFilesLines
* Allow profiler to authenticate by stubbing users directly54327-profiler-doesn-t-work-with-auth-nowSean McGivern2018-11-261-17/+25
| | | | | | | | | | | | | Previously, we used a personal access token. This had a couple of problems: 1. If the user didn't have a PAT, we couldn't impersonate them. 2. It depended on reading the raw PAT from the database. Instead, we can monkey-patch the authentication methods on ApplicationController (overriding the Devise ones), and remove them once we're done. This does mean that profiles will not profile auth correctly, so for that, use a PAT directly.
* Expose a clean_backtrace method from Gitlab::Profilerexpose-clean-backtrace-method-from-profilerSean McGivern2018-06-151-0/+45
| | | | | This method makes it easier for other parts of the app to get clean backtraces, as well as console users.
* Add query counts by model to profiler outputadd-query-counts-to-profiler-outputSean McGivern2018-03-211-2/+22
|
* Include the ee/ directory in backtracesallow-ee-in-backtracesSean McGivern2018-03-121-1/+3
|
* Improve error handling for Gitlab::Profiler and improve doc about providing ↵update-profiler-docs-explaining-how-to-provide-userDylan Griffith2018-02-161-0/+9
| | | | a user
* Add Gitlab::Profiler for profiling from a console or runnerSean McGivern2018-01-191-0/+156
Gitlab::Profiler.profile takes a URL to profile, and returns the ruby-prof profile result. This is currently only for interactive use (in a console) or from the script runner. Note that when using this interactively, changes to the application within that console session will be used, so this can be used to test proposed performance changes.