# Polling configurationThe GitLab UI polls for updates for different resources (issue notes, issuetitles, pipeline statuses, etc.) on a schedule appropriate to the resource.In "Application settings -> Real-time features" you can configure "Pollinginterval multiplier". This multiplier is applied to all resources at once,and decimal values are supported. For the sake of the examples below, we willsay that issue notes poll every 2 seconds, and issue titles poll every 5seconds; these are _not_ the actual values.- 1 is the default, and recommended for most installations. (Issue notes pollevery 2 seconds, and issue titles poll every 5 seconds.)- 0 will disable UI polling completely. (On the next poll, clients will stoppolling for updates.)- A value greater than 1 will slow polling down. If you see issues withdatabase load from lots of clients polling for updates, increasing themultiplier from 1 can be a good compromise, rather than disabling pollingcompletely. (For example: If this is set to 2, then issue notes poll every 4seconds, and issue titles poll every 10 seconds.)- A value between 0 and 1 will make the UI poll more frequently (so updateswill show in other sessions faster), but is **not recommended**. 1 should befast enough. (For example, if this is set to 0.5, then issue notes poll every1 second, and issue titles poll every 2.5 seconds.)