>>> Josh Berkus <[EMAIL PROTECTED]> wrote: > Attached is the postgresql.conf.simple I used in my presentaiton. It
> has an egregious math error in it (see if you can find it) but should > give you the general idea. Well, this sure looks scary: # maintenance_work_mem = 256MB #webserver with 2GB RAM 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? -Kevin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
