Why we moved from AWS RDS to Postgres in Kubernetes

Re:Why we moved from AWS RDS to Postgres in Kubernetes by Nextgrid on Monday September 26, 2022 @03:43PM (#32987385)

You've got some spikes that could signify some large or unoptimized queries, but otherwise yes, the CPU doesn't look that hot.

I suggest upgrading to an instance type which gives you 32GB or more of memory. You'll get a bigger CPU along with it as well, but don't make the CPU your priority, it's not your main bottleneck at the moment.

[ Parent | on HN ]

Re:Why we moved from AWS RDS to Postgres in Kubernetes by xwowsersx on Monday September 26, 2022 @03:45PM (#32987415)

Makes sense, thank you. Sounds like M class is the way to go as other commenter suggested. Also, yes. There are many awful queries that I'm aware of and working to correct.

[ Parent | on HN ]

Re:Why we moved from AWS RDS to Postgres in Kubernetes by CodesInChaos on Tuesday September 27, 2022 @10:09AM (#32995428)

I'd look into Memory Optimized (R*) instances.

[ Parent | on HN ]

Re:Why we moved from AWS RDS to Postgres in Kubernetes by xwowsersx on Tuesday September 27, 2022 @06:21PM (#33001896)

Thank you. I think this makes a lot more sense actually. I can go to db.r6g.xlarge and double the memory to 32gb from the t3.xlarge I'm currently on for an additional ~$117/month vs getting to 32gb with the db.m5.2xlarge for $308 more per month. Also, looks like X2g among the memory optimized is the lowest price per GiB of RAM (for MySQL, MariaDB, and PostgreSQL). Thoughts on the X2g? The db.x2g.large, for example, doubles memory AND network performance (Gbps) vs current DB for less than $30 more per month. Does drop vCPU down to 2 from 4, which might not matter given where CPU utilization seems to spike to (~50% at peak) https://ibb.co/WsxN6D3

[ Parent | on HN ]