blob: b6c09129c79525dbb492bdb917126da61f6b7a94 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
---
stage: Enablement
group: Memory
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
---
# Changing application settings cache expiry interval **(FREE SELF)**
Application settings are cached for 60 seconds by default which should work
for most installations. A higher value would mean a greater delay between
changing an application setting and noticing that change come into effect.
A value of `0` would result in the `application_settings` table being
loaded for every request causing extra load on Redis and/or PostgreSQL.
It is therefore recommended to keep the value above zero.
## Change the application settings cache expiry
To change the expiry value:
**For Omnibus installations**
1. Edit `/etc/gitlab/gitlab.rb`:
```ruby
gitlab_rails['application_settings_cache_seconds'] = 60
```
1. Save the file, and reconfigure and restart GitLab for the changes to take effect:
```shell
gitlab-ctl reconfigure
gitlab-ctl restart
```
---
**For installations from source**
1. Edit `config/gitlab.yml`:
```yaml
gitlab:
application_settings_cache_seconds: 60
```
1. Save the file and [restart](restart_gitlab.md#installations-from-source)
GitLab for the changes to take effect.
|
