From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
---|---|
To: | Jaime Rodriguez <jaime(dot)rodriguez(at)liberux(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Performance and Clustering |
Date: | 2010-04-29 02:04:10 |
Message-ID: | 4BD8E91A.3050805@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Jaime Rodriguez wrote:
> My customer requires that DBMS shall support 4000 simultaneous requests
> Also the system to be deploy maybe a cluster, with 12 microprocessors
In order to support 4000 true simultaneous requests, you'd need 4000
processor cores available. What you probably mean here is that you
expect 4000 simultaneous database connections instead. The number of
connections open and the number actually expected to be doing work at
any time are very different quantities, and that ratio is a critical
number you'll need to determine before you can estimate something here.
Generally a single PostgreSQL server can handle in the range of 100-1000
open connections at a time, depending on OS and hardware specs. The
number of active queries running at any one time will be closer to the
number of cores in the server.
If most connections are read-only, there are a few ways to design a
cluster of systems to support the sort of design needed to scale up to
where you're aiming at. Getting more than one node you can write to in
a cluster is much harder.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg(at)2ndQuadrant(dot)com www.2ndQuadrant.us
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2010-04-29 02:43:18 | Re: Performance and Clustering |
Previous Message | Jaime Casanova | 2010-04-29 01:54:33 | Re: Performance and Clustering |