diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-11-17 00:09:02 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-11-17 00:09:02 +0300 |
| commit | b9033ad4157010ccd8f37437de131ed70af90f45 (patch) | |
| tree | 7d10ebd824040aabc585273e07dec6ebde64730f /doc/development/query_recorder.md | |
| parent | 6d9c4dc2ef4c63bee8e9ca095dc2f0ed683a34f5 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/query_recorder.md')
| -rw-r--r-- | doc/development/query_recorder.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/query_recorder.md b/doc/development/query_recorder.md index d8951c64071..4a02af3348c 100644 --- a/doc/development/query_recorder.md +++ b/doc/development/query_recorder.md @@ -31,8 +31,8 @@ In some cases the query count might change slightly between runs for unrelated r ## Cached queries By default, QueryRecorder will ignore [cached queries](merge_request_performance_guidelines.md#cached-queries) in the count. However, it may be better to count -all queries to avoid introducing an N+1 query that may be masked by the statement cache. -To do this, this requires the `:use_sql_query_cache` flag to be set. +all queries to avoid introducing an N+1 query that may be masked by the statement cache. +To do this, this requires the `:use_sql_query_cache` flag to be set. You should pass the `skip_cached` variable to `QueryRecorder` and use the `exceed_all_query_limit` matcher: ```ruby |