From: Anibal David Acosta <aa@devshock.com>
To: 'Greg Smith' <greg@2ndQuadrant.com>
To: pgsql-performance@postgresql.org
Subject: Re: how delete/insert/update affects select performace?
Date: Thu, 8 Sep 2011 22:36:47 -0400
Message-ID: <000501cc6e99$5484c220$fd8e4660$@devshock.com> (raw)
In-Reply-To: <4E696BC8.3030905@2ndQuadrant.com>
References: <004301cc6e26$015a75e0$040f61a0$@devshock.com>
<4E688FFC0200002500040F10@gw.wicourts.gov>
<012001cc6e45$fa57f950$ef07ebf0$@devshock.com>
<4E696BC8.3030905@2ndQuadrant.com>
Even if I have a server with 16GB of ram, I must set the shared_buffer to
512MB on windows?
In the wiki page they talk about 1/4 of ram, in my case that represent a
shared_buffer = 4GB, that is incorrect?
I have 8 GB of ram for each processor, each processor is a quad core with
hyperthreading, that means 16 "processors" o something like that. Windows
show 16 in task manager.
If I can't configure more than 512MB of shared_buffer all other RAM is
unnecessary?
Thanks for your time.
-----Mensaje original-----
De: pgsql-performance-owner@postgresql.org
[mailto:pgsql-performance-owner@postgresql.org] En nombre de Greg Smith
Enviado el: jueves, 08 de septiembre de 2011 09:29 p.m.
Para: pgsql-performance@postgresql.org
Asunto: Re: [PERFORM] how delete/insert/update affects select performace?
On 09/08/2011 12:40 PM, Anibal David Acosta wrote:
> Postgres 9.0 on windows server 2008 r2 HW is a dell dual processor
> with 16gb of ram .
>
The general guidelines for Windows servers such as
http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server recommend a
fairly small setting for the shared_buffers parameters on Windows--no more
than 512MB. That makes your server a bit less likely to run in the nasty
checkpoint spike issues Kevin was alluding to. I don't think we've seen any
reports of that on Windows. The problem is worst on Linux.
--
Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: aa@devshock.com, greg@2ndQuadrant.com
Subject: Re: how delete/insert/update affects select performace?
In-Reply-To: <000501cc6e99$5484c220$fd8e4660$@devshock.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox