Slow deploy times

[jamietanna]

I’ve been seeing very slow deploy times with my site - www-jvt-me is the site ID.

I’ve been seeing consistently > 4-5 minute deploy times after the site has built and I was wondering if there was anything that could help, given this is slowing me publishing things, as well as maybe incurring further cost?

[perry]

hi there, could you link us to or paste a build log please? i’d like to see where the slowdown is happening.

given that we are on a globally shared build network, you will definitely see slower deploy times during peak hours.

you might check these articles:

[Support Guide] How can I optimize my Netlify build time?

updated in September 2021 If you are interested in learning more about how our bots approach building sites, these three articles are a great place to start: How our Build Bots build sites The last major upgrade to our build environment and perhaps least-loved but most useful, how to debug your builds So you might think, it’s great that Netlify builds every commit from my repos…but isn’t that a bit wasteful? The answer is, it depends, but we can at least give you some best practices …

[Support Guide] How long should Netlify builds take?

updated in November 2021 The only universal answer to this is: it varies. More detail would probably be helpful, right? Below we explain which factors affect the lengths of builds on Netlify One key factor is the site itself. Larger sites will take longer to build than smaller ones, and things like images and video can impact this (if those assets need to be downloaded or processed during build). Another factor is the static site generator (SSG) being used (if any). The perform…

Post processing and deployment taking a long time

hey there, that is a long post processing time, indeed! Do you have a lot of assets that are being optimized? Or a massive form? i can say that it is very likely that your site download is getting stuck due to the site size - that functionality works awesome for small sites, and is somewhat unreliable for large ones, which, hopefully, we will fix at some point, but that clearly isn’t your main issue - your main issue is site builds! here is some maybe helpful info: if you are…

[jamietanna]

Sure thing https://app.netlify.com/teams/jamietanna/builds/600b1b443a18d50008acb1e4

[luke]

Hi, @jamietanna. There are 24,263 files in that deploy. Our forms processor examines all of those files which are HTML for the presence of <form> tags. Your site isn’t using forms so disabling that post-processing would likely greatly improve the post-processing time by no longer examining each file for forms.

There are instructions about how to do so here:

Form detection

If this doesn’t improve the post-processing time or if there are other questions, please let us know.

[jamietanna]

Thanks that appears to have done it I’m sorry I didn’t reach out earlier to work out what was going wrong

[RoeckieTM]

Hi @luke , after a new (incremental) build only changing a couple of files, would the form processing - when active - still examine all files? Just wondering.

[perry]

to the best of my knowledge, it would only re-process forms that had been added or changed - we detect those by scanning through your site for html tags indicating forms are present as part of our build process.