Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Large sites ~200k pages, incremental builds? #9083
We have a large site of about 200k pages and we don't want to have to rebuild the whole site every time we make a change and deploy.
A lot of our pages are set pages that pull in a lot of data and take a while to build but they won't change often.
We could just build them in a separate Gatsby project to the rest of our site. Having two Gatsby projects
Ideally we want to build those "set-pages" once, and then each time we update our gatbsy project we don't have to rebuild them.
Is there a good/recommended way we can selectively rebuild just parts of the site on deploy? We would prefer not to rebuild the whole site on every deployment.
Currently our best thinking is to split the
Have read a lot of closed issues on this I can see that the faster build times in Gatsby v2 help alleviate this issue for a lot of sites, but 200k pages is where we are and we're wondering if build times will be manageable as we increase scale. Mainly we don't want small blog updates having to rebuild the entire
At this moment it's not possible to do incremental builds. It's definitely something we will want to support but it's not trivial to do as currently all code expects that everything is built when running
Here's open issue for that #5002, so I'll close this to not have multiple open duplicate issues
2 similar comments
@fenchi thanks for showing your support, but if you can just react to the original issue with an emoji, that's a much more helpful way of showing your support. Thanks!
(For full context, we can then sort issues by # of reactions, which can be a helpful signal to help us prioritize)