Bump prerender concurrency to 3#710
Closed
bryantgillespie wants to merge 1 commit into
Closed
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Member
Author
|
wasn't the problem |
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.
What
Bumps Nitro prerender
concurrencyfrom1to3to speed up builds.Why
concurrency: 1was set to keep peak memory under the Vercel build ceiling back when per-route API-reference rendering (Shiki highlighting + large OAS payloads) was OOM-killing the build. The pre-render precompute work (#708) moved that expensive highlighting to a build-time step, making each route render much lighter — so parallel renders should now fit comfortably.This is a test to see how far we can push concurrency without OOMing. Starting conservative at 3.
Verification
pnpm buildcompletes clean locally withconcurrency: 3— no OOM, noENOTDIR./apiindex + all per-tag reference pages.api/output is a proper directory (index + per-tag subdirs), no payload-cache file/dir collision.Watch on deploy
Vercel build memory. If it OOMs, revert this single commit; if it's clean with headroom, we can try higher.