From: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
---|---|
To: | "Duffey, Kevin" <KDuffey(at)marketron(dot)com> |
Cc: | PgSQL General ML <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Scalability (both vertical and horizontal)? |
Date: | 2003-09-18 20:54:54 |
Message-ID: | Pine.LNX.4.33.0309181451170.11073-100000@css120.ihs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 18 Sep 2003, Duffey, Kevin wrote:
> We are looking for information regarding any capabilities of PostgreSQL
> in regards to scalability. Ideally we want to be able to scale in both
> directions. What sort of solutions are out there for either or both
> directions of scalability? Specifically, open-source solutions would be
> most in need, but commercial applications are fine as well.
The most important resource as regards vertical scalability is probably
the performance mailing list. I.e. Postgresql can already take advantage
of multiple processors and spare memory and fast I/O subsystems, but
things like 64 way Sun E10ks are not commonly tested with Postgresql, so
if you're the first guy on the block to buy one, you might find some
issues that need ironing out with that large of a piece of iron.
As for horizontal scaling, you could look at ERserver for that. Setup one
master writer and a bunch of slave boxes to handle the majority of the
queries. There's not been a bunch of work into horizontal scaling really,
with most of the clustering software for postgresql aiming at failover /
high availability, not massive parallelization of read and / or writes.
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Chittenden | 2003-09-18 21:04:46 | Re: PostgreSQL versus MySQL |
Previous Message | Mike Mascari | 2003-09-18 20:43:39 | Re: Image data type equivalent in postgresql |