- Successor to "GitLab.com Latency" #947 and "Back calculate gains needed" #1830. - Action items are also to be listed on https://about.gitlab.com/handbook/engineering/performance ### Analysis to be done - Analyze transaction time and correlation with rails controller time #1877 - Analyze reasons for performance difference on two issues, as case study #1880 ### Monitoring to be added - included on handbook/engineering/performance - Gather monitoring data for longer time periods #1879 - Enable Prometheus collection of InfluxDB metrics #1022 - Allow more GitLab internals monitoring https://gitlab.com/gitlab-org/gitlab-ce/issues/28465 - Making workhorse timings available https://gitlab.com/gitlab-com/infrastructure/issues/2025 ### Tracking ongoing efforts - all listed on the engineering handbook page. - [meta] Overview of top 10 slowest queries https://gitlab.com/gitlab-org/gitlab-ce/issues/34535 - [meta] Scoping work on completing the transition to Gitaly https://gitlab.com/gitlab-org/gitaly/issues/313 - [meta] Frontend Performance Audit https://gitlab.com/gitlab-org/gitlab-ce/issues/33958 - Setting up CDN for GitLab.com #2092 (successor to #57 ) - Compressing html with gzip in nginx https://gitlab.com/gitlab-org/gitlab-ce/issues/33719 - Slow SSL Connection Establishment #2321 \cc @gl-infra @sitschner @stanhu @sytses @bjk-gitlab