diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-07-07 00:08:51 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-07-07 00:08:51 +0300 |
| commit | 27b73daa23f7b41c65f7d417283753b93cbaa7b4 (patch) | |
| tree | 7873a861f4c91df6560433e89a267fb60ade2d84 /doc/development/performance.md | |
| parent | 691ed55a053853e58f36635524d2615ac60e445e (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/performance.md')
| -rw-r--r-- | doc/development/performance.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/development/performance.md b/doc/development/performance.md index 69ad524675d..26e107eb2a1 100644 --- a/doc/development/performance.md +++ b/doc/development/performance.md @@ -254,6 +254,13 @@ These results can also be placed into a PostgreSQL database by setting the `RSPEC_PROFILING_POSTGRES_URL` variable. This is used to profile the test suite when running in the CI environment. +We store these results also when running CI jobs on the default branch on +`gitlab.com`. Statistics of these profiling data are [available +online](https://gitlab-org.gitlab.io/rspec_profiling_stats/). For example, +you can find which tests take longest to run or which execute the most +queries. This can be handy for optimizing our tests or identifying performance +issues in our code. + ## Memory profiling One of the reasons of the increased memory footprint could be Ruby memory fragmentation. |