-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gatsby build slow (800 pages) #3790
Comments
We'll be doing a lot of optimizations to improve build performance in v2 and v3 of Gatsby but this is normal for now. |
Hi @KyleAMathews, do you have an idea on how much build performance will improve and what the expected timeline is for v2? What kind of improvements, something like incremental builds, so not all pages are rebuilt on every little change? Currently 15 minutes is unacceptable for us (netlify stops the build after 15 minutes and will only increase if we add another language + customer is a little frustrated that just a small change takes so long before they can see it appear on their website). So we're looking into different solutions, maybe rewrite to a SSR solution like Next.js. Any suggestion on this would be very much appreciated! |
Would also like to know about anticipated pagebuild improvements, specifically what there is to be improved [mine is slow with many fewer than 900 pages, but even with verbose enabled I don't see why]. SUPER loving Gatsby, and as this is my first post in this GH I felt I should say so. Great project, looking forward to learning through it. Thanks for the great work! |
Hey chaps — we merged a PR recently which speeds up builds AND reduces memory usage a lot #4555 v2 is getting close! Hopefully next week we'll get the first beta out + an upgrade guide. |
@KyleAMathews Is it really likely to have a usable beta of v2 next week? We plan to release our blog next week, but we're running into build issues as well. It currently takes ~30 minutes to build our blog (~4000+ pages + sitemaps, ~700 pages per language, 6 languages) on my macbook pro from 2014. It only works if I set There's also something wrong with either Contentful source plugin or |
What's the current status of this? We're considering a move to Gatsby, and have a site with ~1000 pages. If it's the wrong tool for the job, what should we be considering? |
@chrism2671 check out v2! With the memory reduction PR I linked to earlier + my "hulksmash" PR, builds in v2 are ~80% faster for larger sites. #6226 (comment) A 1000 page site should easily build in < 1 minute. |
Description
We build a website with gatsby (npm run build), the data comes from Contentful and it is build on Netlify. The website has around 800 pages. But it takes 15 minutes to build the site on Netlify and Netlify has a 15min limit. Locally it also takes 10 minutes to build the site, which seems a bit long or is it normal?
Deploy log can be found in the pdf
deploy_log_netlify.txt.pdf
Environment
Gatsby version: 1.9.149
Node.js version: v8.9.4
Operating System: OSX, Linux (Netlify)
File contents (if changed):
gatsby-config.js
:package.json
:gatsby-browser.js
: not changedgatsby-ssr.js
: not changedActual result
What happened.
Expected behavior
What should happen?
Steps to reproduce
1.
2.
3.
...
The text was updated successfully, but these errors were encountered: