GitLab Memory Team, 12 Nov 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.7 Kickoff - Enablement:Memory

Description

Kickoff for the 13.7 release for the memory team.

Planning issue: https://gitlab.com/gitlab-org/memory-team/team-tasks/-/issues/69

A

Hello: everyone, my name is fabian simmer, I'm the acting product manager for gitlab's memory team and today, I'm going to walk you through our plans for the next kitkat release. Gitlab, 13.7 and 13.7 is scheduled to arrive on december 22nd so shortly before christmas, our christmas gift to our community and our customers.

A

So let me share my screen and I'll walk you through the priorities for the memory team in that milestone.

A

So for 13.7, we are going to focus on a specific area that is really important to our product strategy as a whole.

A

The memory team is very concerned with the performance of gitlab, and one of the most important things to consider for performance reasons is the memory consumption of gitlab and gitlab can scale from installations that actually have only a few users to installations that have ten thousands of users and something that we are trying to focus on is to understand how gitlab can run in a memory constrained environment and the memory consumption here is really one of those issues where you know currently, four gigabytes of ram is something that we may need, but how can we actually reduce this further to, for example, two gigabytes of ram and because this is a very complex area, there's not one thing that can be done to actually accomplish this in 13.7, the memory team will come together and actually focus on this for an entire week, and this is here in our sort of focus week.

A

Four for one week, the team is going to work more synchronously, it's going to meet every day and it's going to try and understand what specifically can be done to reduce the memory consumption of gitlab to a smaller footprint, and so we don't quite know yet what we'll find so when there are not so many really small issues.

A

Yet this is going to come out of these these discussions and that work the team is going to do, but we do have an idea already on some specifics that we can maybe address, and one here is the life cycle, events for initializers, and so there are just some more expensive operations here that we may want to address and actually separate them out, so that we don't increase our overall memory consumption.

A

So this is one of the things that we we may be addressing linked to this here is the sidekick cluster preloading. So this is another issue that we are going to look at and so currently when x, when we actually bundle execute sidekick. This is quite memory and efficient. We know this already, so there may be an opportunity here to configure this in a different way set it up to use not as much memory.

A

So those are two of the specific items here, but overall the goal is really to come together and then, while the work is ongoing surface, these concerns really understand what would it take? What would we need to do and how would it look and then once that is clear, address those issues um in the other weeks of the release or further down the road.

A

So I think the team is quite excited about this, to have the focus and to take the time to do it and I'm going to report back for 13.8 and see where we are at that point. So have a great rest of the month and thank you for listening, bye.