diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2022-12-05 06:08:47 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2022-12-05 06:08:47 +0300 |
| commit | f0208efd0b9afee8a00690d430e9aec2171a1955 (patch) | |
| tree | 9bf10cd37233e54bcdf84dbb76d5a52aaedd56cf /doc/development/caching.md | |
| parent | f50a7f8d970c50026e52c0b5d1c444b365d3b795 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/caching.md')
| -rw-r--r-- | doc/development/caching.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/caching.md b/doc/development/caching.md index 4c91e8eba6e..58ec7a77591 100644 --- a/doc/development/caching.md +++ b/doc/development/caching.md @@ -80,7 +80,7 @@ indicates we have plenty of headroom. - Generic data can be cached for everyone. - You must keep this in mind when building new features. 1. Try to preserve cache data as much as possible: - - Use nested caches to maintain as much cached data as possible across expiries. + - Use nested caches to maintain as much cached data as possible across expires. 1. Perform as few requests to the cache as possible: - This reduces variable latency caused by network issues. - Lower overhead for each read on the cache. |