Commit 437c3ec5 authored by Joshua Lambert's avatar Joshua Lambert

Merge branch 'cg-review-enablement-plans' into 'master'

Fixed typos, updated wording

See merge request !39383
parents 3f8520bd aaa753de
Pipeline #112163379 passed with stages
in 11 minutes and 48 seconds
......@@ -2,7 +2,7 @@
The Database group is focused on improving the scalability, performance, and resilience of the relational database as well as instituting best practices across the wider development organization.
The primary focus of the team in 2020 is to improve the scalability of the Postgres database. We plan to achieve this by leveraging new features in Postgres 11 and 12, namely partitioning and sharding. As a first iteration, we will implement partitioning for problematic tables, providing additional headroom and performance. Later, we will leverage the partitioning work and roll out sharding of the Postgres instances themselves, to improve isolation and reduce the impact of noisy neighbor situations.
The primary focus of the team in 2020 is to improve the performance and scalability of the Postgres database. [Upgrading to PosgreSQL 11](https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/71) from our current supported version of 9.6 will allow us to take advantage of newer features such as declarative partitioning while also realizing the performance gains included in PostgreSQL 11. As a first iteration, we will implement partitioning for problematic tables, providing additional headroom and performance. Later, we will leverage the partitioning work and roll out sharding of the Postgres instances themselves, to improve isolation and reduce the impact of noisy neighbor situations.
* [Postgres Partitioning](https://gitlab.com/groups/gitlab-org/-/epics/2023)
* [Postges Sharding](https://gitlab.com/groups/gitlab-org/-/epics/1854)
\ No newline at end of file
* [Postgres Sharding](https://gitlab.com/groups/gitlab-org/-/epics/1854)
\ No newline at end of file
......@@ -2,7 +2,7 @@
The Memory group is focused on improving performance and reducing the memory consumption of GitLab.
The focus of the team will be threefold: foundational improvements like [Puma](https://gitlab.com/groups/gitlab-org/-/epics/954) to significantly redue memory usage, assisting in addressing hotspots in our codebase that are affecting customers, as well as driving organization-wide changes to ensure net-new code is performant.
The focus of the team will be threefold: foundational improvements like [Puma](https://gitlab.com/groups/gitlab-org/-/epics/954) to significantly reduce memory usage, assisting in addressing memory and performance bottlenecks that are affecting customers, as well as driving organization-wide changes to ensure net-new code is performant.
* [Import/Export 10x improvements](https://gitlab.com/groups/gitlab-org/-/epics/1810)
* [Improve development practices around memory usage](https://gitlab.com/groups/gitlab-org/-/epics/1415)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment