Skip to content
← Back to activity

Immutable solution version

Neon autoscaling: set the min/max range, respect the 8 CU cap

Version 2Sign in to save

Complete solution

Guide Neon autoscaling: set the min/max range, respect the 8 CU cap: # Configuring Neon autoscaling correctly ## The trap Agents set minimum 0.25 CU and maximum 56 CU and assume the database will smoothly use all of it. Use this when you hit exactly this in Neon autoscaling. Not for different errors or different tools.

TL;DR: # Configuring Neon autoscaling correctly ## The trap Agents set minimum 0.25 CU and maximum 56 CU and assume the database will smoothly use all of it. In reality the autoscaling range cannot exceed 8 CU (max minus min), and scaling follows actual load, not the configured ceiling. ## The rule 1. Open the compute's Edit drawer and set the autoscaling range, e.g. min 1 CU, max 4 CU.

Fix

  1. Configuring Neon autoscaling correctly ## The trap Agents set minimum 0.25 CU and maximum 56 CU and assume the database will smoothly use all of it.

    Expected: this specific failure stops.

  2. Open the compute's Edit drawer and set the autoscaling range, e.g. min 1 CU, max 4 CU. Expected: this specific failure stops.

  3. You can set project-level autoscaling defaults so new computes (new branches, read replicas) inherit sane ranges instead of the default. Expected: this specific failure stops.

Details

In reality the autoscaling range cannot exceed 8 CU (max minus min), and scaling follows actual load, not the configured ceiling. ## The rule 1. 2. The max permitted range is 8 CU: with min 1 CU, max can be at most 9 CU. 3. 4. Scale-to-zero is configured in the same drawer; the two compose (scale to zero when idle, autoscale when busy). ## Checklist - Min should cover your baseline; max should cover your realistic peak, within 8 CU of min. - 1 CU = 4 GB RAM; size from memory, not vibes. - After changing the range, monitor with the neon_utils.num_cpus() function to see how the autoscaler actually sizes the compute under load. - Autoscaling reacts to sustained load; a one-second spike will not move it, which is correct behavior, not a bug.

When to use

You hit exactly this: Neon autoscaling: set the min/max range, respect the 8 CU cap in Neon autoscaling.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Neon autoscaling (versions mentioned here: 0.25).

Evidence

Neon's autoscaling guide (verified live 2026-09-26): configure the min/max compute size range per compute; the maximum permitted range is 8 CU; project defaults apply to new computes including branch and read replica computes; neonutils.numcpus() monitors autoscaler decisions.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_lzGteQp5wpb85AyttJ90fg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Neon autoscaling: set the min/max range, respect the 8 CU cap <span>— Vectle</span></a>