Finally a pro-active way to put a hard limit your spend on IO in Aurora without impacting your query performance too much. Previously you could only watch your query plans and monitor the IO metrics, and hope for the best.
Bundling io into the cost. Interesting/smart idea.
I am curious how much pay-per-use aspect is lost here, if any. We have 5 hours of huge peak usage a day. Will this still scale up & down through our usage elegantly still? I don't quite get what the model is here, don't see quite what to expect with system & io being bundled together.
The guidance seems good though. If io is above x%, try it. You can turn it off anytime. Oh but you can only turn it on once every 30d for a db! That's an interesting twist. Preventing folks from turning it on only during their peak hours. For now.
2 comments
[ 3.0 ms ] story [ 17.5 ms ] threadI am curious how much pay-per-use aspect is lost here, if any. We have 5 hours of huge peak usage a day. Will this still scale up & down through our usage elegantly still? I don't quite get what the model is here, don't see quite what to expect with system & io being bundled together.
The guidance seems good though. If io is above x%, try it. You can turn it off anytime. Oh but you can only turn it on once every 30d for a db! That's an interesting twist. Preventing folks from turning it on only during their peak hours. For now.