summaryrefslogtreecommitdiff
path: root/doc/development/query_recorder.md
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2020-11-04 00:09:12 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2020-11-04 00:09:12 +0000
commit8d94fb4ae136386963c5353f72b227b9c27af4d7 (patch)
tree96ac46df8328893611554fca5533e520c78fe27a /doc/development/query_recorder.md
parent037bda35bf0edc43a591348d4fda01f436389c60 (diff)
downloadgitlab-ce-8d94fb4ae136386963c5353f72b227b9c27af4d7.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/query_recorder.md')
-rw-r--r--doc/development/query_recorder.md1
1 files changed, 0 insertions, 1 deletions
diff --git a/doc/development/query_recorder.md b/doc/development/query_recorder.md
index ae5c2947d40..fb87e5137e5 100644
--- a/doc/development/query_recorder.md
+++ b/doc/development/query_recorder.md
@@ -26,7 +26,6 @@ end
As an example you might create 5 issues in between counts, which would cause the query count to increase by 5 if an N+1 problem exists.
-NOTE: **Note:**
In some cases the query count might change slightly between runs for unrelated reasons. In this case you might need to test `exceed_query_limit(control_count + acceptable_change)`, but this should be avoided if possible.
## Cached queries