Re: Using AWS ephemeral SSD storage for production database workload?
От | Ben Chobot |
---|---|
Тема | Re: Using AWS ephemeral SSD storage for production database workload? |
Дата | |
Msg-id | 315F7690-F453-43DE-8C27-61D533178934@silentmedia.com обсуждение исходный текст |
Ответ на | Re: Using AWS ephemeral SSD storage for production database workload? (Sam Gendler <sgendler@ideasculptor.com>) |
Ответы |
Re: Using AWS ephemeral SSD storage for production database workload?
|
Список | pgsql-general |
> On Jan 29, 2018, at 8:05 PM, Sam Gendler <sgendler@ideasculptor.com> wrote: > > Why not use EBS storage, but don’t use provisioned iops SSDs (io1) for the ebs volume. Just use the default storage type(gp2) and live with the 3000 IOPS peak for 30 minutes that that allows. You’d be amazed at just how much I/o can be handledwithin the default IOPS allowance, though bear in mind that you accrue iops credits at a rate that is proportionalto storage amount once you’ve started to eat into your quota, so the performance of someone using general-purposeSSDs (gp2) with 2 terabytes of storage will be different than someone using 100GB of storage. But I recentlymoved several databases to gp2 storage and saved a ton of money doing so (we were paying for 5000 IOPS and using5 AT PEAK other than brief bursts to a couple hundred when backing up and restoring). I’ve done numerous backups andrestores on those hosts since then and have had no trouble keeping up and have never come close to the 3k theoreticalmax, even briefly. Replication doesn’t appear to be bothered, either. One reason would be that gp2 volumes cap out at 160MB/s. We have a bunch of databases on gp2 (it works great) but that throughputcap can bite you if you’re not expecting it.
В списке pgsql-general по дате отправления: