Build and enhance a highly performant GitLab product portfolio, and establish best practices for performance oriented development.
The Memory team is responsible for optimizing GitLab application performance by managing the memory resources required. The team is also responsible for changes affecting the responsiveness of the application. We will accomplish these goals in two ways. First we will research and resolve reported memory issues to the best of our ability and within our published SLAs. Additionally, will build tooling to proactively inform developers of the static and dynamic memory consumption of their proposed changes. You can read more about our approach, in detail, here.
The following people are permanent members of the Memory Team:
| Person | Role |
|---|---|
| Craig Gomes | Engineering Manager, Memory & Database |
| Kamil Trzciński | Distinguished Engineer, Ops and Enablement |
| Qingyu Zhao | Senior Backend Engineer, Memory |
| Aleksei Lipniagov | Senior Backend Engineer, Memory |
| Nikola Milojevic | Senior Backend Engineer, Memory |
| Matthias Käppler | Senior Backend Engineer, Memory |
The following members of other functional teams are our stable counterparts:
| Person | Role |
|---|---|
| Fabian Zimmer | Principal Product Manager, Geo |
Where we can we follow the GitLab values and communicate asynchronously. However, there have a few important recurring meetings. Please reach out to the #g_memory Slack channel if you'd like to be invited.
We follow the GitLab engineering workflow guidelines. To bring an issue to our attention please create an issue in the relevant project, or in the Memory team project. Add the ~"group::memory" label along with any other relevant labels. If it is an urgent issue, please reach out to the Product Manager or Engineering Manager listed in the Stable Counterparts section above.
The Memory Team uses the Memory by Milestone board to plan issues for each milestone.
We are adopting a lightweight weighting system, similar to those adopted by other teams.
We use the ~Deliverable label to track our Say/Do ratio. At the beginning of each milestone, during a Memory Team Weekly meeting, we review the issues and determine those issues we are confident we can deliver within the milestone. The issue will be marked with the ~Deliverable label. At the end of the milestone the successfully completed issues with the ~Deliverable label are tracked in two places. We have a dashboard in Sisense that will calculate how many were delivered within the mileston and account for issues that were moved. Additionally, our milestone retro issue lists all of the ~Deliverable issues shipped along with those that missed the milesone.
The Memory Team Roadmap gives a view of what is currently in flight as well as projects that have been prioritized for the next 3+ months.
