2021-01-29 00:20:46 +05:30
---
2021-02-22 17:27:13 +05:30
stage: Enablement
group: Distribution
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
2021-01-29 00:20:46 +05:30
---
2017-08-17 22:00:37 +05:30
# Polling configuration
The GitLab UI polls for updates for different resources (issue notes, issue
titles, pipeline statuses, etc.) on a schedule appropriate to the resource.
2021-02-22 17:27:13 +05:30
In ** [Admin Area ](../user/admin_area/index.md ) > Settings > Preferences > Real-time features**,
you can configure "Polling
2017-08-17 22:00:37 +05:30
interval multiplier". This multiplier is applied to all resources at once,
and decimal values are supported. For the sake of the examples below, we will
say that issue notes poll every 2 seconds, and issue titles poll every 5
seconds; these are _not_ the actual values.
- 1 is the default, and recommended for most installations. (Issue notes poll
2019-07-07 11:18:12 +05:30
every 2 seconds, and issue titles poll every 5 seconds.)
2017-08-17 22:00:37 +05:30
- 0 will disable UI polling completely. (On the next poll, clients will stop
2019-07-07 11:18:12 +05:30
polling for updates.)
2017-08-17 22:00:37 +05:30
- A value greater than 1 will slow polling down. If you see issues with
2019-07-07 11:18:12 +05:30
database load from lots of clients polling for updates, increasing the
multiplier from 1 can be a good compromise, rather than disabling polling
completely. (For example: If this is set to 2, then issue notes poll every 4
seconds, and issue titles poll every 10 seconds.)
2017-08-17 22:00:37 +05:30
- A value between 0 and 1 will make the UI poll more frequently (so updates
2019-07-07 11:18:12 +05:30
will show in other sessions faster), but is **not recommended** . 1 should be
fast enough. (For example, if this is set to 0.5, then issue notes poll every
1 second, and issue titles poll every 2.5 seconds.)
