News for hackers. Stuff that matters.

A comment on Debugging PostgreSQL performance the hard way. Parent comment

Re:Debugging PostgreSQL performance the hard way by dfsegoat on Thursday September 29, 2016 @05:15PM (#12608808)
Totally with you there. The pricing is nutty and we had similar issues - but that was back on magnetic drive type (we migrated to RDS in 2012) - ever since then we've been too scared to "get off the piops".

So just provision a 1TB volume or so, and garner the standard iops throughput that comes as a result of the volume size right? I will give that a shot. Looks like you are hitting 1k+ on read and write easy. That is pretty impressive and plenty for us.

[ Parent | on HN ]
Re:Debugging PostgreSQL performance the hard way by mbell on Thursday September 29, 2016 @09:04PM (#12609937)
With a gp2 SSD EBS volume you get 3k iops baseline per 1TB of storage up to a max of 10k iops (~3.3TB volume), there is also some burst allowance over that. In my experience so far the baseline numbers have been pretty accurate.

This is a relatively recent change (last year?), it used to cap out at 3k iops rather than 10k. The only real reason to go for provisioned iops now is if you need > 10k iops per volume.

[ Parent | on HN ]