Container sizing guidance#3748
Open
benjaminach wants to merge 9 commits into
Open
Conversation
benjaminach
changed the title
benjaminach
commented
May 21, 2026
|
|
||
| - `web` for HTTP traffic; | ||
| - `worker` for background jobs; | ||
| - `clock` or `scheduler` for recurring jobs; |
Contributor
Author
There was a problem hiding this comment.
parler du cron?
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add a dedicated guide to help customers choose a safe initial container size, validate it with metrics and load testing, and understand remediation paths when memory usage becomes critical.
Also update the general scaling page with a short section clarifying how memory usage affects vertical vs horizontal scaling decisions.
Changes