From: | r t <pgsql(at)xzilla(dot)net> |
---|---|
To: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> |
Cc: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>, Sandeep Srinivasa <sss(at)clearsenses(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Why facebook used mysql ? |
Date: | 2010-11-14 22:48:56 |
Message-ID: | AANLkTimqaXJT84qqpVv80EFJ6GC8KK23cNEKkN=hXQF2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Nov 14, 2010 at 12:15 PM, Ron Mayer
<rm_pg(at)cheapcomplexdevices(dot)com>wrote:
> Lincoln Yeoh wrote:
> > What's more important to such companies is the ability to scale over
> > multiple machines.
>
> That question - how much work it is to administer thousands of database
> servers - seems to have been largely missing from this conversation.
>
> Apparently back in 2008, Facebook had 1800 MySQL servers with 2 DBAs.[1]
>
> I wonder how that compares with large-scale Postgres deployments.
>
>
From a technology standpoint, it doesn't need to be ostensibly different,
provided you use Postgres in a way similar to how facebook is using MySQL.
Well, at least now; 8.4's re-implementation of the free space map was
critical for "zero-administration" type deployments. If you can script basic
failover deployments (remember that 1/2 of those 1800 are just slave
machines), you don't abstract storage from the app, and you keep database
schema similar across nodes, you can really ramp up the number of deployed
servers per dba.
Robert Treat
play: http://www.xzilla.net
work: http://www.omniti.com/is/hiring
From | Date | Subject | |
---|---|---|---|
Next Message | anypossibility | 2010-11-14 23:04:56 | when postgres failed to recover after the crash... |
Previous Message | Tom Lane | 2010-11-14 22:35:45 | Re: ipv4 data type does not allow to use % as subnet mask delimiter |