diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-21 09:08:25 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-21 09:08:25 +0300 |
| commit | 8f306a7dc503ae0fed4acebc528f2bc2030dad83 (patch) | |
| tree | 80e62141eab6ff86ea7a184565afb32a650217d9 /doc/development/performance.md | |
| parent | 76937b2add54d9ecfd1310847e244ac833d90e3b (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/performance.md')
| -rw-r--r-- | doc/development/performance.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/performance.md b/doc/development/performance.md index 2e73161a11f..050444c57af 100644 --- a/doc/development/performance.md +++ b/doc/development/performance.md @@ -8,7 +8,7 @@ consistent performance of GitLab. The process of solving performance problems is roughly as follows: 1. Make sure there's an issue open somewhere (for example, on the GitLab CE issue - tracker), and create one if there is not. See [#15607](https://gitlab.com/gitlab-org/gitlab-foss/issues/15607) for an example. + tracker), and create one if there is not. See [#15607](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/15607) for an example. 1. Measure the performance of the code in a production environment such as GitLab.com (see the [Tooling](#tooling) section below). Performance should be measured over a period of _at least_ 24 hours. |