summaryrefslogtreecommitdiff
path: root/doc/development/cached_queries.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-12-16 15:10:18 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-12-16 15:10:18 +0000
commit6364c14cc1f445d471bca118dca5af5a85b2c5dc (patch)
tree2579c5592f207e86ff7a0c5c7499caad723cdec1 /doc/development/cached_queries.md
parent5a2284f3500088e04cf3a5854fb06dc9db2b6077 (diff)
downloadgitlab-ce-6364c14cc1f445d471bca118dca5af5a85b2c5dc.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/cached_queries.md')
-rw-r--r--doc/development/cached_queries.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/cached_queries.md b/doc/development/cached_queries.md
index 01c8e63edca..4f82d721164 100644
--- a/doc/development/cached_queries.md
+++ b/doc/development/cached_queries.md
@@ -29,7 +29,7 @@ more expensive from a memory perspective. They could mask
so you should treat them the same way you treat regular N+1 queries.
In cases of N+1 queries masked by cached queries, the same query is executed N times.
-It will not hit the database N times but instead returns the cached results N times.
+It doesn't hit the database N times but instead returns the cached results N times.
This is still expensive because you need to re-initialize objects each time at a
greater expense to the CPU and memory resources. Instead, you should use the same
in-memory objects whenever possible.