Menu
Here are the parameters I have set on the table:
And here is what I see for the capacity over time.
Why is it remaining at 25 write units? Shouldn't it go down to 5 write units (the minimum set)?
886
When the workload decreases, Application Auto Scaling decreases the throughput so that you don't pay for unused provisioned capacity. If you use the AWS Management Console to create a table or a global secondary index, DynamoDB auto scaling is enabled by default. You can modify your auto scaling settings at any time.
Provisioned Autoscaling It will respond fairly quickly to capacity increase, but will be very pessimistic when reducing capacity and will wait relatively long (15 minutes) before adjusting it downward — a reasonable tradeoff of availability over cost.
Modifying or disabling DynamoDB auto scaling settings To do this, go to the Additional settings tab for your table, and select Edit in the Read/write capacity section. For more information about these settings, see Enabling DynamoDB auto scaling on existing tables.
Auto scaling uses Amazon CloudWatch to monitor a table's read and write capacity metrics. To do so, it creates CloudWatch alarms that track consumed capacity. The upper threshold alarm is triggered when consumed reads or writes breach the target utilization percent for two consecutive minutes.
That's because of this note from AWS DynamoDB AutoScaling documentation:
Currently, Auto Scaling does not scale down your provisioned capacity if your table’s consumed capacity becomes zero. As a workaround, you can send requests to the table until Auto Scaling scales down to the minimum capacity, or change the policy to reduce the maximum provisioned capacity to be the same as the minimum provisioned capacity.
In your case, the consumed capacity went down to 0 between 8:00 to 10:00, so the provisioned capacity remained at 25.
54
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
