Re: Low Performance for big hospital server ..

From: Michael Adler <adler(at)pobox(dot)com>
To: amrit(at)health2(dot)moph(dot)go(dot)th
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Low Performance for big hospital server ..
Date: 2005-01-02 14:08:28
Message-ID: 20050102140828.GA21826@pobox.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Sun, Jan 02, 2005 at 09:54:32AM +0700, amrit(at)health2(dot)moph(dot)go(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message amrit 2005-01-02 16:28:13 Re: Low Performance for big hospital server ..
Previous Message Mark Kirkwood 2005-01-02 09:23:45 Re: Low Performance for big hospital server ..