Show HN: PostgreSQL performance and cost across 23 EC2 instance types

Re:Show HN: PostgreSQL performance and cost across 23 EC2 in... by nijave on Tuesday July 07, 2026 @01:13PM (#48820689)

Would be interesting to see huge pages and io2 impact.

I 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.

[ Parent | on HN ]

Re:Show HN: PostgreSQL performance and cost across 23 EC2 in... by anivan_ on Tuesday July 07, 2026 @01:45PM (#48821110)

Good points, thanks. On huge pages: this is also about RDS vs self-managed EC2 Postgres. RDS effectively has "on" by default, but default self-managed (that I benchmarked) is "try" which is effectively "off". I'll update the methodology page to cover that, and, yeah, it makes sense to cover that separately.

io2 is on my future-work list. And agree, I have the same feelings about IOPS.

[ Parent | on HN ]

Re:Show HN: PostgreSQL performance and cost across 23 EC2 in... by Rafuino on Tuesday July 07, 2026 @02:44PM (#48821847)

Most of the recent AMD instances on AWS have SMT off so 1 core per vCPU. None of those seem to be tested here though

[ Parent | on HN ]