Show HN: PostgreSQL performance and cost across 23 EC2 instance types
(postgres.saneengineer.com)
I'd be very curious to see you add the Optimized Reads instance types, e.g. r8gd or m8gd, to your benchmark. They add a local NVMe-based SSD block storage that serves as a cache in front of the network-based disks among other use cases. They have been a huge win for us for a read-heavy workload where the dataset is significantly larger than memory.
replyWould be interesting to see huge pages and io2 impact.
replyI did a smaller version on Azure and disk latency had a massive impact much more so than max IOPs (although their crappy storage offering needed like 64-128 iodepth to get advertised iops).
Results seem mostly in line with expectations. Iirc vcpu is threads so on arm64 you get 4 smt1 cores vs Intel/AMD you get 2 smt2 cores.
Interesting, is there something like this for azure
replyI was initially inspired by the https://instances.vantage.sh/, so, like them, I want to add other providers later. Like Azure and GCP.
replyIt would also be interesting to have cross-provider comparison. I think it's doable. Thanks!
Would love to see a comparison between Aurora PostgreSQL and self-host PostgreSQL on the same EC2 instance type.
replyGood point! I kept the configuration of the Postgres pretty close to the defaults, and it would be interesting to compare it with the same default Aurora Postgres.
replyAnd it should be easy to add - I'll check it, thanks!
I would really see this compared to what AWS is offering via RDS
replyYes! This was my initial dilemma - whether to test RDS or self-hosted Postgres on EC2. I decided to start with EC2 to be a bit more "pure", and remove cost overhead of RDS.
replyBut support for RDS is my next candidate for development. Plus, comparison would also be interesting.
[flagged]
replydeleted
reply