2017-09-10 17:25:29 +05:30
|
|
|
# Performance Bar
|
|
|
|
|
|
|
|
A Performance Bar can be displayed, to dig into the performance of a page. When
|
|
|
|
activated, it looks as follows:
|
|
|
|
|
|
|
|
![Performance Bar](img/performance_bar.png)
|
|
|
|
|
2018-03-17 18:26:18 +05:30
|
|
|
It allows you to see (from left to right):
|
2017-09-10 17:25:29 +05:30
|
|
|
|
2018-03-17 18:26:18 +05:30
|
|
|
- the current host serving the page
|
2019-12-26 22:10:19 +05:30
|
|
|
- time taken and number of DB queries; click through for details of these queries
|
2019-07-07 11:18:12 +05:30
|
|
|
![SQL profiling using the Performance Bar](img/performance_bar_sql_queries.png)
|
2019-12-26 22:10:19 +05:30
|
|
|
- time taken and number of [Gitaly] calls; click through for details of these calls
|
2019-07-07 11:18:12 +05:30
|
|
|
![Gitaly profiling using the Performance Bar](img/performance_bar_gitaly_calls.png)
|
2019-12-26 22:10:19 +05:30
|
|
|
- time taken and number of [Rugged] calls; click through for details of these calls
|
2019-10-12 21:52:04 +05:30
|
|
|
![Rugged profiling using the Performance Bar](img/performance_bar_rugged_calls.png)
|
2019-12-26 22:10:19 +05:30
|
|
|
- time taken and number of Redis calls; click through for details of these calls
|
2019-10-12 21:52:04 +05:30
|
|
|
![Redis profiling using the Performance Bar](img/performance_bar_redis_calls.png)
|
2019-12-26 22:10:19 +05:30
|
|
|
- a link to add a request's details to the performance bar; the request can be
|
|
|
|
added by its full URL (authenticated as the current user), or by the value of
|
|
|
|
its `X-Request-Id` header
|
2017-09-10 17:25:29 +05:30
|
|
|
|
2018-05-09 12:01:36 +05:30
|
|
|
On the far right is a request selector that allows you to view the same metrics
|
|
|
|
(excluding the page timing and line profiler) for any requests made while the
|
|
|
|
page was open. Only the first two requests per unique URL are captured.
|
|
|
|
|
2019-12-21 20:55:43 +05:30
|
|
|
## Request warnings
|
|
|
|
|
|
|
|
For requests exceeding pre-defined limits, a warning icon will be shown
|
|
|
|
next to the failing metric, along with an explanation. In this example,
|
|
|
|
the Gitaly call duration exceeded the threshold:
|
|
|
|
|
|
|
|
![Gitaly call duration exceeded threshold](img/performance_bar_gitaly_threshold.png)
|
|
|
|
|
|
|
|
If any requests on the current page generated warnings, the icon will
|
|
|
|
appear next to the request selector:
|
|
|
|
|
|
|
|
![Request selector showing two requests with warnings](img/performance_bar_request_selector_warning.png)
|
|
|
|
|
|
|
|
And requests with warnings are indicated in the request selector with a
|
|
|
|
`(!)` after their path:
|
|
|
|
|
|
|
|
![Request selector showing dropdown](img/performance_bar_request_selector_warning_expanded.png)
|
|
|
|
|
2017-09-10 17:25:29 +05:30
|
|
|
## Enable the Performance Bar via the Admin panel
|
|
|
|
|
|
|
|
GitLab Performance Bar is disabled by default. To enable it for a given group,
|
2019-02-15 15:39:39 +05:30
|
|
|
navigate to the Admin area in **Settings > Metrics and Profiling > Profiling - Performance bar**
|
|
|
|
(`admin/application_settings/metrics_and_profiling`).
|
2017-09-10 17:25:29 +05:30
|
|
|
|
|
|
|
The only required setting you need to set is the full path of the group that
|
|
|
|
will be allowed to display the Performance Bar.
|
|
|
|
Make sure _Enable the Performance Bar_ is checked and hit
|
|
|
|
**Save** to save the changes.
|
|
|
|
|
2018-03-17 18:26:18 +05:30
|
|
|
Once the Performance Bar is enabled, you will need to press the [<kbd>p</kbd> +
|
2019-12-26 22:10:19 +05:30
|
|
|
<kbd>b</kbd> keyboard shortcut](../../../user/shortcuts.md) to actually
|
2018-03-17 18:26:18 +05:30
|
|
|
display it.
|
|
|
|
|
|
|
|
You can toggle the Bar using the same shortcut.
|
|
|
|
|
2017-09-10 17:25:29 +05:30
|
|
|
![GitLab Performance Bar Admin Settings](img/performance_bar_configuration_settings.png)
|
|
|
|
|
2018-05-09 12:01:36 +05:30
|
|
|
[Gitaly]: ../../gitaly/index.md
|
2019-10-12 21:52:04 +05:30
|
|
|
[Rugged]: ../../high_availability/nfs.md#improving-nfs-performance-with-gitlab
|