Skip to main content
Open console

Scaling

Resize a machine for good, let autoscale move it when it is busy, or upscale it for seven days, and how each is billed.

5 min read

A machine is bought at a size, and the contract carries that size. There are three ways to give it more:

For Billed
Resize a size that should stay the new size, at its ordinary price, from the moment it starts
Autoscale (beta) traffic you cannot predict by the day, only while it is bigger
Upscale for seven days a week you know will be busy by the day, for the week

Autoscale and upscales are for production machines on cloud native compute (the ones whose disk is not part of their size, see Machines) on a dedicated plan. Both are on the Autoscale card of the project's Commercial terms. A day at a bigger size costs more than the same size bought for good; the price list has the premium.

Resize for good

Use Resize on the machine, on the environment's Resources tab or the machines page. It works on any machine in any environment.

  • Bigger on every machine. Smaller only on cloud native compute: see which way a machine can move.
  • The sizes sold where the machine is. The list is the configurator's, for the machine's datacentre. For production it holds only what is in stock there now. The current size stays in the list, so it can be kept.
  • Refusal. A move the provider has no room for is refused before anything stops, with the limit it would pass.
  • The contract moves with it. The new size is billed from the moment the machine starts on it, for the rest of the period, at its ordinary price. A smaller one is credited the same way.
  • Machines doing the same job move together: the web servers behind a balancer, one at a time.
  • It is downtime for a few minutes on most machines. Growing a Cloud Native machine is often done while it runs. The resize dialog says which before you confirm: see it is downtime.

Keeping the size autoscale or an upscale chose. Open Resize and choose the size the machine is on. Nothing is resized: the size goes on the contract at its ordinary price, and the upscale ends. Choosing any other size resizes the machine and ends the upscale too. Either way, that day is billed as an autoscaled day.

Autoscale

Autoscale is in beta. It works and is billed as described here. Like every beta feature, it is not covered by the uptime commitment.

Switch it on in the configurator, under Configure project, or later on the Autoscale card. For each machine, choose the largest size it may go to. Where no machine may, the card says why.

  • Up: when CPU stays above 80% for 15 minutes, the machine moves one size up, to the next size with more cores, as far as the size you chose. A reading or two under the line in that time does not start the count again. It stays on the same kind of cores, shared or dedicated, where its datacentre sells a bigger size of that kind. It moves to the other kind only where it does not.
  • Down: after at least a day on the bigger size, once CPU has stayed below 40% for an hour, it comes back one size. It never goes below the size you bought. A database steps down in the project's maintenance window.
  • Which machines: production machines only, and only those that serve a page: the all-in-one machine, the web servers, the database and the load balancer. Several web servers resize one after another, so behind a load balancer the site stays up.

Switching it on costs nothing. Only the time a machine spends bigger is billed.

Upscale for seven days

On the Autoscale card, choose a bigger size for any production machine: web servers, the database, the cache, search, a queue, a worker, an extra. It moves there at once and goes back to the size you bought seven days later. A bigger size can be more cores or, where that is what the machine needs, more memory alone.

A machine whose restart loses something comes back down in the project's maintenance window: the database, a cache (which starts empty), Varnish, a search index or a queue (away for about a minute), and the files machine. The card says so for each.

Choose no upscale to end one early: the machine goes back straight away.

While an upscale lasts, autoscale, if it is on, may take the machine higher but never below the upscaled size.

Autoscale and upscales, either way

  • Only CPU and memory change. The disk stays the size it is.
  • Downtime. Scaling down restarts the machine, for about a minute. Scaling up restarts some machines and not others, also for about a minute. Support can tell you which yours are.
  • You are told each time a machine is moved, when an upscale ends, and when a busy machine wanted to go past the size you allowed.
  • Billed by the day, on your next invoice. Each day, or part of a day, a machine spends above the size you bought is charged at a premium over that size's daily price, in place of the size you bought. The price list has the rate, before tax; VAT is added where you pay it, as on everything else.
  • Not on the shared plan, and not during a free trial.

Next

  • Machines: the two kinds, and which way each can move
  • Monitoring: what the machines are doing
Need a hand?

Open a ticket from Support in the console. We answer on the ticket.

Open the console How support works