gitlab-org--gitlab-foss/doc/administration/application_settings_cache.md

stage	group	info
Data Stores	Memory	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:

   gitlab_rails['application_settings_cache_seconds'] = 60
   

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

   gitlab-ctl reconfigure
   gitlab-ctl restart
   

---

For installations from source

1. Edit config/gitlab.yml:

   gitlab:
     application_settings_cache_seconds: 60
   

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