In this issue, the goal is to analyze the database workload on GitLab.com and draw first conclusions from it. The idea is to uncover areas of interest, e.g. by identifying particularly worse queries and describing a methodology to find those in the first place. 1. Identify 2 queries and their feature category that have a high impact on the primary database instance 1. Explain how we define "high impact" in each of those cases 1. Document how we reached that conclusion 1. Create issues for each area and describe what causes the high database impact in this area (problem description) As a deliverable, the results can go into a page on the handbook as a summary: https://about.gitlab.com/handbook/engineering/development/enablement/database/#documentation