On Tue, Aug 19, 2008 at 1:17 PM, Kevin Grittner <[EMAIL PROTECTED]> wrote: >> Josh Berkus <[EMAIL PROTECTED]> wrote: > But I'm amazed by this, too: > > # max_connections = 700 # web application database > > How many CPUs and spindles are you assuming there? > > My testing and experience suggest applications should use no more than > 4 per CPU plus 2 per spindle, absolute maximum. Don't you find that a > connection pool with queuing capability is required for best > performance with a large number of users?
Agreed, with this many concurrent users, I would expect severe lock contention on the ProcArrayLock. Similarly, if this were heavily updated, WAL-related locks would likely become another significant bottleneck. -- Jonah H. Harris, Senior DBA myYearbook.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
