Update Load Balancer sizing in Ref Arch docs
What does this MR do?
MR updates sizing guidance for Load Balancers to move up a size in the Reference Architecture documentation after a review of CPU and Network Bandwidth usage in heavy situations such as a large amount of concurrent clones of a large monorepo. Additionally, for AWS machine types specifically network bursting can be impactful compared with others so machine types have been switched to network enhanced variants (c5n
) to compensate.
Related issues
Closes gitlab-org/quality/reference-architectures#286 (closed)
Author's checklist
-
Optional. Consider taking the GitLab Technical Writing Fundamentals course. -
Follow the: -
If you're adding a new page, add the product tier badge under the H1 topic title. -
If you are a GitLab team member, request a review based on: - The documentation page's metadata.
- The associated Technical Writer.
If you are a GitLab team member and only adding documentation, do not add any of the following labels:
~"frontend"
~"backend"
~"type::bug"
~"database"
These labels cause the MR to be added to code verification QA issues.
Reviewer's checklist
Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.
If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.
-
If the content requires it, ensure the information is reviewed by a subject matter expert. - Technical writer review items:
-
Ensure docs metadata is present and up-to-date. -
Ensure the appropriate labels are added to this MR. -
Ensure a release milestone is set. - If relevant to this MR, ensure content topic type principles are in use, including:
-
The headings should be something you'd do a Google search for. Instead of Default behavior
, say something likeDefault behavior when you close an issue
. -
The headings (other than the page title) should be active. Instead of Configuring GDK
, say something likeConfigure GDK
. -
Any task steps should be written as a numbered list. - If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
-
-
-
Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Merge request reports
Activity
assigned to @grantyoung
2 Warnings 9b018895: The commit body should not contain more than 72 characters per line. For more information, take a look at our Commit message guidelines. This merge request does not refer to an existing milestone. 1 Message This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge. Documentation review
The following files require a review from a technical writer:
-
doc/administration/reference_architectures/10k_users.md
(Link to current live version) -
doc/administration/reference_architectures/25k_users.md
(Link to current live version) -
doc/administration/reference_architectures/2k_users.md
(Link to current live version) -
doc/administration/reference_architectures/3k_users.md
(Link to current live version) -
doc/administration/reference_architectures/50k_users.md
(Link to current live version) -
doc/administration/reference_architectures/5k_users.md
(Link to current live version) -
doc/administration/reference_architectures/index.md
(Link to current live version)
The review does not need to block merging this merge request. See the:
-
Metadata for the
*.md
files that you've changed. The first few lines of each*.md
file identify the stage and group most closely associated with your docs change. - The Technical Writer assigned for that stage and group.
- Documentation workflows for information on when to assign a merge request for review.
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Danger-
added docs-only label
Thank you @grantyoung for getting these changes in quickly!
- Resolved by Achilleas Pipinellis
Ok this is ready for review @axil thanks.
requested review from @axil
added 1702 commits
-
1942db76...71cca53f - 1699 commits from branch
master
- 3b5fa535 - Update Load Balancer sizing in Ref Arch docs
- 72c1a08d - Add update history note
- 667762c7 - Add line in main RA index doc
Toggle commit list-
1942db76...71cca53f - 1699 commits from branch
added 757 commits
-
667762c7...f362ed02 - 754 commits from branch
master
- 9b018895 - Update Load Balancer sizing in Ref Arch docs
- 38604772 - Add update history note
- d31a34d7 - Add line in main RA index doc
Toggle commit list-
667762c7...f362ed02 - 754 commits from branch
changed milestone to %16.10
added Technical Writing devopssystems groupdistribution labels
added sectioncore platform label
@axil, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline was created more than 4 hours ago, you should:
- Ensure the merge request is not in Draft status.
- Start a pipeline (especially important for Community contribution merge requests).
- Set the merge request to auto-merge.
This is a guideline, not a rule. Please consider replying to this comment for transparency.
This message was generated automatically. You're welcome to improve it.
mentioned in commit e45200a9
added workflowstaging-canary label
added workflowcanary label and removed workflowstaging-canary label
mentioned in merge request gitlab-environment-toolkit!1302 (merged)
added releasedpublished label