Reddit
reddit.com › r/aws › introducing scaling to 0 capacity with amazon aurora serverless v2
r/aws on Reddit: Introducing scaling to 0 capacity with Amazon Aurora Serverless v2
November 20, 2024 - Are you sure you're not confusing Serverless v1 with Serverless v2? V1 did scale to 0, V2 not until now (afaik). ... And v2 scales can happen in 15 seconds max. V1 took minutes to scale up or down..
AWS
aws.amazon.com › blogs › database › introducing-scaling-to-0-capacity-with-amazon-aurora-serverless-v2
Introducing scaling to 0 capacity with Amazon Aurora Serverless v2 | Amazon Web Services
November 20, 2024 - Amazon Aurora Serverless v2 now supports scaling capacity down to 0 ACUs, enabling you to optimize costs during periods of database inactivity. Aurora Serverless is an on-demand, auto scaling configuration of Aurora that automatically adjusts ...
Videos
Aurora Serverless v2: Automatic Database Scaling - AWS
48:36
AWS re:Invent 2021 - Instant and fine-grained scaling with Amazon ...
06:40
Aurora Serverless v2 is now.... SERVERLESS! (kind of) - YouTube
Aurora Serverless V2: Simplify Database Management - AWS
03:53
12. AWS RDS Aurora Serverless - Querying Aurora Serverless using ...
19:35
AWS re:Invent 2024 - Serverless scaling with Amazon Aurora PostgreSQL ...
Amazon Web Services
docs.aws.amazon.com › amazon rds › user guide for aurora › using aurora serverless v2 › how aurora serverless v2 works
How Aurora Serverless v2 works - Amazon Aurora
In recent Aurora MySQL and Aurora PostgreSQL versions, Aurora Serverless v2 writers and readers can scale all the way down to zero ACUs. We refer to this capability as automatic pause and resume, or auto-pause. You can choose whether to allow this behavior by specifying a zero or nonzero value ...
DEV Community
dev.to › aws-heroes › does-scale-to-zero-redefine-auroras-serverlessness-5hf7
Does Scale-to-Zero Redefine Aurora’s ‘Serverlessness’? - DEV Community
November 25, 2024 - Amazon Aurora Serverless v2 now supports scale-to-zero, allowing you to stop paying for your database when it isn't in use.
AWS
aws.amazon.com › about-aws › whats-new › 2024 › 11 › amazon-aurora-serverless-v2-scaling-zero-capacity
Amazon Aurora Serverless v2 supports scaling to zero capacity - AWS
Amazon Aurora Serverless v2 now supports scaling to 0 Aurora Capacity Units (ACUs). This launch enables the database to automatically pause after a period of inactivity based on database connections. When the first connection is requested, the database will automatically resume and scale to ...
Amazon Web Services
docs.aws.amazon.com › amazon rds › user guide for aurora › using aurora serverless v2 › performance and scaling for aurora serverless v2
Performance and scaling for Aurora Serverless v2 - Amazon Aurora
It's tempting to always choose ... smallest capacity when it's completely idle, while remaining active. You can also enable automatic pause behavior by specifying a minimum capacity of 0 ACUs, as explained in Scaling to Zero ......
GitHub
github.com › hashicorp › terraform-provider-aws › issues › 40226
[Enhancement]: Support scaling to zero capacity for aurora serverless v2 instance · Issue #40226 · hashicorp/terraform-provider-aws
November 21, 2024 - Amazon Aurora Serverless v2 now supports scaling capacity down to 0 ACUs, enabling you to optimize costs during periods of database inactivity. Aurora Serverless is an on-demand, auto scaling configuration of Aurora that automatically adjusts ...
Published Nov 21, 2024
Neon
neon.com › blog › aurora-serverless-v2-scales-to-zero-now-what
Aurora Serverless v2 Scales to Zero: Now, What? - Neon
December 24, 2024 - Aurora Serverless v2 clusters can now scale down to 0 ACUs during idle periods · Clusters will autopause entirely when no connections are active · Clusters will wake up automatically in 15 seconds when traffic returns · For Aurora Postgres, ...
DEV Community
dev.to › sudo_anuj › scaling-to-zero-with-amazon-aurora-serverless-v2-553n
Scaling to Zero with Amazon Aurora Serverless v2 - DEV Community
December 16, 2024 - The new version v2 of Amazon Aurora Serverless has made improvements in providing scaling support down to zero Aurora Capacity Units (ACUs). This is useful to save cost database is not in use.
Amazon Web Services
docs.aws.amazon.com › amazon rds › user guide for aurora › using aurora serverless v2 › scaling to zero acus with automatic pause and resume for aurora serverless v2
Scaling to Zero ACUs with automatic pause and resume for Aurora Serverless v2 - Amazon Aurora
You can specify that Aurora Serverless v2 DB instances scale down to zero ACUs and automatically pause, if they don't have any connections initiated by user activity within a specified time period. You do so by specifying a minimum ACU value of zero for your DB cluster.
InfoQ
infoq.com › news › 2024 › 12 › aurora-serverless-zero-capacity
Aurora Serverless v2 Adds Zero-Capacity Scaling for True Serverless - InfoQ
December 1, 2024 - Amazon Aurora Serverless v2 has recently announced that it now supports scaling to zero capacity, enabling the database to automatically pause after a period of inactivity based on database connections.
DEV Community
dev.to › aws-builders › aurora-serverless-v2-scales-to-zero-but-how-fast-49md
Aurora Serverless v2 scales to zero.. but how fast? - DEV Community
December 9, 2024 - During Pre:Invent season, AWS announced that Aurora Serverless v2 now scales down to zero, leaving no cost (except storage costs) to the customer.
Reddit
reddit.com › r/aws › experiences with aurora serverless v2?
r/aws on Reddit: Experiences with Aurora Serverless v2?
September 2, 2024 -
Hi all,
I've been reading some older threads about using Serverless v2 and see a lot of mentions of DBs never idling at 0.5.
I'm looking to migrate a whole bunch of Wordpress MySQL DBs and was thinking about migrating to Aurora to save on costs, by combining multiple DBs in one instance, as most of them, especially the Test and Staging DBs, are almost never used.
However seeing this has me worried, as any cost savings would be diminished immediately if the clusters wouldn't idle at .5 ACU.
What are your experiences with Serverless? Happy to hear them, especially in relation to Wordpress DBs!
Any other suggestions RE WP DBs are welcome too!
Top answer 1 of 11
15
My experience is that is performs poorly in absolute terms compared to similarly sized provisioned instances and that its like 10x worse perf/$. Its fine for something that has near zero load 2/3 of the time.
2 of 11
10
Pasting something I wrote elsewhere. I've been trying Aurora Serverless v2 PostgreSQL on a project and the results are pretty surprising. We were using db.t4g.medium (2 vCPUs and 4GB RAM) instances before and switched to 2 ACUs (according to the docs this gives you 4GB RAM and "corresponding CPU, and network"). The word corresponding is doing a lot of heavy lifting in that sentence We have a writer and a reader instance as it's a production system. If you set the failover priority of the reader to tier 2 or higher then the reader is supposed to scale down independently of the writer rather than remaining at the same ACU. We want this as the writer is never busy and if it does failover we're happy to wait for reader to scale up. See https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2-administration.html#aurora-serverless-v2-choosing-promotion-tier The result we saw was that post the switch the average CPU went from ~ 15% to ~ 35% and maximum CPU went from ~ 15% to 100% and the writer and reader were both scaled up to 2 ACUs. Opened a ticket with AWS to say "wtf" as I expected the reader to be sitting at 0.5 ACUs as it does nothing and CPU to be broadly what it was previously. AWS said that for the reader "From the Performance insights, I don't see any SQL queries waiting on CPU but I do see SQL queries running on the instance that are consuming CPU. From enhanced monitoring, I see that most of the CPU usage is consumed by RDS processes running within the instance. This also includes the backend Aurora processes and the processes needed for data replication." That seems pretty off as the writer is not busy at all so I can't fathom why the reader is doing much at all. I also queried why 2 ACUs wasn't broadly equivalent to a db.t4g.medium and support came back with: There is no direct relationship or correlation between ACU and vCPU, only that "Each ACU is a combination of approximately 2 gibibytes (GiB) of memory, corresponding CPU, and network. Please note, we do not have any exact figures regarding how many vCPU each ACU has, however, based on my testing of Aurora Serverless v2 and based on estimated vCPUs from performance insights, I can provide you with a rough estimate of vCPU & memory per ACU: 2 ACU - 1 vCPU (4 GiB RAM) 4 ACU - 1 vCPU (8 GiB RAM) 8 ACU - 2 vCPU (16 GiB RAM) 16 ACU - 4 vCPU (32 GiB RAM) 32 ACU - 8 vCPU (64 GiB RAM) 64 ACU - 16 vCPU (122 GiB RAM) 128 ACU - 32 vCPU (256 GiB RAM) Prior to changing to serverless config, you were using db.t4g.medium instance type which has 2vCPUs and 4GB memory [1] Based on your current configuration, with 2 ACUs as max capacity, you are getting only 1vCPU and 4GB RAM and hence the CPU usage is high. To get 2 vCPUs, you would need to configure at least 8 ACUs. Please change the max capacity of the cluster accordingly and verify if it addresses the CPU usage issue. An ACU costs $0.12 per ACU-hour so if I follow AWS' guidance in order to get 2 vCPUs I'm going to need to pay:- 0.12*8*720*2 = $1382.40 versus the cost for a db.t4g.medium $59.8600 x 2 = $119.72 This all seems utterly bonkers.
AWS re:Post
repost.aws › questions › QUifVVAoF5R9y_DsFX33IaSQ › aurora-serverless-v2-0-capacity-scaling
Aurora Serverless v2 0 Capacity Scaling | AWS re:Post
December 28, 2023 - Serverless v1 vs. v2 · To reduce the cost of the admin instance, I'm using Serverless v1 because it can scale down to 0 capacity when the admin instance is not running. However, according to the documentation, Serverless v2 has a minimum capacity ...
Hacker News
news.ycombinator.com › item
Aurora Serverless v2 doesn't scale to zero, though. Minimum capacity costs $43/m... | Hacker News
May 25, 2022 - It doubles the cost of V1 and they have the gall to say: · Oh, why thank you AWS, how kind of you. I can go to 0.5? That doesn't matter at all, the price is the save as 1 ACU on V1
Aws-news
aws-news.com › article › 01934ba8-5d45-a899-6545-8a62ab10609b
Amazon Aurora Serverless v2 supports scaling to zero capacity
Amazon Aurora Serverless v2 now supports scaling to zero capacity (0 ACUs), allowing databases to automatically pause during inactivity and resume when needed,...
Reddit
reddit.com › r/aws › no, aws, aurora serverless v2 is not serverless
r/aws on Reddit: No, AWS, Aurora Serverless v2 Is Not Serverless
June 20, 2022 - You don't need to specifically ... as that is with aurora rds. Serverless means you don't need to manage servers (services), only defining capacity, not that it can run at zero....
Last Week in AWS
lastweekinaws.com › home › blog › no, aws, aurora serverless v2 is not serverless
No, AWS, Aurora Serverless v2 Is Not Serverless - Last Week in AWS Blog
February 5, 2025 - Amazon Aurora Serverless v2 never scales to zero or suspends itself — so it's not fulfilling the serverless promise of pay-as-you-go pricing.
Amazon Web Services
docs.aws.amazon.com › amazon rds › user guide for aurora › using aurora serverless v2 › managing aurora serverless v2 db clusters
Managing Aurora Serverless v2 DB clusters - Amazon Aurora
For the auto-pause and resume capability that's enabled by setting the minimum capacity to 0 ACUs, see Scaling to Zero ACUs with automatic pause and resume for Aurora Serverless v2. For more information on making sure that your Aurora Serverless v2 DB clusters can scale up to 256 ACUs, see Upgrading your Aurora Serverless v2 DB cluster to allow scaling to 256 ACUs.
Top answer 1 of 6
2
I had to turn off the AI monitoring on the DB. Then restart the instance. This then started the db at the minimum.
2 of 6
0
I can confirm this behaviour but as yet can't explain it. We have three databases running, all with the same schema and with different ACU limits set. Our production and staging databases insist at near flatlines close to the max capacity allowed whilst one other behaves as we would expect and only shows an upscale when we actually send it load.
We have tried rebooting the instances but they immediately scale up and do not appear willing to scale down.
We have full support with AWS so will raise a ticket with them and should report back here if we get an explanation/solution