craigg

Most backend developers work on all aspects of GitLab, building features, fixing bugs, and generally improving the application. The Database Group is responsible for making application changes to improve database performance, availability and reliability. Additionally, the Backend Engineer, Database will be expected to review database related code with the goal of eventually becoming a Database Maintainer.

We have multiple other open roles at GitLab - https://boards.greenhouse.io/gitlab/

GitLab | Multiple | REMOTE only

I'm hiring for Backend Engineer, Database roles (https://about.gitlab.com/job-families/engineering/backend-en...) but we have a handful of other roles open as well. To view all of the roles for which we are actively sourcing - https://about.gitlab.com/jobs/careers/

When you apply, indicate the desired role.

As an Engineering Manager for the recently formed Database team here at GitLab, this tool has proven to be incredibly valuable. We floated the idea of running this on a regular basis back in April https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues... and now we have daily reports that we review https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues...

samokhvalov helped us to get this set up

We've been considering which minimum version requirement of PostgreSQL at GitLab here: https://gitlab.com/gitlab-org/gitlab/issues/31454. We will add PostgreSQL 12 for consideration as well.

The partitioning improvements will help with our events tables (https://gitlab.com/gitlab-org/gitlab/issues/24538) as Sid notes above. Also the notable improvements in query performance, especially over large data sets will help with the other large tables we need to address. Most notably: merge_request_diff_commits https://gitlab.com/gitlab-org/gitlab/issues/31454

and ci_builds https://gitlab.com/gitlab-org/gitlab/issues/30441

Hi this is Craig, the Engineering Manager for the Memory team. We're actively working on reducing the memory issues with GitLab. We are approaching this by responding to known issues and building out proactive tooling to inform developers of memory usage during the development cycle.

You can follow along with our efforts on this board: https://gitlab.com/groups/gitlab-org/-/boards/1143987?label_...