Faster builds
complete
J
Jaap Frolich
It would be great if the machines that run the app build are (optionally) larger instances so that builds are fast. Currently my docker image is taking 15m, would be great if the build time can be improved.
I'd be willing to pay for faster builds where I can configure the instance size.
Log In
Activity Feed
Sort by
G
Gregg Luskin
This is still an issue for us. In our own infrastructure our builds are ~2m. In render the exact same project takes over 15m to build and another few minutes to deploy. This is a major blocker for us moving more production services to Render. Anurag Goel We are paying for premier build pipelines but it's still far too slow. Any recommendations?
Anurag Goel
G
Guillaume Simard
Anurag Goel Dead link
Anurag Goel
Guillaume Simard fixed.
a
adihanifsdr
Anurag Goel would be great if non-team user can see the pricing for Starter and Performance. I cannot find it anywhere the additional pricing since I'm not team user
Anurag Goel
complete
k
kyle
Anurag Goel: How can I scale up my build resources? Is this just a general improvement in build times or how can I opt in?
Anurag Goel
kyle: we will introduce a build plan with more CPU and memory later this year.
k
kyle
Anurag Goel: The option to build docker images outside of render would also satisfy our needs FWIW.
Anurag Goel
kyle: that feature is already in progress; it should launch in early access over the next few weeks.
Anurag Goel
This has been done across the board.
M
Matt Stewart
This is a CD bottleneck for my Elixir service that is really causing frustrations on my team. We had much longer than expected downtime due to how long it took to get a critical bug fix out. A few options:
- Implement a manual caching mechanism such as CircleCI's (https://circleci.com/docs/2.0/caching/). This would allow the super long steps of installing and building dependencies to be cached.
- Allow defining a separate tier for builds. We had an Elixir dependency that required a lot of memory for building. Webpack is CPU bound.
J
Jaap Frolich
Indeed would be great to be able to pay for this. Would good to be able to select build and deploy instance size.
K
Kai Marshland
Anurag Goel this is a feature I would be willing to pay for. Currently deploys take 8-12 minutes. At my company's current stage, we would pay $5-$10/month to get it down to 2 minutes. Happy to chat over DMs about why this is valuable to me
K
Kai Marshland
My analysis of why deploys take so long:
- ~15% of it is spent downloading the cache. Could be gotten rid of by having a dedicated build server that has everything pre-downloaded (which I'd be willing to pay for at the same pricing structure as for web servers)
- ~60% of it is spent pre-compiling things with webpack. Doesn't seem to take nearly as long on my local machine, due either to better caching or more compute, probably both
- ~15% is internal render things, probably not optimizable further
- Remaining 10% is booting, other tasks, etc. Some of these are parallelizable
r
render_k9tmadbsncix4
Do builds get faster when using the larger service plans?