Autoscaling
complete
w
webservices
Scale out and scale in automatically based on a metric such as CPU utilization rate. Scale out should add a specified number of instances, run build and deploy, and then automatically add it to the cluster. Scale in should remove the instance from the cluster and destroy it.
Log In
Anurag Goel
complete
Autoscaling is now stable and available to all Render users! https://render.com/docs/scaling#autoscaling
Activity Feed
Sort by
T
Tushar Ranka
Anurag Goel are there plans to extend the autoscaling feature? As mentioned in this thread many times over, memory and CPU based scaling doesn't work in all cases. Having request queue based auto-scaling is needed for web services, so you can respond to bursts in traffic. The other options is to time-based scaling.
Could you please provide an update on this as I am finding the CPU and memory based auto-scaling not very useful, and I have to over-provision my service?
Anurag Goel
Tushar Ranka: Hi Tushar, our customers find CPU/memory based autoscaling is actually a better alternative to request-based autoscaling. The problem with request-based scaling is that it doesn't account for bottlenecks in the database. Increasing instances when the DB is overloaded is actually worse for performance.
Still, we do plan to allow scaling on custom metrics; I'd love to learn about your use case if our CPU/memory based scaling doesn't work for you in practice.
T
Tushar Ranka
Anurag Goel: My application is very I/O bound, calls other APIs. We really don't see major spikes in CPU or memory when we get extra traffic.
I have also seen time-based scaling with AWS that works well. It's not as "smart" but it works :)
M
Min Thurain Htun IT ONE
Tushar Ranka: I agree with time-based scaling.
j
jonathan
CPU and memory as the only metrics for auto-scaling is not ideal. :(
Options on heroku can use things like "time in request queue" (for web), or even custom metrics delivered by an end-point on your application (the latter makes just about anything possible).
I wonder if it would be possible to create API's to make third-party autoscaling possible, so they could potentially do more than you have done built-in.
Anurag Goel
complete
Autoscaling is now stable and available to all Render users! https://render.com/docs/scaling#autoscaling
S
Sai Krishna
It'd be incredibly useful to have autoscaling by memory for my nextjs app.
CPU utilisation is very minimal and memory usage remains fairly constant under 500mb and occasionally it goes upto 750mb. The app crashes if I use 1gb ram plan and just because of this, I'm on 2gb ram plan, paying excessively just for <10% of the scenario. Attaching a screenshot of the metrics.
A
Andy Chong
Adding Memory utilization will be great!
Anurag Goel
Andy Chong: how does your app's memory increase with load? A lot of memory-bound apps require
vertical
autoscaling, which is on our roadmap. We'd love to know more about workloads that can benefit from memory-based horizontal autoscaling.A
Andy Chong
Anurag Goel: Technically speaking, my RoR app is more memory-hungry than CPU, therefore CPU cannot really be a good trigger for autoscaling. But then I think being able to scale based on the requests queue time in the load balancer will be a better one for my case, as mention by yoran.
Anurag Goel
Autoscaling is now available in early access! Please see https://community.render.com/t/autoscaling-available-in-early-access/611 for details.
P
Peter Schröder
👍 nice! currently evaluating getrender and it looks great. not having an autoscaling is a major blocker though. if you have a beta-channel or something like this, i'd love to participate in a preview.
Anurag Goel
in progress
We're going to start out with horizontal autoscaling based on memory and CPU utilization targets. Stay tuned!
E
Emmanuel Amodu
Anurag Goel: For vertical scaling, taking a snapshot of the current service would make more sense for me, as sometimes we have temporary data (on sqlite) we would like to persist as the system scales up.
P
Peter Schröder
Anurag Goel: any ETA on the memory based targets? our web and worker instances are both memory bound and the current CPU utilization is not a good autoscaling metric. it would also be great to allow configuration of the number of upscale and downscale instances and the delay between scaling events. this will help us with bursts of usage that we regularly see in our app.
Anurag Goel
Peter Schröder: how does your app's memory increase with load? A lot of memory-bound apps require vertical autoscaling, which is on our roadmap. We'd love to know more about workloads that can benefit from memory-based horizontal autoscaling.
P
Peter Schröder
Anurag Goel: our workload mangles a lot of photos and is more io and memory bound when parts of the photos are loaded into memory. There is a low correlation to CPU. Horizontal autoscaling sounds promising as we see a lot workers dying when we reach a memory threshold in spikes.
Anurag Goel
Peter Schröder: memory based autoscaling will be available when we launch autoscaling publicly.
D
Daniel Meechan
Our team's considering switching to Render but not having autoscaling (either vertical or horizontal) is a blocker for us. Is this planned for 2020 or can we expect it to arrive later?
Anurag Goel
Daniel Meechan: horizontal autoscaling is definitely planned for this year; most likely this fall or sooner.
Anurag Goel
planned
Load More
→