pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mark Kirkwood <markir@coretech.co.nz>
To: amrit@health2.moph.go.th
Cc: PGsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Low Performance for big hospital server ..
Date: Mon, 03 Jan 2005 19:19:50 +1300
Message-ID: <41D8E406.1090501@coretech.co.nz> (raw)
In-Reply-To: <1104728050.41d8cff2b2b29@webmail.moph.go.th>
References: <1104634472.41d762681b548@webmail.moph.go.th>
	<20050102140828.GA21826@pobox.com>
	<1104683293.41d8211d62221@webmail.moph.go.th>
	<41D8AD42.1010806@coretech.co.nz>
	<1104728050.41d8cff2b2b29@webmail.moph.go.th>

amrit@health2.moph.go.th wrote:

>>>max_connections = 160
>>>shared_buffers =  2048	  [Total = 2.5 Gb.]
>>>sort_mem  = 8192   [Total = 1280 Mb.]
>>>vacuum_mem = 16384
>>>effective_cache_size  = 128897 [= 1007 Mb. = 1 Gb.  ]
>>>Will it be more suitable for my server than before?
>>>
>>>
>>>
>>>
>>>      
>>>
>>I would keep shared_buffers in the 10000->20000 range, as this is
>>allocated *once* into shared memory, so only uses 80->160 Mb in *total*.
>>    
>>
>
>You mean that if I increase the share buffer to arround 12000 [160 comnnections
>] , this will not affect the mem. usage ?
>
>  
>
shared_buffers = 12000 will use 12000*8192 bytes (i.e about 96Mb). It is
shared, so no matter how many connections you have it will only use 96M.


>>The lower sort_mem will help reduce memory pressure (as this is
>>allocated for every backend connection) and this will help performance -
>>*unless* you have lots of queries that need to sort large datasets. If
>>so, then these will hammer your i/o subsystem, possibly canceling any
>>gain from freeing up more memory. So there is a need to understand what
>>sort of workload you have!
>>    
>>
>
>Will the increasing in effective cache size to arround 200000 make a little bit
>improvement ? Do you think so?
>
>  
>
I would leave it at the figure you proposed (128897), and monitor your
performance.
(you can always increase it later and see what the effect is).

regards

Mark




view thread (38+ messages)  latest in thread

Message-ID: <41D8E406.1090501@coretech.co.nz>
Permalink:  ../41D8E406.1090501@coretech.co.nz/
Also on:    postgresql.org/message-id/41D8E406.1090501@coretech.co.nz

 · 

reply

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: markir@coretech.co.nz, amrit@health2.moph.go.th
  Subject: Re: Low Performance for big hospital server ..
  In-Reply-To: <41D8E406.1090501@coretech.co.nz>

* 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