Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2023-04-15 06:14:24 +0300
committerGitLab Bot <gitlab-bot@gitlab.com>2023-04-15 06:14:24 +0300
commitd482517583173924ba7961a2b0e9e07d1b51bb78 (patch)
tree01ef6769846a451c4e3539caa1e32f54dd001157 /doc/development/merge_request_concepts
parent9b0b4d9b9484aaeb82de5f24942460c679ae909e (diff)
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/merge_request_concepts')
-rw-r--r--doc/development/merge_request_concepts/performance.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/merge_request_concepts/performance.md b/doc/development/merge_request_concepts/performance.md
index 3b2a097ea2d..174307fc6a7 100644
--- a/doc/development/merge_request_concepts/performance.md
+++ b/doc/development/merge_request_concepts/performance.md
@@ -158,7 +158,7 @@ query. This in turn makes it much harder for this code to overload a database.
## Use read replicas when possible
-In a DB cluster we have many read replicas and one primary. A classic use of scaling the DB is to have read-only actions be performed by the replicas. We use [load balancing](../../administration/postgresql/database_load_balancing.md) to distribute this load. This allows for the replicas to grow as the pressure on the DB grows.
+In a DB cluster we have many read replicas and one primary. A classic use of scaling the DB is to have read-only actions be performed by the replicas. We use [load balancing](../database/load_balancing.md) to distribute this load. This allows for the replicas to grow as the pressure on the DB grows.
By default, queries use read-only replicas, but due to
[primary sticking](../../administration/postgresql/database_load_balancing.md#primary-sticking), GitLab uses the