4 ms·
That's quite interesting; I don't see how one can really so soundly beat the disk configuration, but it certainly can be matched by something similar. It was p
by fdr 14y ago
That's quite interesting; I don't see how one can really so soundly beat the disk configuration, but it certainly can be matched by something similar.
It was posted about quite some time ago: http://orion.herokuapp.com/past/2009/7/29/io_performance_on_ebs/ http://orion.herokuapp.com/past/2009/7/29/io_performance_on_.... If this has become bad advice, inquiring minds wish to know. EBS Priops seem promising and different.
Replication out of Heroku would be neat, but the WAL as-is is architecture and operating system dependent. Luck and tenaciousness willing, logical replication in Postgres may yet serve that use case, some day -- we'll have to see as to the details. A lot of effort has been expended attempting to get it in some form into 9.3, but it's far from sure thing.
Also, don't forget to set up archiving, if you continue to retain fast interconnect with S3: https://github.com/wal-e/wal-e https://github.com/wal-e/wal-e, which I principally wrote on Heroku's behalf, but now is a project of multiple users and contributors. It has a focus on ease of use and reliability, although it could suffer improvement.
- ctide 14y agoYeah, we're using wal-e in conjunction with streaming replication. Either of those options would have been awesome (anything but Bucardo, really. Bucardo's triggers overwhelmed an already overwhelmed database)
- zwily 14y ago"EBS Priops seem promising and different." We run many busy PG databases on PIOPS. The difference from normal EBS is huge. Very happy with PIOPS.