Application cache interval

DETAILS: Tier: Free, Premium, Ultimate Offering: 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:

::Tabs

:::TabTitle Linux package (Omnibus)

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

:::TabTitle Self-compiled (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.

::EndTabs