From: Mark Kirkwood <markir@coretech.co.nz>
To: amrit@health2.moph.go.th
Cc: pgsql-performance@postgresql.org, Michael Adler <adler@pobox.com>
Subject: Re: Low Performance for big hospital server ..
Date: Mon, 03 Jan 2005 15:26:10 +1300
Message-ID: <41D8AD42.1010806@coretech.co.nz> (raw)
In-Reply-To: <1104683293.41d8211d62221@webmail.moph.go.th>
References: <1104634472.41d762681b548@webmail.moph.go.th>
<20050102140828.GA21826@pobox.com>
<1104683293.41d8211d62221@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*.
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!
best wishes
Mark
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, adler@pobox.com
Subject: Re: Low Performance for big hospital server ..
In-Reply-To: <41D8AD42.1010806@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