From: amrit@health2.moph.go.th
To: pg@fastcrypt.com
Cc: PGsql-performance <pgsql-performance@postgresql.org>
Subject: Re: Low Performance for big hospital server ..
Date: Mon, 3 Jan 2005 08:54:03 +0700
Message-ID: <1104717243.41d8a5bb9cb9b@webmail.moph.go.th> (raw)
In-Reply-To: <41D827C1.3050707@fastcrypt.com>
References: <1104634472.41d762681b548@webmail.moph.go.th>
<20050102140828.GA21826@pobox.com>
<1104683293.41d8211d62221@webmail.moph.go.th>
<41D827C1.3050707@fastcrypt.com>
> The common wisdom of shared buffers is around 6-10% of available memory.
> Your proposal below is about 50% of memory.
>
> I'm not sure what the original numbers actually meant, they are quite large.
>
I will try to reduce shared buffer to 1536 [1.87 Mb].
> also effective cache is the sum of kernel buffers + shared_buffers so it
> should be bigger than shared buffers.
also make the effective cache to 2097152 [2 Gb].
I will give you the result , because tomorrow [4/12/05] will be the official day
of my hospital [which have more than 1700 OPD patient/day].
> Also turning hyperthreading off may help, it is unlikely it is doing any
> good unless you are running a relatively new (2.6.x) kernel.
Why , could you give me the reason?
> I presume you are vacuuming on a regular basis?
Yes , vacuumdb daily.
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: amrit@health2.moph.go.th, pg@fastcrypt.com
Subject: Re: Low Performance for big hospital server ..
In-Reply-To: <1104717243.41d8a5bb9cb9b@webmail.moph.go.th>
* 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