Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
264aa533
Commit
264aa533
authored
Sep 23, 2020
by
Craig Norris
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update spacing and formatting for tables
parent
c6236ab7
Changes
7
Hide whitespace changes
Inline
Side-by-side
Showing
7 changed files
with
100 additions
and
105 deletions
+100
-105
doc/administration/reference_architectures/10k_users.md
doc/administration/reference_architectures/10k_users.md
+19
-20
doc/administration/reference_architectures/1k_users.md
doc/administration/reference_architectures/1k_users.md
+4
-4
doc/administration/reference_architectures/25k_users.md
doc/administration/reference_architectures/25k_users.md
+19
-20
doc/administration/reference_architectures/2k_users.md
doc/administration/reference_architectures/2k_users.md
+7
-7
doc/administration/reference_architectures/3k_users.md
doc/administration/reference_architectures/3k_users.md
+16
-17
doc/administration/reference_architectures/50k_users.md
doc/administration/reference_architectures/50k_users.md
+19
-20
doc/administration/reference_architectures/5k_users.md
doc/administration/reference_architectures/5k_users.md
+16
-17
No files found.
doc/administration/reference_architectures/10k_users.md
View file @
264aa533
...
...
@@ -17,21 +17,21 @@ full list of reference architectures, see
| Service | Nodes | Configuration | GCP | AWS | Azure |
|--------------------------------------------|-------------|-------------------------|-----------------|-------------|----------|
| External load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Consul | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| PostgreSQL | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| PgBouncer | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Internal load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Redis - Cache | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Redis - Queues / Shared State | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Redis Sentinel - Cache | 3 | 1 vCPU, 1.7
GB memory
| g1-small | t2.small | B1MS |
| Redis Sentinel - Queues / Shared State | 3 | 1 vCPU, 1.7
GB memory
| g1-small | t2.small | B1MS |
| Gitaly | 2 (minimum) | 16 vCPU, 60
GB memory
| n1-standard-16 | m5.4xlarge | D16s v3 |
| Sidekiq | 4 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| GitLab Rails | 3 | 32 vCPU, 28.8
GB memory
| n1-highcpu-32 | c5.9xlarge | F32s v2 |
| Monitoring node | 1 | 4 vCPU, 3.6
GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| Object
S
torage | n/a | n/a | n/a | n/a | n/a |
| NFS
Server | 1 | 4 vCPU, 3.6GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| External load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Consul | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| PostgreSQL | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| PgBouncer | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Internal load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Redis - Cache | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Redis - Queues / Shared State | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Redis Sentinel - Cache | 3 | 1 vCPU, 1.7
GB memory
| g1-small | t2.small | B1MS |
| Redis Sentinel - Queues / Shared State | 3 | 1 vCPU, 1.7
GB memory
| g1-small | t2.small | B1MS |
| Gitaly | 2 (minimum) | 16 vCPU, 60
GB memory
| n1-standard-16 | m5.4xlarge | D16s v3 |
| Sidekiq | 4 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| GitLab Rails | 3 | 32 vCPU, 28.8
GB memory
| n1-highcpu-32 | c5.9xlarge | F32s v2 |
| Monitoring node | 1 | 4 vCPU, 3.6
GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| Object
s
torage | n/a | n/a | n/a | n/a | n/a |
| NFS
server | 1 | 4 vCPU, 3.6 GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
The Google Cloud Platform (GCP) architectures were built and tested using the
[
Intel Xeon E5 v3 (Haswell)
](
https://cloud.google.com/compute/docs/cpu-platforms
)
...
...
@@ -40,11 +40,10 @@ or higher, are required for your CPU or node counts. For more information, see
our
[
Sysbench
](
https://github.com/akopytov/sysbench
)
-based
[
CPU benchmark
](
https://gitlab.com/gitlab-org/quality/performance/-/wikis/Reference-Architectures/GCP-CPU-Benchmarks
)
.
For data objects (such as LFS, Uploads, or Artifacts), an
[
object storage service
](
#configure-the-object-storage
)
is recommended instead
of NFS where possible, due to better performance and availability. Since this
doesn't require a node to be set up,
*Object Storage*
is noted as not
applicable (n/a) in the previous table.
Due to better performance and availability, for data objects (such as LFS,
uploads, or artifacts), using an
[
object storage service
](
#configure-the-object-storage
)
is recommended instead of using NFS. Using an object storage service also
doesn't require you to provision and maintain a node.
## Setup components
...
...
doc/administration/reference_architectures/1k_users.md
View file @
264aa533
...
...
@@ -20,8 +20,8 @@ many organizations .
| Users | Configuration | GCP | AWS | Azure |
|--------------|-------------------------|----------------|-----------------|----------------|
| Up to 500 | 4 vCPU, 3.6
GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| Up to 1,000 | 8 vCPU, 7.2
GB memory
| n1-highcpu-8 | c5.2xlarge | F8s v2 |
| Up to 500 | 4 vCPU, 3.6
GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| Up to 1,000 | 8 vCPU, 7.2
GB memory
| n1-highcpu-8 | c5.2xlarge | F8s v2 |
The Google Cloud Platform (GCP) architectures were built and tested using the
[
Intel Xeon E5 v3 (Haswell)
](
https://cloud.google.com/compute/docs/cpu-platforms
)
...
...
@@ -30,9 +30,9 @@ or higher, are required for your CPU or node counts. For more information, see
our
[
Sysbench
](
https://github.com/akopytov/sysbench
)
-based
[
CPU benchmark
](
https://gitlab.com/gitlab-org/quality/performance/-/wikis/Reference-Architectures/GCP-CPU-Benchmarks
)
.
In addition to the stated configurations, we recommend having at least 2GB of
In addition to the stated configurations, we recommend having at least 2
GB of
swap on your server, even if you currently have enough available memory. Having
swap
will help
reduce the chance of errors occurring if your available memory
swap
helps to
reduce the chance of errors occurring if your available memory
changes. We also recommend configuring the kernel's swappiness setting to a
lower value (such as
`10`
) to make the most of your memory, while still having
the swap available when needed.
...
...
doc/administration/reference_architectures/25k_users.md
View file @
264aa533
...
...
@@ -17,21 +17,21 @@ full list of reference architectures, see
| Service | Nodes | Configuration | GCP | AWS | Azure |
|-----------------------------------------|-------------|-------------------------|-----------------|-------------|----------|
| External load balancing node | 1 | 4 vCPU, 3.6
GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| Consul | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| PostgreSQL | 3 | 8 vCPU, 30
GB memory
| n1-standard-8 | m5.2xlarge | D8s v3 |
| PgBouncer | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Internal load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Redis - Cache | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Redis - Queues / Shared State | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Redis Sentinel - Cache | 3 | 1 vCPU, 1.7
GB memory
| g1-small | t2.small | B1MS |
| Redis Sentinel - Queues / Shared State | 3 | 1 vCPU, 1.7
GB memory
| g1-small | t2.small | B1MS |
| Gitaly | 2 (minimum) | 32 vCPU, 120
GB memory
| n1-standard-32 | m5.8xlarge | D32s v3 |
| Sidekiq | 4 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| GitLab Rails | 5 | 32 vCPU, 28.8
GB memory
| n1-highcpu-32 | c5.9xlarge | F32s v2 |
| Monitoring node | 1 | 4 vCPU, 3.6
GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| Object
S
torage | n/a | n/a | n/a | n/a | n/a |
| NFS
Server | 1 | 4 vCPU, 3.6GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| External load balancing node | 1 | 4 vCPU, 3.6
GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| Consul | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| PostgreSQL | 3 | 8 vCPU, 30
GB memory
| n1-standard-8 | m5.2xlarge | D8s v3 |
| PgBouncer | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Internal load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Redis - Cache | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Redis - Queues / Shared State | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Redis Sentinel - Cache | 3 | 1 vCPU, 1.7
GB memory
| g1-small | t2.small | B1MS |
| Redis Sentinel - Queues / Shared State | 3 | 1 vCPU, 1.7
GB memory
| g1-small | t2.small | B1MS |
| Gitaly | 2 (minimum) | 32 vCPU, 120
GB memory
| n1-standard-32 | m5.8xlarge | D32s v3 |
| Sidekiq | 4 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| GitLab Rails | 5 | 32 vCPU, 28.8
GB memory
| n1-highcpu-32 | c5.9xlarge | F32s v2 |
| Monitoring node | 1 | 4 vCPU, 3.6
GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| Object
s
torage | n/a | n/a | n/a | n/a | n/a |
| NFS
server | 1 | 4 vCPU, 3.6 GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
The Google Cloud Platform (GCP) architectures were built and tested using the
[
Intel Xeon E5 v3 (Haswell)
](
https://cloud.google.com/compute/docs/cpu-platforms
)
...
...
@@ -40,11 +40,10 @@ or higher, are required for your CPU or node counts. For more information, see
our
[
Sysbench
](
https://github.com/akopytov/sysbench
)
-based
[
CPU benchmark
](
https://gitlab.com/gitlab-org/quality/performance/-/wikis/Reference-Architectures/GCP-CPU-Benchmarks
)
.
For data objects (such as LFS, Uploads, or Artifacts), an
[
object storage service
](
#configure-the-object-storage
)
is recommended instead
of NFS where possible, due to better performance and availability. Since this
doesn't require a node to be set up,
*Object Storage*
is noted as not
applicable (n/a) in the previous table.
Due to better performance and availability, for data objects (such as LFS,
uploads, or artifacts), using an
[
object storage service
](
#configure-the-object-storage
)
is recommended instead of using NFS. Using an object storage service also
doesn't require you to provision and maintain a node.
## Setup components
...
...
doc/administration/reference_architectures/2k_users.md
View file @
264aa533
...
...
@@ -17,14 +17,14 @@ For a full list of reference architectures, see
| Service | Nodes | Configuration | GCP | AWS | Azure |
|------------------------------------------|--------|-------------------------|----------------|--------------|---------|
| Load balancer | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| PostgreSQL | 1 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| Redis | 1 | 1 vCPU, 3.75
GB memory
| n1-standard-1 | m5.large | D2s v3 |
| Gitaly | 1 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| GitLab Rails | 2 | 8 vCPU, 7.2
GB memory
| n1-highcpu-8 | c5.2xlarge | F8s v2 |
| Monitoring node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Load balancer | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| PostgreSQL | 1 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| Redis | 1 | 1 vCPU, 3.75
GB memory
| n1-standard-1 | m5.large | D2s v3 |
| Gitaly | 1 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| GitLab Rails | 2 | 8 vCPU, 7.2
GB memory
| n1-highcpu-8 | c5.2xlarge | F8s v2 |
| Monitoring node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Object storage | n/a | n/a | n/a | n/a | n/a |
| NFS server (optional, not recommended) | 1 | 4 vCPU, 3.6
GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| NFS server (optional, not recommended) | 1 | 4 vCPU, 3.6
GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
The Google Cloud Platform (GCP) architectures were built and tested using the
[
Intel Xeon E5 v3 (Haswell)
](
https://cloud.google.com/compute/docs/cpu-platforms
)
...
...
doc/administration/reference_architectures/3k_users.md
View file @
264aa533
...
...
@@ -24,18 +24,18 @@ costly-to-operate environment by using the
| Service | Nodes | Configuration | GCP | AWS | Azure |
|--------------------------------------------|-------------|-----------------------|----------------|-------------|---------|
| External load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Redis | 3 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| Consul + Sentinel | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| PostgreSQL | 3 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| PgBouncer | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Internal load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Gitaly | 2 (minimum) | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Sidekiq | 4 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| GitLab Rails | 3 | 8 vCPU, 7.2
GB memory
| n1-highcpu-8 | c5.2xlarge | F8s v2 |
| Monitoring node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Object
S
torage | n/a | n/a | n/a | n/a | n/a |
| NFS
Server (optional, not recommended) | 1 | 4 vCPU, 3.6GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| External load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Redis | 3 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| Consul + Sentinel | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| PostgreSQL | 3 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| PgBouncer | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Internal load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Gitaly | 2 (minimum) | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Sidekiq | 4 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| GitLab Rails | 3 | 8 vCPU, 7.2
GB memory
| n1-highcpu-8 | c5.2xlarge | F8s v2 |
| Monitoring node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Object
s
torage | n/a | n/a | n/a | n/a | n/a |
| NFS
server (optional, not recommended) | 1 | 4 vCPU, 3.6 GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
The Google Cloud Platform (GCP) architectures were built and tested using the
[
Intel Xeon E5 v3 (Haswell)
](
https://cloud.google.com/compute/docs/cpu-platforms
)
...
...
@@ -44,11 +44,10 @@ or higher, are required for your CPU or node counts. For more information, see
our
[
Sysbench
](
https://github.com/akopytov/sysbench
)
-based
[
CPU benchmark
](
https://gitlab.com/gitlab-org/quality/performance/-/wikis/Reference-Architectures/GCP-CPU-Benchmarks
)
.
For data objects (such as LFS, Uploads, or Artifacts), an
[
object storage service
](
#configure-the-object-storage
)
is recommended instead
of NFS where possible, due to better performance and availability. Since this
doesn't require a node to be set up,
*Object Storage*
is noted as not
applicable (n/a) in the previous table.
Due to better performance and availability, for data objects (such as LFS,
uploads, or artifacts), using an
[
object storage service
](
#configure-the-object-storage
)
is recommended instead of using NFS. Using an object storage service also
doesn't require you to provision and maintain a node.
## Setup components
...
...
doc/administration/reference_architectures/50k_users.md
View file @
264aa533
...
...
@@ -17,21 +17,21 @@ full list of reference architectures, see
| Service | Nodes | Configuration | GCP | AWS | Azure |
|-----------------------------------------|-------------|-------------------------|-----------------|--------------|----------|
| External load balancing node | 1 | 8 vCPU, 7.2
GB memory
| n1-highcpu-8 | c5.2xlarge | F8s v2 |
| Consul | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| PostgreSQL | 3 | 16 vCPU, 60
GB memory
| n1-standard-16 | m5.4xlarge | D16s v3 |
| PgBouncer | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Internal load balancing node | 1 | 8 vCPU, 7.2
GB memory
| n1-highcpu-8 | c5.2xlarge | F8s v2 |
| Redis - Cache | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Redis - Queues / Shared State | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Redis Sentinel - Cache | 3 | 1 vCPU, 1.7
GB memory
| g1-small | t2.small | B1MS |
| Redis Sentinel - Queues / Shared State | 3 | 1 vCPU, 1.7
GB memory
| g1-small | t2.small | B1MS |
| Gitaly | 2 (minimum) | 64 vCPU, 240
GB memory
| n1-standard-64 | m5.16xlarge | D64s v3 |
| Sidekiq | 4 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| GitLab Rails | 12 | 32 vCPU, 28.8
GB memory
| n1-highcpu-32 | c5.9xlarge | F32s v2 |
| Monitoring node | 1 | 4 vCPU, 3.6
GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| Object
S
torage | n/a | n/a | n/a | n/a | n/a |
| NFS
Server | 1 | 4 vCPU, 3.6GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| External load balancing node | 1 | 8 vCPU, 7.2
GB memory
| n1-highcpu-8 | c5.2xlarge | F8s v2 |
| Consul | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| PostgreSQL | 3 | 16 vCPU, 60
GB memory
| n1-standard-16 | m5.4xlarge | D16s v3 |
| PgBouncer | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Internal load balancing node | 1 | 8 vCPU, 7.2
GB memory
| n1-highcpu-8 | c5.2xlarge | F8s v2 |
| Redis - Cache | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Redis - Queues / Shared State | 3 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| Redis Sentinel - Cache | 3 | 1 vCPU, 1.7
GB memory
| g1-small | t2.small | B1MS |
| Redis Sentinel - Queues / Shared State | 3 | 1 vCPU, 1.7
GB memory
| g1-small | t2.small | B1MS |
| Gitaly | 2 (minimum) | 64 vCPU, 240
GB memory
| n1-standard-64 | m5.16xlarge | D64s v3 |
| Sidekiq | 4 | 4 vCPU, 15
GB memory
| n1-standard-4 | m5.xlarge | D4s v3 |
| GitLab Rails | 12 | 32 vCPU, 28.8
GB memory
| n1-highcpu-32 | c5.9xlarge | F32s v2 |
| Monitoring node | 1 | 4 vCPU, 3.6
GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| Object
s
torage | n/a | n/a | n/a | n/a | n/a |
| NFS
server | 1 | 4 vCPU, 3.6 GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
The Google Cloud Platform (GCP) architectures were built and tested using the
[
Intel Xeon E5 v3 (Haswell)
](
https://cloud.google.com/compute/docs/cpu-platforms
)
...
...
@@ -40,11 +40,10 @@ or higher, are required for your CPU or node counts. For more information, see
our
[
Sysbench
](
https://github.com/akopytov/sysbench
)
-based
[
CPU benchmark
](
https://gitlab.com/gitlab-org/quality/performance/-/wikis/Reference-Architectures/GCP-CPU-Benchmarks
)
.
For data objects (such as LFS, Uploads, or Artifacts), an
[
object storage service
](
#configure-the-object-storage
)
is recommended instead
of NFS where possible, due to better performance and availability. Since this
doesn't require a node to be set up,
*Object Storage*
is noted as not
applicable (n/a) in the previous table.
Due to better performance and availability, for data objects (such as LFS,
uploads, or artifacts), using an
[
object storage service
](
#configure-the-object-storage
)
is recommended instead of using NFS. Using an object storage service also
doesn't require you to provision and maintain a node.
## Setup components
...
...
doc/administration/reference_architectures/5k_users.md
View file @
264aa533
...
...
@@ -24,18 +24,18 @@ costly-to-operate environment by using the
| Service | Nodes | Configuration | GCP | AWS | Azure |
|--------------------------------------------|-------------|-------------------------|----------------|-------------|----------|
| External load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Redis | 3 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| Consul + Sentinel | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| PostgreSQL | 3 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| PgBouncer | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Internal load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Gitaly | 2 (minimum) | 8 vCPU, 30
GB memory
| n1-standard-8 | m5.2xlarge | D8s v3 |
| Sidekiq | 4 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| GitLab Rails | 3 | 16 vCPU, 14.4
GB memory
| n1-highcpu-16 | c5.4xlarge | F16s v2 |
| Monitoring node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Object
S
torage | n/a | n/a | n/a | n/a | n/a |
| NFS
Server (optional, not recommended) | 1 | 4 vCPU, 3.6GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
| External load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Redis | 3 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| Consul + Sentinel | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| PostgreSQL | 3 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| PgBouncer | 3 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Internal load balancing node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Gitaly | 2 (minimum) | 8 vCPU, 30
GB memory
| n1-standard-8 | m5.2xlarge | D8s v3 |
| Sidekiq | 4 | 2 vCPU, 7.5
GB memory
| n1-standard-2 | m5.large | D2s v3 |
| GitLab Rails | 3 | 16 vCPU, 14.4
GB memory
| n1-highcpu-16 | c5.4xlarge | F16s v2 |
| Monitoring node | 1 | 2 vCPU, 1.8
GB memory
| n1-highcpu-2 | c5.large | F2s v2 |
| Object
s
torage | n/a | n/a | n/a | n/a | n/a |
| NFS
server (optional, not recommended) | 1 | 4 vCPU, 3.6 GB memory
| n1-highcpu-4 | c5.xlarge | F4s v2 |
The Google Cloud Platform (GCP) architectures were built and tested using the
[
Intel Xeon E5 v3 (Haswell)
](
https://cloud.google.com/compute/docs/cpu-platforms
)
...
...
@@ -44,11 +44,10 @@ or higher, are required for your CPU or node counts. For more information, see
our
[
Sysbench
](
https://github.com/akopytov/sysbench
)
-based
[
CPU benchmark
](
https://gitlab.com/gitlab-org/quality/performance/-/wikis/Reference-Architectures/GCP-CPU-Benchmarks
)
.
For data objects (such as LFS, Uploads, or Artifacts), an
[
object storage service
](
#configure-the-object-storage
)
is recommended instead
of NFS where possible, due to better performance and availability. Since this
doesn't require a node to be set up,
*Object Storage*
is noted as not
applicable (n/a) in the previous table.
Due to better performance and availability, for data objects (such as LFS,
uploads, or artifacts), using an
[
object storage service
](
#configure-the-object-storage
)
is recommended instead of using NFS. Using an object storage service also
doesn't require you to provision and maintain a node.
## Setup components
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment