docs: back-link the two separate scaling pages #11296
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- "Running At Massive Scale" is in the User Guide, while "Scaling" (along with HA, DR, etc) is in the Operator Guide
- link the two to each other as they have different information
- rate limit and GC in one, horizontal and vertical scaling and sharding in the other
Signed-off-by: Anton Gilgur <agilgur5@gmail.com>
terrytangyuan
approved these changes
Jul 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Modifications
Verification
n/a
Review Notes
Should these pages be consolidated into one?
I'm not sure why one was put into the User Guide vs. the Operator Guide though, so don't know the original rationale. As a user, it does instill some confidence that Argo can scale quite a bit, so I could potentially assume some rationale there.
But I would think all the config details would be left to the Operator Guide and the User Guide would just have a summary of benchmarks or something and then just link to the Operator Guide for how to achieve those numbers via configuration.