Re: Hosting PG on AWS in 2013

From: Vincent Veyron <vv(dot)lists(at)wanadoo(dot)fr>
To: Ben Chobot <bench(at)silentmedia(dot)com>
Cc: David Boreham <david_list(at)boreham(dot)org>, pgsql-general(at)postgresql(dot)org
Subject: Re: Hosting PG on AWS in 2013
Date: 2013-04-08 09:15:20
Message-ID: 1365412520.4293.23.camel@asus-1001PX.home
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Le dimanche 07 avril 2013 à 11:19 -0700, Ben Chobot a écrit :

>
> Overall I won't say that you can get amazing DB performance inside
> AWS, but you can certainly get reasonable performance with enough
> PIOPs volumes and memory, and while the on-demand cost is absurd
> compared to what you can build with bare metal, the reserved-instance
> cost is more reasonable (even if not cheap).

Indeed.

Could someone explain to me the point of using an AWS instance in the
case of the OP, whose site is apparently very busy, versus renting a
bare metal server in a datacenter?

As an example, the site in my sig, which admittedly has much lower
requirements, since I only have a handful of users, has been hosted very
reliably on a rented server at online.net for the past two years on
their smallest server for 15 euros/month. Average load sits at 0.3%.

Using this feels like having a machine in your facility, only better
protected. I use several of those for redundancy.

Is there something I'm missing?

--
Salutations, Vincent Veyron
http://marica.fr/site/demonstration
Logiciel de gestion des contentieux juridiques et des sinistres d'assurance

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Vincent Veyron 2013-04-08 09:37:42 Re: Building 3rd-party contrib/extension on Windows?
Previous Message Michael Paquier 2013-04-08 08:23:10 Re: how to create materialized view in postgresql 8.3