Hi, we have tried BETA of Autoscaling feature and we have some thoughts how to make it better. In its current setup its not really suitable for our production workloads. Here are some thoughts how to make it better:

1. Define separate scaling steps At them moment the scaling step is always 1. Going from M10 -> M20 which is not really suitable for burst loads where going one step up might not be enough. Same goes for rapid scaling down

Example:
Scale range = M10 - M50
Scale step up 4 = (M10 -> M50)
Scale step down 2 = (M50 -> M30 -> M10)

1. Define custom timescale
   It seems that current setup is to start scaling down after 72h, and then repeat every 24h.
   Our system can be scaled down much more rapidly, when our burst load goes away its done for a few days, we know we can start scaling down after 12h and repeat every 6h.
   With current setup it will take 6 days to scale down from M50 -> M10.

2. Define custom scaling metrics and thresholds
   It seems that current system is not taking N of connected clients as a scaling metric.

3. when connecting from cloud functions its easy to have a lot of connections which are not draining CPU or memory, when we are scaled down to M10 that limit is only 200

4. additionally we would like to scale up when our CPU limit is >50% which is not possible ATM

Nice to have:
4. Time based scaling events
scale up/down at specified time & day, useful for scaling up DEV/Research environments within working hours

PS: writing a long post in this form is terrible

Hi, Currently there is no option to initiate auto scaling during heavy workload/ requests comes and the cpu/ memory utilization is 75% for the even within
- 5 minutes
- 15 minutes
- 30 minutes
- 45 minutes

The system has to wait for 1 hour to autoscale to next tier.This one of the concerns for the heavy workload applications.

Idea:

Add a custom duration option as

• minutes also while monitoring the cpu / memory utilization

Example : When a CPU / Memory utilization is above 75% for the past 15 minutes , move the cluster to the next tier when auto scaling is enabled .This can also be implemented as a dropdown option ( 5min, 15 min, 30 min, 45 min, 1 hour, 3 hours , 6 hours etc)

Auto scaling is a great feature and as of now if any cluster gets scaled up/down an alert email will be sent to the email list provided in the Access Manager . However , in the activity feed we are unable to see them .

Use case:

For instance if an user want to know how many times the Auto-scaling happened and at what specified time that event occurred on a particular cluster there is no definitive answer as the only way is to check the email alerts that's been received.

It would be great if there is a way that " Auto-scaling" events can be incorporated into Activity feed

Case #00731969

Is it possible to tweak the scale up settings so that my clusters scale up faster than they do today?

I think it is best to analyze my clusters and figure out how long they are staying above 70% and then average it out, and if equal to or greater than that average, I would like my clusters to scale up.

Once scaled up, I want it to remain scaled up for the next ~2 hours at least and only scale down if usage gets really small enough for it to justify scale down.

Right now, the auto scale-up is not scaling up effectively when needed.

We need to scale up well below the 1 hour time period. Maybe scale up if it uses > 75% for ~10 minutes, and remain scaled up for two hours until usage goes down or something like that.

Maybe we need to have profiles for "Aggressive Scaleup", "Auto", "Low", etc...

Currently autoscaling is predefined with conditions like
scale up:
The Average CPU Utilization has exceeded 75% for the past hour.
The Memory Utilization has exceeded 75% for the past hour.
scale down:
The average CPU Utilization and Memory Utilization over the past 24 hours is below 50%.
The cluster hasn't been scaled down (manually or automatically) in the past 24 hours.

Following changes will save more resources and money:

-This 24 hours time for scale down should be made flexible/adjustable to suit customers requirement.
-One hour time to scale up should be adjustable to scale up faster. This may need for some critical application.

First one will save more valuable resource and money while db will be running in optimized condition
Second one will reduce critical application failure by adjusting scale up time