Thanks! We stuck with plain EC2. RDS has a limit of 80,000 provisioned IOPS and our read replicas on Postgres 9.6 would regularly hit near double that during peak
Did you consider lowering those IOPS with application-level and/or distributed in-memory cache and/or pub-sub notifications to let your app nodes not pester the database so much? Reasonably performant hand-written SQL (no ORM!), review of query plans, maybe shift the hot path into functions/procs?
Believe it or not these numbers are actually from _after_ me and some others spent a few weeks cleaning up our heavier queries
Re:Our Journey to PostgreSQL 12
by throwdbaaway on Tuesday January 26, 2021 @01:56AM
(#25913274)
That's an impressive amount of IOPS. I have always been a EBS / pd-ssd guy, and mostly rely on memory to reduce the IOPS requirement. But as cloud providers typically charge a ridiculous amount of money for memory, a setup like yours with instance storage / local-ssd is an intriguing option.
That limit doesn’t apply to Aurora - did you consider that?
Apparently I'm living in the twilight zone because I have a vivid memory of reading the Aurora docs and seeing the same limit. Oh well, it's something to consider for the next upgrade.
Re:Our Journey to PostgreSQL 12
by 0xbadcafebee on Tuesday January 26, 2021 @12:06PM
(#25918295)
So.......... caching?
Did they migrate into Amazon RDS while doing this? For smaller projects I've stopped doing the self managed postgresql thing. The pricing is higher (75%?) for RDS for some use cases but can be worth it.
Going to try RDS Proxy next.