Wow! Thanks. This is by far, the best written and more informative stuff I've read on this.
I've been considering switching to AWS sooner-than-later for the RDS ( we bootstrapped on Linode with a plan to redeploy on AWS in the future ) , but it looks like we shouldn't pursue that yet! On Wednesday, February 19, 2014 3:08:15 AM UTC-5, Valentino Volonghi wrote: > > PG RDS is fairly bad, we're going to move off of it because it's > really unusable but we're creating our own replacement for it. But if > you enable Multi-AZ support you'll have a ton of latency that's > unexplained (multiple seconds of latency on each query or connection). > Sometimes write latencies will spike to multiple seconds and so on. We > ran a pg 8.4 database in ec2 on our own instance with EBS and > everything and never had these issues a single time in 5 years. We've > had more problems with PG 9.3.2 in RDS in 4 weeks than in 8.4 on our > hardware in 5 years. Still vastly immature IMHO, we're using PIOPS and > EBS optimized instances. > > The other issue is that there are no c3s in RDS yet so you get a much > faster machine (5x) by running your own c3s instead of the m2s for 50% > more cost. > > -- > Valentino Volonghi | Chief Architect > P: +1-877-723-7655 | F: +1-415-738-8026 > AdRoll.com Increase Sales. Raise Awareness. > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
