Re: Postgres.exe Process taking too much memory and CPU usage - making the system extremely slow.
От | Greg Smith |
---|---|
Тема | Re: Postgres.exe Process taking too much memory and CPU usage - making the system extremely slow. |
Дата | |
Msg-id | 4B226105.4040208@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: Postgres.exe Process taking too much memory and CPU usage - making the system extremely slow. (Dave Page <dpage@pgadmin.org>) |
Ответы |
Re: Postgres.exe Process taking too much memory and CPU
usage - making the system extremely slow.
Re: Postgres.exe Process taking too much memory and CPU usage - making the system extremely slow. |
Список | pgsql-general |
Dave Page wrote:
Dave is talking about Greg Stark here, lest anyone credit me for something I wasn't involved in. I just updated the shared_buffers section of "Tuning Your PostgreSQL Server" to reflect Dave's comments and to generally clean up the Windows suggestions here. I recall seeing some comments in the past that suggested earlier systems started to fall off at closer to 64MB rather than 128MB, tweaked the wording there accordingly. 8MB working out best is really unexpected though; I'd like to know what you were doing where *that* was the optimal setting.On Fri, Dec 11, 2009 at 9:02 AM, Massa, Harald Armin <chef@ghum.de> wrote:I got MUCH better results by drastically lowering shared_buffers on Windows. Drastically = 8MB.Wow - really? Greg and I did some rough pgbench experiments last year and were finding the on a 4GB machine, running XP Pro, 512MB seemed to be optimal, but it was only marginally better than 128 or 256MB. Going lower than that made a noticable difference, and going higher we saw performance dropping off again as well.
-- Greg Smith 2ndQuadrant Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.com
В списке pgsql-general по дате отправления: