diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-12-17 03:09:53 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-12-17 03:09:53 +0300 |
| commit | 2e3423047a0df21153b06fee43743a1fa90e658e (patch) | |
| tree | 31e4c10cc93dbed67876fb64fcc6b50f98e073a8 /doc/development/performance.md | |
| parent | c47247f7cd8272d2cdc9f472d00a2542724ee95e (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/performance.md')
| -rw-r--r-- | doc/development/performance.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/performance.md b/doc/development/performance.md index e3b0415918a..f3ce924de38 100644 --- a/doc/development/performance.md +++ b/doc/development/performance.md @@ -305,7 +305,7 @@ bundle exec stackprof --stackcollapse /tmp/stackprof.55769.c6c3906452.profile | ## RSpec profiling -GitLab's development environment also includes the +The GitLab development environment also includes the [rspec_profiling](https://github.com/foraker/rspec_profiling) gem, which is used to collect data on spec execution times. This is useful for analyzing the performance of the test suite itself, or seeing how the performance of a spec @@ -358,7 +358,7 @@ We can use two approaches, often in combination, to track down memory issues: We can use `memory_profiler` for profiling. -The [`memory_profiler`](https://github.com/SamSaffron/memory_profiler) gem is already present in GitLab's `Gemfile`, +The [`memory_profiler`](https://github.com/SamSaffron/memory_profiler) gem is already present in the GitLab `Gemfile`, you just need to require it: ```ruby |