---
title: "Autoscaling"
description: "22 posts about Autoscaling, summarised, each linking to the original."
---

# Autoscaling
> 22 posts about Autoscaling, summarised, each linking to the original.

## Articles

### [Updating Scale](https://yomu.fyi/post/updating-scale.md)
- Company: [Fly.io](https://yomu.fyi/company/fly-io.md)
- Published: May 13, 2020
- Type: Announcement

Fly introduces a new scaling model and command set intended to simplify how applications distribute instances across regions and manage global load. Instead of assigning instance counts to a fixed regional list, the system uses a pool of allowed regions plus global minimum and maximum instance counts, with Standard and Balanced models determining placement. Standard distributes instances evenly through the minimum and adds demand-driven instances without relocating them, while Balanced can move instances from other regions once the maximum is reached to match regional demand. The new flyctl regions command manages the pool, and flyctl scale show, standard, balanced, set, and vm commands configure or inspect scaling mode, counts, and VM size. Regional allocation can still fall back to a nearby region when the selected region cannot create an instance.


### [Scaling Fly for All](https://yomu.fyi/post/scaling-fly-for-all.md)
- Company: [Fly.io](https://yomu.fyi/company/fly-io.md)
- Published: Mar 17, 2020
- Type: Announcement

Fly makes its scaling controls available to all users, allowing them to manage application instance counts across regions and choose virtual-machine sizes. The default plan places an application in one region, while Fly’s autopilot can add an instance when a connection limit of roughly 20–25 is reached and select its location. The new flyctl scale regions command reports or sets regions and per-region minimum counts; for example, ams=1 hkg=1 sjc=1 keeps at least one instance in each location, with weights influencing where new instances are preferred. Users can also run flyctl scale vm to apply a VM size to all current and future instances, triggering a new app version and redeployment. Available sizes range from micro-1x with 128 MB to cpu8mem8 with 8 GB, while the article notes that the system was later superseded.


[Newer posts](https://yomu.fyi/topic/autoscaling.md)