Learn how Neon's autoscaling works - it estimates Postgres' working set size and keeps it in memory. Engineering post here

Changelog

The latest product updates from Neon

Safer project deletes

We've heard you. Where it might have felt just a little too easy to delete a project — along with its branches, databases, and roles — we've added a bit more friction to the process. You now have to type out the name of your project by hand before you can delete.

type project name to confirm delete

Local File Cache (LFC)-aware autoscaling

As we continue to mature our Autoscaling offering, we've rolled out LFC-aware autoscaling to all regions.

Alt text

One hour of real-time autoscaling from a selection of your databases.

The idea behind this feature is to improve performance by keeping your entire working set (a subset of frequently accessed or recently used data) in memory. We already recommend this in the docs, and we've now made it a native part of how autoscaling works: your compute now dynamically resizes to fit your working set within the LFC.

If you're not familiar with Neon's Local File Cache (LFC), you can learn more about it here: What is the Local File Cache?

Fixes & improvements
  • The authorization flow initiated by neonctl auth now asks for additional permissions. This update is part of the groundwork for the upcoming Early Access release for Organization accounts. Stay tuned!
  • We now dynamically set the maximum size of the LFC (Local File Cache) according to your compute's max vCPU. Previously, the max size was set to a static 100 GiB, which sometimes caused compute to run out of space in the LFC disk.
  • We've renamed our Free Tier to Free Plan everywhere: our website, our docs, and our console.
  • Fixed a mismatch between a selected timezone range (UTC) and the local timezone showing on different graphs on the Monitoring page, which sometimes caused misleading reports or missing data.
Back to all changelog posts