diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-20 17:34:42 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-05-20 17:34:42 +0300 |
| commit | 9f46488805e86b1bc341ea1620b866016c2ce5ed (patch) | |
| tree | f9748c7e287041e37d6da49e0a29c9511dc34768 /doc/development/performance.md | |
| parent | dfc92d081ea0332d69c8aca2f0e745cb48ae5e6d (diff) | |
Add latest changes from gitlab-org/gitlab@13-0-stable-ee
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 5068103ff16..2e73161a11f 100644 --- a/doc/development/performance.md +++ b/doc/development/performance.md @@ -46,7 +46,7 @@ GitLab provides built-in tools to help improve performance and availability: GitLab team members can use [GitLab.com's performance monitoring systems](https://about.gitlab.com/handbook/engineering/monitoring/) located at <https://dashboards.gitlab.net>, this requires you to log in using your `@gitlab.com` email address. Non-GitLab team-members are advised to set up their -own InfluxDB and Grafana stack. +own Prometheus and Grafana stack. ## Benchmarks @@ -109,7 +109,7 @@ In short: By collecting snapshots of process state at regular intervals, profiling allows you to see where time is spent in a process. The [StackProf](https://github.com/tmm1/stackprof) gem is included in GitLab's development environment, allowing you to investigate -the behaviour of suspect code in detail. +the behavior of suspect code in detail. It's important to note that profiling an application *alters its performance*, and will generally be done *in an unrepresentative environment*. In particular, |