From: | "chris smith" <dmagick(at)gmail(dot)com> |
---|---|
To: | "Bill Moran" <wmoran(at)potentialtech(dot)com> |
Cc: | "Postgres General" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Bigtime scaling of Postgresql (cluster and stuff I suppose) |
Date: | 2007-09-01 13:12:51 |
Message-ID: | 3c1395330709010612v4cde74c6h9b9eeb6e837977da@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> Ever read anything on how myspace is laid out? The big ones need
> replication to handle the traffic.
Actually no.
http://highscalability.com/livejournal-architecture
"Using MySQL replication only takes you so far." (Yeh it's mysql but
the point is valid regardless).
"You can't keep adding read slaves and scale."
A lot use sharding now to keep scaling (limiting to "X" users/accounts
per database system and just keep adding more database servers for the
next "X" accounts).
Myspace info here:
http://highscalability.com/myspace-architecture
At 3mill users:
- split its user base into chunks of 1 million accounts and put all
the data keyed to those accounts in a separate instance of SQL Server
I'm sure there's replication behind the scenes to help with
read-queries but it's definitely not a magic wand that will fix
everything.
--
Postgresql & php tutorials
http://www.designmagick.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Bill Bartlett | 2007-09-01 13:22:37 | Re: Export data to MS Excel |
Previous Message | Anthony Brock (KG4AGD) | 2007-09-01 13:05:22 | Error Message: invalid command-line arguments for server process |