Re: A smaller default postgresql.conf
От | Kevin Grittner |
---|---|
Тема | Re: A smaller default postgresql.conf |
Дата | |
Msg-id | 48AAB9EA.EE98.0025.0@wicourts.gov обсуждение исходный текст |
Ответ на | Re: A smaller default postgresql.conf (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: A smaller default postgresql.conf
Re: A smaller default postgresql.conf Re: A smaller default postgresql.conf |
Список | pgsql-hackers |
>>> Josh Berkus <josh@agliodbs.com> 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
В списке pgsql-hackers по дате отправления: