Re: A smaller default postgresql.conf - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: A smaller default postgresql.conf
Date
Msg-id 36e682920808191024leef42b5hc27c2ab98d87d331@mail.gmail.com
Whole thread Raw
In response to Re: A smaller default postgresql.conf  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Tue, Aug 19, 2008 at 1:17 PM, Kevin Grittner
<Kevin.Grittner@wicourts.gov> wrote:
>> Josh Berkus <josh@agliodbs.com> 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: A smaller default postgresql.conf
Next
From: Simon Riggs
Date:
Subject: Re: Adjusting debug_print_plan to be more useful by default