Re:Why we moved from AWS RDS to Postgres in Kubernetes
by aeyes on Monday September 26, 2022 @08:58PM
(#32990539)
I would advise that you try to fit the working set into memory before spending on provisioned IOPS. Reading a lot of data from network storage constantly should be avoided as much as possible, having more IOPS doesn't necessarily improve read latency.
Re:Why we moved from AWS RDS to Postgres in Kubernetes
by brazzledazzle on Monday September 26, 2022 @07:25PM
(#32989945)
Provisioned IOPS is much more expensive though, so make sure you really need it. If you use general IOPS you can monitor your burst balance. You can always start with general and then move to provisioned when you need it too.
Re:Why we moved from AWS RDS to Postgres in Kubernetes
by xwowsersx on Monday September 26, 2022 @10:23PM
(#32990976)
Thanks. If I'm reading this https://ibb.co/bNGmrCB correctly, it seems like we have plenty burst balance. Does this seem to indicate that provisioned IOPS is unlikely to help us here?
Re:Why we moved from AWS RDS to Postgres in Kubernetes
by brazzledazzle on Wednesday September 28, 2022 @02:33PM
(#33011506)
Yeah you're looking good though I would recommend adding a CloudWatch alert to make sure it doesn't sneak up on you. IIRC in general provisioned IOPS can help with other performance attributes like throughput so I would look at the differences documented by AWS and then take a look at all of the relevant metrics to be certain.
General storage IOPS is governed by your provisioned storage size. You can again get much more consistent performance by using provisioned IOPS.
Feel free to email me if you want to chat through things specific to your env - email is in my about: