Does Pro make Pages builds faster?
We're struggling with the pages build speeds (for both preview and production builds) and debating whether to upgrade. Would only make sense for us if the "Queued" times are drastically reduced - is this the case with the paid plan?
8 Replies
The "Queued" status comes from the limitation of only having one build running at the same time on the free plan. With a Pro plan, you can have 5 concurrent builds, meaning 5 builds can be running at the same time. A sixth build will be "Queued" until one of the five already running builds finishes. Same for the Business plan which will give you 20 concurrent builds.
See https://pages.cloudflare.com/#pricing
Cloudflare Pages
Build your next application with Cloudflare Pages
Thanks Rhaegal. I just checked and turns out we're actually on the Pro plan, but we've just outgrown the 5 concurrent builds. Is there any way to manually bump our number of concurrent builds up to 10 to try it out before we (eventually) upgrade to Business?
and are both preview and production builds in the same queue? I ask because in theory, if so, if we turn off preview builds, would it make all the production builds go faster?
Oh actually I see the product is "Workers Paid" - is that separate from Pages Pro?
For Pages concurrent builds are counted per account. So they are for all builds across all projects and environments (preview and prod) in your account. https://developers.cloudflare.com/pages/platform/limits/#builds
Imo the pricing for Pages is a bit confusing.
If you have a website (a zone, or domain) in your Cloudflare account on a paid plan (these: https://www.cloudflare.com/plans/), it will unlock the higher limits on Pages for that account.
On the other hand you have Workers Paid ($5 Dollar + usage) which is decoupled from Pages & the paid plans mentioned above.
Workers Paid will give you six concurrent Worker builds (https://developers.cloudflare.com/workers/ci-cd/builds/limits-and-pricing/), but won't give you extra concurrent Builds in Pages.
It might be a good idea to check if you can migrate your Project from Pages to Workers (check here: https://developers.cloudflare.com/workers/static-assets/migration-guides/migrate-from-pages/)
This is the cheaper option. Workers can do the same (and more than) Pages and Cloudflare has stated that Workers will receive the focus of Cloudflare's development efforts going forwards.
Cloudflare Docs
Limits
Below are limits observed by the Cloudflare Free plan. For more details on removing these limits, refer to the Cloudflare plans page.
Ah okay that's helpful, so if I disable preview branch builds, in theory that should unclog the queue?

This will make it so that only commits to your production branch will be built and deployed. However, it'll still be the case that only one build can be running at a time.
True, but if before we had a production build, then 3 preview builds, and then another production build, it would have had to go 1-by-1 through those 3 preview builds before being able to build the production one correct?
By setting it to none, I just want to confirm it won't waste any time with the 3 preview builds
And thank you for the notes on switching to workers, I'll investigate the feasibility of that for my team
That is correct.
It will then just do the two production builds one after the other in the order they were created.
The preview builds just won't show up. They'll be gone.
Great - thank you! Appreciate the help