From: Michael Adler <adler@pobox.com>
To: amrit@health2.moph.go.th
Cc: pgsql-performance@postgresql.org
Subject: Re: Low Performance for big hospital server ..
Date: Sun, 2 Jan 2005 09:08:28 -0500
Message-ID: <20050102140828.GA21826@pobox.com> (raw)
In-Reply-To: <1104634472.41d762681b548@webmail.moph.go.th>
References: <1104634472.41d762681b548@webmail.moph.go.th>
On Sun, Jan 02, 2005 at 09:54:32AM +0700, amrit@health2.moph.go.th wrote:
> postgresql 7.3.2-1 with RH 9 on a mechine of 2 Xeon 3.0 Ghz and ram of 4 Gb.
You may want to try disabling hyperthreading, if you don't mind
rebooting.
> grew up to 3.5 Gb and there were more than 160 concurent connections.
Looks like your growing dataset won't fit in your OS disk cache any
longer. Isolate your most problematic queries and check out their
query plans. I bet you have some sequential scans that used to read
from cache but now need to read the disk. An index may help you.
More RAM wouldn't hurt. =)
-Mike Adler
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: adler@pobox.com, amrit@health2.moph.go.th
Subject: Re: Low Performance for big hospital server ..
In-Reply-To: <20050102140828.GA21826@pobox.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