From 6364c14cc1f445d471bca118dca5af5a85b2c5dc Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Wed, 16 Dec 2020 15:10:18 +0000 Subject: Add latest changes from gitlab-org/gitlab@master --- doc/development/cached_queries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/development/cached_queries.md') 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. -- cgit v1.2.1