Hi, I'd like to understand if there is some kind of optimization or cache that can be added / implemented into the build process of a large Astro-powered blog. We have a blog with over 400 articles, the build process takes around 40 minutes between building the pages and optimizing the images and we're running it on a Github action worker.
As of now, Github is terminating our process because it's taking too much time/resources. I'd like to understand if there is a possibility to cache part of the process (like the installation of dependencies ,which I've already implemented) to reduce build times. Specially considering that 99% of the blog is not updated on every build, I feel like this process could be a lot faster.
#Caching and Optimizing build process of large sites
balmy epoch
willow pike
I don't believe there's a way to cache built pages, but if you're using @astrojs/image for optimisation, it does have a caching option which you could add to your list of cached resources.
https://docs.astro.build/en/guides/integrations-guide/image/#configcachedir
If you're using another optimisation solution, it would depend on that dependency's caching options
balmy epoch
I can look into that
but definitely the biggest chunk of time is spent building pages
signal gazelle
I'm also very curious about skipping pages that haven't been updated. My blog is built with 11ty, and I'm toying with switching to Astro, but the build times on 11ty are much faster than what I see people getting with Astro, so I've stuck with 11ty for now. I'd love to see an --incremental mode like 11ty has.