Improve Application Memory Documentation#3739
Open
benjaminach wants to merge 18 commits into
Open
Conversation
… Metrics to this new page
benjaminach
changed the title
leo-scalingo
requested changes
May 11, 2026
Co-authored-by: Léo Unbekandt <159253935+leo-scalingo@users.noreply.github.com>
EtienneM
requested changes
May 12, 2026
Frzk
requested changes
May 13, 2026
Contributor
Frzk
left a comment
Frzk
left a comment
There was a problem hiding this comment.
non-blocking: While I understand the need for a "Memory Management" section in each language section, I feel like there's also some duplicated content. I think these should be revised and completed when we'll rework the languages pages.
non-blocking: The OOM error description is quite developed compared to the others. IMHO, this creates a gap and a lack of homogeneity that should ideally be filled (in a way or another) at some point.
praise: Thanks for moving the "OOM Crash" section to a more appropriate one 👍
praise: Thanks for caring about the little things (spelling, etc).
Co-authored-by: François <francois+github@kubler.org>
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
4 participants
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.
This PR improves the documentation around application memory usage on Scalingo.
It clarifies how memory, swap, container sizes, metrics, and runtime crashes relate to each other, and moves the OOM crash explanation to the Runtime Issues page where it better fits troubleshooting workflows.
It also adds language-specific memory management pointers for Go, Java, Node.js, PHP, Python, and Ruby, so users can find the main runtime settings that influence memory usage.
Changes