fix: raise eleventy heap cap from 2048 to 3072 MB - #409
Merged
Conversation
#397 lowered --max-old-space-size from 4096 to 2048 based on a 210-page garden. Large text-heavy gardens (~1100+ notes) exceed that: the build dies with a V8 "allocation failure" at ~2 GB heap while the 4Gi build container still has half its memory unused. 3072 gives those gardens room while still leaving ~1 GB on a 4Gi container for sharp's native allocations, which was the reason #397 lowered it in the first place. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FuHUwv79QekUJwCMB4rpvh
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.
Why
#397 lowered
--max-old-space-sizefrom 4096 to 2048, tuned on a 210-page garden. Large text-heavy gardens (~1,100+ notes, ~10 min builds) now die mid-build with a V8allocation failureat ~2 GB heap, while a 4Gi build container (like vercel has) still has half its memory free. First hit: a hosted garden that had built fine on 4096.Change
One line in
package.json:--max-old-space-size=2048→3072.3072 clears the gardens we've seen fail (heap peaked right at the 2 GB cap) and still leaves ~1 GB on a 4Gi container for sharp's native memory, which was #397's reason for lowering it.