Application cache interval

Tier: Free, Premium, Ultimate
Offering: GitLab Self-Managed

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.

Change the expiration interval for application cache

To change the expiry value:

Edit /etc/gitlab/gitlab.rb:

gitlab_rails['application_settings_cache_seconds'] = 60

Save the file, and then reconfigure and restart GitLab for the changes to take effect:
```
gitlab-ctl reconfigure
gitlab-ctl restart
```

Edit config/gitlab.yml:

gitlab:
  application_settings_cache_seconds: 60

Save the file, and then restart GitLab for the changes to take effect.

Docs

Edit this page to fix an error or add an improvement in a merge request.

Create an issue to suggest an improvement to this page.

Product

Create an issue if there's something you don't like about this feature.

Propose functionality by submitting a feature request.

Feature availability and product trials

View pricing to see all GitLab tiers and features, or to upgrade.

Try GitLab for free with access to all features for 30 days.

Get help

If you didn't find what you were looking for, search the docs.

If you want help with something specific and could use community support, post on the GitLab forum.

For problems setting up or using this feature (depending on your GitLab subscription).

Request support