Speed up CI build via nitro.prerender.concurrency - #5559
Draft
ZJvandeWeg wants to merge 1 commit into
Draft
Conversation
CI's "Build the forge" step in test.yml consistently spent ~11.4 of its ~13.6 minutes prerendering ~560 routes. Log analysis showed the sum of individual route render times matched the phase's wall-clock time almost exactly, meaning routes were rendering strictly serially - Nitro's prerender concurrency defaults to 1 and nuxt.config.ts never overrode it. Most of the per-route cost is async (content queries, template rendering) rather than CPU-bound, so concurrency can safely exceed the runner's core count.
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ZJvandeWeg
marked this pull request as draft
August 10, 2026 18:53
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.
Summary
Testsworkflow'sBuild the forgestep (npm run build:nuxt:skip-images) has consistently taken ~13.6 minutes across recentmainruns.nuxt.config.ts'snitro.prerenderblock never setconcurrency, so it was stuck at Nitro's default of 1.concurrency: 10. Most of the per-route cost is async (content collection queries, SSR template rendering) rather than CPU-bound, so this can reasonably exceed the runner's core count (GH-hostedubuntu-latest= 4 vCPUs).Test plan
concurrency: 10(loggedPrerendering 1069 routesand proceeded normally into the next build phase, no errors)Build the forgecompletes faster than the ~13.6 minute baseline, and that nothing regresses (in particular, watch for any race condition in build-time route-collection helpers that assumed serial execution)🤖 Generated with Claude Code