Ship faster with database branching workflows: Add prod-like data to your preview and local dev environments.

Changelog

The latest product updates from Neon

Faster cold starts in all regions

Neon's Autosuspend feature scales a compute instance to zero after a period of inactivity. A characteristic of this feature is a "cold start", which occurs when an idle compute is restarted to process requests. Recently, cold-start times have been improved through a variety of enhancements, outlined below:

  • Compute pools: Instead of starting computes from zero, requests for computes are now served from pools of pre-started compute instances.
  • Compute configuration optimization: Configuration changes at compute startup were eliminated where possible.
  • Caching of internal IP addresses: Internal IP addresses are now cached to avoid waits for internal DNS routing.
  • Concurrency improvements: Concurrency optimizations were applied to the compute startup process.
  • Code path optimization: Code paths frequently accessed during compute startup were optimized.

With these improvements, cold starts are faster in all supported regions. Cold starts in the US East (Ohio) — aws-us-east-2 region, where the Neon Control Plane is hosted, are the fastest at approximately 500 ms. Work is underway to deploy the Neon Control Plane regionally to enable the same millisecond startup times for projects in all regions. For more information about this effort, please check out the blog post from the Neon engineering team: Cold starts just got hot.

Please be aware that Neon Pro plan users can adjust or disable the Autosuspend setting, controlling when a compute scales to zero. Additionally, Neon's Autoscaling feature allows you to scale compute resources down to a fractional size during periods of low activity.

Back to all changelog posts