Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
7f6faabe
Commit
7f6faabe
authored
Feb 05, 2021
by
Craig Gomes
Committed by
Yannis Roussos
Feb 05, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Adding Query Performance Investigation Template
parent
1e36cde0
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
39 additions
and
0 deletions
+39
-0
.gitlab/issue_templates/Query Performance Investigation.md
.gitlab/issue_templates/Query Performance Investigation.md
+39
-0
No files found.
.gitlab/issue_templates/Query Performance Investigation.md
0 → 100644
View file @
7f6faabe
## Description
As the name implies, the purpose of the template is to detail underperforming queries for futher investigation.
### Steps
-
[ ] Rename the issue to -
`Query Performance Investigation - [Query Snippet | Table info]`
-
For example -
`Query Performance Investigation - SELECT "namespaces".* FROM "namespaces" WHERE "namespaces"."id" = $1 LIMIT $2`
-
[ ] Provide information in the Requested Data Points table
-
[
] Provide [priority and severity labels
](
https://about.gitlab.com/handbook/engineering/quality/issue-triage/#availability
)
-
[ ] If this requires immediate attention cc
`@gitlab-org/database-team`
and reach out in the #g_database slack channel
### Requested Data points
Please provide as many of these fields as possible when submitting a query performance report.
-
TPS
-
Duration
-
Source of calls (Sidekiq, WebAPI, etc)
-
Query ID
-
SQL Statement
-
Query Plan
-
Query Example
-
Total number of calls (relative)
-
% of Total time
<!--
-
Example of a postgres checkup report - https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/snippets/2056787
-
Epic - Improving the Database resource usage (&365) - https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/365#short-term-query-improvements
-
Past examples of query performance investigations that have led to this template creation.
-
Possible Index suggestion or query rewriting (#292454) - https://gitlab.com/gitlab-org/gitlab/-/issues/292454)
-
High number of Sessions to the database with the value SET parameter (#292022) - https://gitlab.com/gitlab-org/gitlab/-/issues/292022)
-
Query performance "Select 1" (#220055) - https://gitlab.com/gitlab-org/gitlab/-/issues/220055
-
Select statements that are in execution during database CPU utilization peak times - licenses table (#292900) - https://gitlab.com/gitlab-org/gitlab/-/issues/292900
-->
/label ~"group::database" ~"database::triage"
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment