Parallel Query Running with Gatsby 4
summary
Parallel query running re-architects Gatsby to run GraphQL page and static queries across worker processes, using lmdb-store shared DB to exchange data and build artifacts, which lets builds utilize all CPU cores instead of one. Real sites see large wins: 27,000-page Contentful site: 2.5x faster query running, 9,000-page MDX site: 3x faster. Enable via the Gatsby 4 preview default or a config flag; benefits appear for query-heavy, CPU-bound projects.
AI-written summary · about
chapters (15)
- 0:00Introduction and welcome
- 1:05Demo of parallel query running
- 3:37Why static sites matter
- 5:19The JAM tax and build trade-offs
- 6:21What is query running
- 8:49Query running challenges
- 9:33Parallel query running concept
- 11:16Underlying architecture changes
- 13:24Future possibilities with LMDB
- 14:29Performance improvements explained
- 15:34Gatsby’s speed and scale innovations
- 17:20Deferred static generation
- 18:02Real-world performance gains
- 19:24How to use parallel query running
- 20:27Closing and Q&A
