GitLab Performance - Kylie Norquist
module-name: "GitLab Performance"
area: "Troubleshooting & Diagnostics"
maintainers:
- wchandler
Overview
Goal:
Objectives: At the end of this module, you should be able to:
Tackle stage 1 first and the last stage last, but the others can be completed in any order you prefer.
Stage 0: Commit to learning about GitLab Performance
-
Done with Stage 0
-
Create an issue using this template by making the Issue Title: -
Add yourself and your trainer as the assignees. -
Notify your manager to let them know you've started. -
Commit to this by notifying the current experts that they can start routing non-technical GitLab Performance questions to you. -
Optional: Set a milestone, if applicable, and a due date to help motivate yourself!
Stage 1: GitLab's Architecture & Internals
-
Done with Stage 1
This stage is aimed for you to have a good grasp of GitLab internals.
-
Review GitLab's Architecture, Components, Request Type & System Layout -
GitLab's Architecture Overview -
GitLab.com's Production Architecture overview -
GitLab.com's cloud native high level architecture
-
Stage 2: GitLab's HA Installation methods
-
Done with Stage 2
This stage is aimed at you having a high level understanding of the different High-Availability Installation methods.
Stage 3: GitLab/Linux Performance Analysis & Troubleshooting
-
Done with Stage 3
This stage lists resources to tools/performance topics that are usually experienced by GitLab's customers
-
Familiarity GitLab Support Toolbox -
GitLab Tools -
Git Performance: -
PostgreSQL Performance -
AWS Rate Limits -
Linux System Performance Tracing/Analysis
Stage 4: Tickets
-
Find 10 Solved tickets to get a sense of what gets asked and how others have done troubleshooting in this area. -
__ -
__ -
__ -
__ -
__ -
__ -
__ -
__ -
__ -
__
-
-
Answer 5 tickets on this module's topic and paste the links here. Do this even if a ticket seems too advanced for you to answer. Find the answers from an expert and relay them to the customers. -
__ -
__ -
__ -
__ -
__
-
Stage 5: Pair on customer calls
-
Pair on or perform five diagnostic calls, where a customer is having trouble with GitLab Performance. -
call with ___ -
call with ___ -
call with ___ -
call with ___ -
call with ___
-
Penultimate stage: Review
Any updates or improvements needed? If there are any dead links, out of date or inaccurate content, missing content whether in this module or in other documentation, list it below as tasks for yourself! Once ready, have a maintainer or manager review.
-
Update ...
Final stage: Completion
-
Have your trainer review your tickets and assessment. If you do not have a trainer, ask an expert to review. -
Manager: schedule a call (or integrate into 1:1) to review how the module went. -
Submit a MR to update modules
andknowledge_areas
in the Support Team yaml file with this training module's topic. You will now be listed as GitLab Performance Expert on Skills by Person page.
Edited by Kylie Norquist