The following container & CPU threshold settings are available for configuration:

• Percentile: Determines the percentile for evaluating RAM and CPU usage.
• Minimum Container Count: Sets the lowest container count to which the service can be scaled down by Autoscaler.
• Maximum Container Count: Sets the highest container count to which the service can be scaled up to by Autoscaler.
• Scale Up Steps: Sets the amount of containers to add when autoscaling (ex: a value of 2 will go from 1->3->5). Container count will never exceed the configured maximum.
• Scale Down Steps: Sets the amount of containers to remove when autoscaling (ex: a value of 2 will go from 4->2->1). Container count will never exceed the configured minimum.
• Scale Down Threshold (CPU Usage): Specifies the percentage of the current CPU usage at which an up-scaling action is triggered.
• Scale Up Threshold (CPU Usage): Specifies the percentage of the current CPU usage at which a down-scaling action is triggered.

The following time-based settings are available for configuration:

• Metrics Lookback Time Interval: The duration in seconds for retrieving past performance metrics.
• Post Scale Up Cooldown: The waiting period in seconds after an automated scale-up before another scaling action can be considered.
• Post Scale Down Cooldown: A defined interval in seconds to pause after an automated scale-down, before evaluating the possibility of further scaling actions.
• Post Release Cooldown: The time in seconds to wait following any general scaling operation, allowing stabilization before considering additional scaling changes.

The following RAM & CPU Threshold settings are available for configuration:

• Percentile: Determines the percentile for evaluating RAM and CPU usage.
• Minimum Memory (MB): Sets the lowest memory limit to which the service can be scaled down by Autoscaler.
• Maximum Memory (MB): Defines the upper memory threshold, capping the maximum memory allocation possible through Autoscaler. If blank, the container can scale to the largest size available.
• Memory Scale Up Percentage: Specifies the percentage of the current memory limit at which the service’s memory usage triggers an up-scaling action.
• Memory Scale Down Percentage: Determines the percentage of the next lower memory limit that, when reached or exceeded by memory usage, initiates a down-scaling action.
• Memory Optimized Memory/CPU Ratio Threshold: Establishes the ratio of Memory (in GB) to CPU (in CPUs) at which values exceeding the threshold prompt a shift to an R (Memory Optimized) profile.
• Compute Optimized Memory/CPU Ratio Threshold: Sets the Memory-to-CPU ratio threshold, below which the service is transitioned to a C (Compute Optimized) profile.

The following time-based settings are available for configuration:

• Metrics Lookback Time Interval: The duration in seconds for retrieving past performance metrics.
• Post Scale Up Cooldown: The waiting period in seconds after an automated scale-up before another scaling action can be considered.
• Post Scale Down Cooldown: A defined interval in seconds to pause after an automated scale-down, before evaluating the possibility of further scaling actions.
• Post Release Cooldown: The time in seconds to wait following any general scaling operation, allowing stabilization before considering additional scaling changes.

See our guide here for How to scale apps and services

Contact Aptible Support to request access!