This epic is the SSOT for ongoing and planned Performance Enablement Team work. Please find below the work that is currently in-progress. ## Project Work ### :hourglass: Work In Progress These epics are currently in progress | **Topic** | **Start Date** | **Target End Date** | **Summary** | |-----------|----------------|---------------------|-------------| | [Performance Enablement: Business as usual](https://gitlab.com/groups/gitlab-org/quality/-/epics/99) <br/> @mkomor1 (+5 participants) <br/> ~"group::performance enablement" | 2025-01-11 | | **2025-10-29**: <br>no updates<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/99#note_2851687822_<br><!-- STATUS NOTE END --><br> | | [Load test agentic chat and SW development flows](https://gitlab.com/groups/gitlab-org/quality/-/epics/201) <br/> @bwilkerson13 (+1 participants) <br/> ~"group::performance enablement" | 2025-07-14 | 2025-10-31 | **2025-11-05**: <br>[The AIGW team has identified some differences in the metrics between AIGW running with real LLM calls vs. mocked.](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/3794#note_2868027847) This could have an impact on the realism of the performance test findings, so they are adjusting the mocks for more accurate modeling.<br><br>Work by PE on the log aggregation for troubleshooting continues.<br><br>:arrow_forward: **Next**:<br><br>* Modify the mocked load tests to include real tool calls<br>* Modify the mocked load tests to update the conversation history in a way that's consistent with real LLM calls<br>* Investigate and try to reproduce high memory usage (\> 50%)<br>* https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/2037+<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/201#note_2867822922_<br><!-- STATUS NOTE END --><br> | | [Make CPT report stable and accurate by adding environment metrics and fixing known issues](https://gitlab.com/groups/gitlab-org/quality/-/epics/251) <br/> @vishal.s.patel (+0 participants) <br/> ~"group::performance enablement" | 2025-10-13 | 2025-10-31 | **2025-10-22**: <br>:tada: **achievements**:<br><br>* Submitted few MRs for fixing a bug where CPT didn't run for MRs from fork. This is usually helpful for any dependency updates that the renovate bot makes as they may impact performance. These MRs have been merged making the CPT runs more stable and encountering less failures.<br><br><br>* https://gitlab.com/gitlab-org/gitlab/-/merge_requests/209043<br>* https://gitlab.com/gitlab-org/quality/component-performance-testing/-/merge_requests/98<br><br>:issue-blocked: **blockers**:<br><br>- None<br><br>:arrow_forward: **next**:<br><br>- Working on [**Retry duo before posting comment to make sure the report is complete and has various rules applied**](https://gitlab.com/gitlab-org/quality/component-performance-testing/-/issues/113)<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/251#note_2836139330_<br><!-- STATUS NOTE END --><br> | | [Establish Performance Issue Data Pipeline at GitLab](https://gitlab.com/groups/gitlab-org/quality/-/epics/228) <br/> @bwilkerson13 (+13 participants) <br/> ~"group::performance enablement" | | 2025-10-29 | **2025-11-05**: <br>Epic still ready to close.<br><br>This time with [the correct format hopefully](https://handbook.gitlab.com/handbook/engineering/infrastructure/platforms/project-management/#when-a-project-is-finished) :sweat_smile:<br><br>**The Original Problem**<br><br>The Performance Enablement team lacked a data-driven understanding of performance issues at GitLab.<br><br>This left us with no way to systematically identify and prioritize work that addresses GitLab's most urgent performance issues, and we were unable to speak with any confidence about those issues either.<br><br>**Changes/Findings**<br><br>We investigated Incident.io data back to 2025-08-01 for GitLab.com to understand recent trends.<br><br>We identified that, over the last 2.5 months, outages of Gitaly (2094 minutes, or ~35 hours), and Rails (1195 minutes, ~20 hours) contributed the most Work Minutes spent by Team Members on performance incidents. ([Deeper analysis for the reasoning on using this metric is available.](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/3954#results))<br><br>We also identified that Application Bugs/Unintentional Performance Side-Effect (3149 minutes, ~52 hours) are the most impactful performance incident trigger. This isn't new information, but being able to identify and track it with data is a significant maturation of our team's process.<br><br>We established dashboards to continue monitoring this metric and other supporting incident data, and established a monthly review process to evaluate this data going forward.<br><br>**Impact**<br><br>- Performance Enablement will be able to quantify success of future projects by referencing trends in Work Minutes spent on Performance Incidents.<br><br>- We have also established [a monthly process for reviewing the data](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/3970#note_2854186848), to ensure we remain focused on addressing the latest issues that are causing our Team Members and customers the most performance-related pain.<br><br>- This data is being used to guide the Q4 road map for Performance Enablement to focus on providing more sophisticated tools for Gitaly performance testing, earlier in the development cycle. As a result, we are proactively positioned to address recent asks for testing around Gitaly RAFT, and around new Reference Architecture changes.<br><br>**Links**<br><br>- [Initial Manual Analysis Results](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/3954#results)<br>- [Link to .com Dashboard](https://app.incident.io/gitlab/insights/dashboards/custom/01K80Z97QT80ZY6NPPZ391QQQX)<br>- [Link to Dedicated Dashboard](https://app.incident.io/gitlab/insights/dashboards/custom/01K814SW8X1DZJVB6Z48DFE8JA)<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/228#note_2867822976_<br><!-- STATUS NOTE END --><br> | ### :arrow_forward: Next These are the epics we will be focusing on next | **Topic** | **Target Start Date** | **Summary** | |-----------|-----------------------|-------------| | [Measure how much impact the performance results on MRs is having](https://gitlab.com/groups/gitlab-org/quality/-/epics/237) <br/> @vishal.s.patel (+0 participants) <br/> ~"group::performance enablement" | | | | [Enable engineers to self-serve CPT through better documentation](https://gitlab.com/groups/gitlab-org/quality/-/epics/236) <br/> (+0 participants) <br/> ~"group::performance enablement" | | | ### :stop_button: Triage Epics that are currently being triaged | **Topic** | **Summary** | |-----------|-------------| | [GitLab Performance Tool v3.0.0](https://gitlab.com/groups/gitlab-org/-/epics/4300) <br/> ~"group::performance enablement" | | | [Roadmap: Shift-Left and Shift-Right Performance Testing Excellence](https://gitlab.com/groups/gitlab-org/quality/-/epics/111) <br/> ~"group::performance enablement" | | | [Enable GitLab Browser Performance Tool to be used in MRs](https://gitlab.com/groups/gitlab-org/quality/-/epics/146) <br/> ~"group::performance enablement" | **2025-05-21**: <br>Started to work on the requirement gathering and splitting into issues. Making a demo on the tool usage, so teams can start exploring this before enabling this in the MRs<br><br>:tada: **achievements**:<br>- Migrating the blueprint from issue to Handbook - https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/13221<br><br>:issue-blocked: **blockers**:<br>- None<br><br>:arrow_forward: **next**:<br>- Create the demo and share it as part of the Guide.<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/146#note_2518397943_<br><!-- STATUS NOTE END --><br> | | [Track historical performance test results data to enable trend analysis over time](https://gitlab.com/groups/gitlab-org/quality/quality-engineering/-/epics/124) <br/> ~"group::performance enablement" | **2025-04-30**: <br>:tada: **achievements**:<br><br>- making progress on defining the [changes needed in GPT](https://gitlab.com/gitlab-org/quality/performance/-/issues/642) to support pushing results to the dashboard<br><br> | | [Improvements to Gitlab Browser Performance Tool GBPT (using Sitespeed)](https://gitlab.com/groups/gitlab-org/quality/-/epics/175) <br/> ~"group::performance enablement" | | | [Investigations into interesting performance or load events](https://gitlab.com/groups/gitlab-org/quality/-/epics/204) <br/> | | | [Reduce performance testing bottlenecks by creating a centralized knowledge base in the handbook, phase 2](https://gitlab.com/groups/gitlab-org/quality/-/epics/188) <br/> ~"group::performance enablement" | | | [Establish a default test settings/profile in GPT for GDK](https://gitlab.com/groups/gitlab-org/quality/quality-engineering/-/epics/159) <br/> ~"group::performance enablement" | **2025-07-02**: <br>Hi @john.mcdonnell can you please provide an update here? Thanks!<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/quality-engineering/-/epics/159#note_2597652926_<br><!-- STATUS NOTE END --><br> | | [Make passing GitLab Performance Tool results a pre-commit requirement in GDK](https://gitlab.com/groups/gitlab-org/quality/quality-engineering/-/epics/150) <br/> ~"group::performance enablement" | **2025-06-25**: <br>This item will be going to the backlog per the team decision in https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/3738+.<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/quality-engineering/-/epics/150#note_2582756537_<br><!-- STATUS NOTE END --><br> | | [Reference Architecture test results for Feature Performance into Quality Insights Dashboard](https://gitlab.com/groups/gitlab-org/quality/quality-engineering/-/epics/143) <br/> ~"group::performance enablement" | | | [Introduce Observability Based Performance Testing](https://gitlab.com/groups/gitlab-org/quality/-/epics/112) <br/> ~"group::performance enablement" | **2025-01-22**: <br>Was Pipeline DRI last week, didn't make as much progress as I'ld like<br><br><br>:tada: **achievements**:<br>- Opened an [MR](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/11184) documenting an approach to Observability Based Performance Testing, out for review and editing<br><br><br>:arrow_forward: **next**:<br>- Finish the review and merge the MR<br>- Identify a team to pair with to iterate with<br>- Investigate improvements to the Cells performance dashboard<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/112#note_2308771821_<br><!-- STATUS NOTE END --><br> | ### :white_check_mark: Completed Work Items that have been completed <details> | **Topic** | **Started** | **Ended** | **Summary** | |-----------| ------------| ----------| ------------ | | [Reduce performance testing bottlenecks by creating a centralized knowledge base in the handbook for Feature Performance Testing](https://gitlab.com/groups/gitlab-org/quality/-/epics/135) <br/> ~"group::performance enablement" | 2025-01-01 | 2025-10-15 | **2025-07-09**: <br><br>:tada: **achievements**:<br><br>- Closed out the last issue for the [handbook page](https://handbook.gitlab.com/handbook/engineering/testing/performance-tools/) documenting which tool to use, any remaining open questions will be handled as an iteration in [phase 2](https://gitlab.com/groups/gitlab-org/quality/-/epics/188)<br>- Split finding a home to link the [creating a GPT test with Duo Workflow](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/3644) recording into a separate effort to improve [GPT self-help documentation](https://gitlab.com/gitlab-org/quality/performance/-/issues/651)<br><br>:arrow_forward: **next**:<br><br>- Once we have the remaining issues closed, this epic can be closed.<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/135#note_2612894659_<br><!-- STATUS NOTE END --><br> | | [Setup Gitlab Browser Performance Tool GBPT (using Sitespeed) for Production Monitoring](https://gitlab.com/groups/gitlab-org/quality/quality-engineering/-/epics/134) <br/> ~"group::performance enablement" | 2025-02-01 | 2025-09-19 | **2025-09-10**: <br>_This Epic can be closed_<br><br>To establish continuous performance monitoring in production environments, we needed to revive the https://gitlab.com/gitlab-org/frontend/sitespeed-measurement-setup and setup up the Online version of the Sitespeedio, so that anyone from Gitlab can test web browser performance using this.<br><br>The Sitespeed Online tool is available in https://sitespeed.runway.gitlab.net/ and its only for team members as its protected by Basic auth (Username password in 1password "Sitespeed Runway Production"<br><br>The impact of this is its more available to the teams and the dashboards show performance trends and metrics of various Gitlab pages - https://dashboards.gitlab.net/d/fe-perf-sitespeed-page-metrics/fe-perf3a-sitespeed-page-metrics?from=now-7d&orgId=1&timezone=browser&to=now&var-browser=chrome&var-connectivity=cable&var-function=median&var-group=gitlab_com&var-page=_explore&var-path=desktop&var-testname=gitlab<br><br>A demo walkthrough of the tool is available here - https://youtu.be/Fk7MRn-Ala4<br><br>Self-Service Documentation and Troubleshooting guides<br><br>https://gitlab.com/gitlab-org/quality/sitespeed-runway/-/blob/main/docs/self-service.md<br><br>https://gitlab.com/gitlab-org/quality/sitespeed-runway/-/blob/main/docs/troubleshooting.md<br><br>**Shout-outs:**<br><br>@gsgl Helping me throughout the runway setup and supporting with the infra-mgnt and config-mgnt :thank_you:<br><br>@nduff Guiding me with the dashboard setup :thank_you_spin:<br><br>@AndyWH Polishing the demo @bwilkerson13 Polishing the handbook documentation :thank-you:<br><br>:tada: **achievements**:<br><br>* Completed the [Dashboard setup](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/3820)<br>* Completed Recording Demo: https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/3668<br>* Production-ready guides for team adoption and also handbook updates - https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/15768<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/quality-engineering/-/epics/134#note_2740517830_<br><!-- STATUS NOTE END --><br> | | [Pilot Component level performance testing tool to AI Assist team](https://gitlab.com/groups/gitlab-org/quality/-/epics/165) <br/> ~"group::performance enablement" | 2025-03-15 | 2025-08-11 | **2025-05-07**: <br>Updated the tests running in AI-Gateway to differentiate between warmup period and the actual test period so that the warmup period can be ignored while reporting on the results.<br><br>:tada: **achievements**:<br><br>* MR to differentiate between warmup and load_test period is currently in Maintainer review and should be merged by tomorrow. - https://gitlab.com/gitlab-org/modelops/applied-ml/code-suggestions/ai-assist/-/merge_requests/2434/<br>* Mark Lapierre has been assigned to [write up a performance test by following the document ](https://gitlab.com/gitlab-org/quality/component-performance-testing/-/issues/8)and provide feedback on it and this should happen in 18.1.<br><br>:issue-blocked: **blockers**:<br><br>None<br><br>:arrow_forward: **next**:<br><br>* Work on the feedback provided by Mark and update the documentation.<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/165#note_2488256911_<br><!-- STATUS NOTE END --><br> | | [Introduce Component level performance testing](https://gitlab.com/groups/gitlab-org/quality/-/epics/122) <br/> ~"group::performance enablement" | 2025-03-15 | 2025-04-11 | **2025-04-09**: <br>All the exit criteria of this epic have been met and this epic can be closed. [Conclusion](#conclusion) has been added to the epic's description.<br><br>:tada: **achievements**:<br><br>* Added custom JSON data to report for better parsing in InfluxDB which would make it easier to create dashboards in Grafana - https://gitlab.com/gitlab-org/quality/component-performance-testing/-/issues/4#top<br>* https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/3506+ completed<br>* Did some research on Gitaly to see if its fits the pre-requisite criteria to use CPT(Component Performance Testing in its pipelines) - [Gathered info for onboarding Gitaly as a part of component performance testing](https://gitlab.com/gitlab-org/quality/component-performance-testing/-/issues/6)<br><br>:issue-blocked: **blockers**:<br><br>* None<br><br>:arrow_forward: **next**:<br><br>* Updating existing reports to show variance by comparing runs on MR with runs against successful master.<br>* Connect with Gitaly EMs to understand their performance requirement around Gitaly and discuss discuss about CPT value in Gitaly MRs.<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/122#note_2441217174_<br><!-- STATUS NOTE END --><br> | | [Make Component Performance Testing (CPT) generic for all components](https://gitlab.com/groups/gitlab-org/quality/-/epics/169) <br/> ~"group::performance enablement" | 2025-04-12 | 2025-08-11 | **2025-04-30**: <br>Focused on reporting bits to make it more reliable.<br><br>:tada: **achievements**:<br><br>* Created a Demo on CPT: https://www.youtube.com/watch?v=UtnLyup0y3s<br>* Added standard deviation to the custom report so that this can be sent to Influxdb and a graph can be created in Grafana- https://gitlab.com/gitlab-org/quality/component-performance-testing/-/merge_requests/25<br>* Added service name to the custom report to distinguish the component - https://gitlab.com/gitlab-org/quality/component-performance-testing/-/merge_requests/27<br><br>:issue-blocked: **blockers**:<br><br>* On call DRI last week<br><br>:arrow_forward: **next**:<br><br>* Creating Standard deviation graph in Grafana.<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/169#note_2476951868_<br><!-- STATUS NOTE END --><br> | | [Support Cells SREs to be able to run the E2E suite as part of the Cells pipelines](https://gitlab.com/groups/gitlab-org/quality/quality-engineering/-/epics/133) <br/> ~"group::performance enablement" | 2025-04-17 | 2025-05-23 | **2025-05-21**: <br>:tada: **achievements**:<br><br>- Summarized the [Cells E2E test strategy](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/3585) discussion to hand off to the [test strategy plan](https://gitlab.com/groups/gitlab-org/quality/-/epics/173)<br>- This epic can be closed, the current work is not test related (setting up infrastructure to share secrets between the Cells) and the team will open a RFH once they get to the point of needing our help.<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/quality-engineering/-/epics/133#note_2516340410_<br><!-- STATUS NOTE END --><br> | | [Enable shift-left performance testing in GitLab repo for Merge Request API to highlight regression early on](https://gitlab.com/groups/gitlab-org/quality/-/epics/193) <br/> ~"group::performance enablement" | 2025-07-10 | 2025-08-15 | **2025-08-13**: <br>Reporting for CPT has been enabled in GitLab MRs. This epic can be considered done and can be closed.<br><br>Added conclusion in the description.<br><br>:tada: **achievements**:<br><br>- @john.mcdonnell has enabled the reporting in MRs in GitLab repo following https://gitlab.com/gitlab-org/gitlab/-/merge_requests/198818<br>- @john.mcdonnell submitted more [reporting MRs](https://gitlab.com/gitlab-org/quality/component-performance-testing/-/merge_requests/83) based on feedback from the feedback issue.<br>- Announcement has been made on [slack channel](https://gitlab.slack.com/archives/CJWA4E9UG/p1754884098225659?thread_ts=1753650901.040289&cid=CJWA4E9UG)<br>- Getting good feedbacks on the [feedback issue](https://gitlab.com/gitlab-org/quality/component-performance-testing/-/issues/69) with teams keen on onboarding with CPT<br>- Refined the documentation in GitLab repo: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/200902<br><br>:issue-blocked: **blockers**:<br><br>- @john.mcdonnell assisting with Load testing for Agentic Duo chat<br><br>:arrow_forward: **next**:<br><br>- Working on feedback and refining report https://gitlab.com/gitlab-org/quality/component-performance-testing/-/merge_requests/84<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/193#note_2684456422_<br><!-- STATUS NOTE END --><br><br/><br/>**Nested Epics: 3**<br/><br/>• https://gitlab.com/groups/gitlab-org/quality/-/epics/198+ <br/>• https://gitlab.com/groups/gitlab-org/quality/-/epics/166+ <br/>• https://gitlab.com/groups/gitlab-org/quality/-/epics/194+ **2025-07-09**: This epic can be closed as CPT(Component performance testing) now has the capability to spin up CNG instance of GitLab using `orchestrator` which is an internal gem developed in the GitLab repo and used for e2e testing as well. Attached is the conclusion for this epic. :tada: **achievements**: * Documentation done on how to use CNG with CPT as a part of https://gitlab.com/gitlab-org/quality/component-performance-testing/-/merge_requests/50/diffs MR. :issue-blocked: **blockers**: - None :arrow_forward: **next**: - Will move on to [Data seeder](https://gitlab.com/groups/gitlab-org/quality/-/epics/198) epic _Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/194#note_2612894914_ <!-- STATUS NOTE END --><br/> | | [Dogfood Duo to generate performance report and provide MR analysis related to performance in GitLab MRs](https://gitlab.com/groups/gitlab-org/quality/-/epics/217) <br/> ~"group::performance enablement" | 2025-08-25 | 2025-10-08 | **2025-10-01**: <br>This epic can be closed as Performance reporting with Duo is now enabled on GitLab Repo MRs with more stability and also the ability to identify if the performance degradation is [environment related](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/205316#note_2768071651) or [code changes related](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/206178#note_2777222279).<br><br>:tada: **achievements**:<br><br>- Enabled Duo Reporting on GitLab repo MRs<br>- Reporting only runs on backend chagnes/Backend+frontend changes, thereby reducing noise for developers. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/206623/pipelines<br>- Developers can now provide `pipeline:skip-performance` label to skip running the performance test<br><br>:issue-blocked: **blockers**:<br><br>- None<br><br>:arrow_forward: **next**:<br><br>- Move towards working on https://gitlab.com/groups/gitlab-org/quality/-/epics/237+<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/217#note_2789840192_<br><!-- STATUS NOTE END --><br> | | [Adding Git for SSH performance testing support POC](https://gitlab.com/groups/gitlab-org/quality/-/epics/239) <br/> ~"group::performance enablement" | 2025-09-19 | 2025-10-17 | **2025-10-15**: <br>This Epic can be closed<br><br>:tada: **achievements**:<br><br>- synced with @jamesliu-gitlab on [gitaly team's needs and the oddities we uncovered](https://gitlab.com/groups/gitlab-org/quality/-/epics/239#note_2814047505)<br>- Reviewed the findings and made the decision on the path forward, [building a custom K6 extension](https://gitlab.com/groups/gitlab-org/quality/-/epics/239#recommendation)<br>- Kudos to @john.mcdonnell for doing some exploration into [implementing in native Golang](https://gitlab.com/gitlab-org/quality/quality-engineering/xk6-git-ssh/-/merge_requests/1) while I was building and testing the POC, that rounded out the lessons learned and enabled a more complete decision.<br><br>:arrow_forward: **next**:<br><br>- We have unblocked https://gitlab.com/groups/gitlab-org/quality/-/epics/209+ and will continue development there.<br>- We will continue [exploring the performance oddities uncovered in this POC](https://gitlab.com/gitlab-org/quality/quality-engineering/team-tasks/-/issues/3923)<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/239#note_2821273003_<br><!-- STATUS NOTE END --><br> | | [Automated Database Query Analysis](https://gitlab.com/groups/gitlab-org/quality/-/epics/164) <br/> ~"group::performance enablement" | | 2025-05-02 | **2025-04-30**: <br>The functionality to extract new SQL queries on MRs is now running in production and available for all new MRs. There was a concern prior to starting this epic that we would have some false positive results, and this has proven to be the case.<br>We can address how to better filter out these results as a follow up when we have a larger dataset to understand how and where they originate from.<br><br>:tada: **achievements**:<br>- Completed functionality :tada:<br><br>:issue-blocked: **blockers**:<br>-<br><br>:arrow_forward: **next**:<br>-<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/164#note_2476952186_<br><!-- STATUS NOTE END --><br><br/><br/>**Nested Epics: 1**<br/><br/>• https://gitlab.com/groups/gitlab-org/quality/-/epics/150+ <br/> | | [Onboard Developer Experience: Performance Enablement](https://gitlab.com/groups/gitlab-org/quality/-/epics/120) <br/> ~"group::performance enablement" | | 2025-02-11 | **2024-12-11**: <br>:tada: **achievements**:<br>- Transition of Self Managed Platform team backlog items to Performance Enablement team or Software Delivery Framework team<br>- Created Performance Enablement Team [HB](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/developer-experience/performance-enablement/) page<br>- ASYNC Team Roadmap workshop to define various tracks for Performance Enablement and related issues were raised to tie to roadmap epics<br><br>:arrow_forward: **next**:<br>- Performance Enablement Roadmap [MR](gitlab-com/gl-infra/infra-roadmap!29) to be reviewed<br>- Team roadmap workshop round 2 for refinement of roadmap epics<br><br>_Copied from https://gitlab.com/groups/gitlab-org/quality/-/epics/120#note_2254336867_<br><!-- STATUS NOTE END --><br> | </details> ### :rotating_light: Epics that need attention These linked epics are not in the correct state or missing a workflow label <details> | **Topic** | **Links** | **Reason** | |-----------|-----------|-------------| | [Selective test execution to lower GPT test run times from 90+ minutes](https://gitlab.com/groups/gitlab-org/quality/quality-engineering/-/epics/158) <br/> @vishal.s.patel (+3) <br/> group::performance enablement | Epic has ~"workflow-infra::Done" but is opened | | [Expand data seeding parallelisation for all data types](https://gitlab.com/groups/gitlab-org/quality/-/epics/196) <br/> (+0) <br/> group::performance enablement | Epic has ~"workflow-infra::Done" but is opened | </details>