blob: b3aac932fa8309d1e816b8dc9a28dc240351dc9c (
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
---
# Change the expiration interval for application cache **(FREE SELF)**
By default, GitLab caches application settings for 60 seconds. Occasionally,
you may need to increase that interval to have more delay between application
setting changes and when users notice those changes in the application.
We recommend you set this value to greater than `0` seconds. Setting it to `0`
causes the `application_settings` table to load for every request. This causes
extra load for Redis and PostgreSQL.
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 then 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 then [restart](restart_gitlab.md#installations-from-source)
GitLab for the changes to take effect.
|
