pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: William Yu <wyu@talisys.com>
To: pgsql-performance@postgresql.org
Subject: Re: Low Performance for big hospital server ..
Date: Mon, 03 Jan 2005 00:32:10 -0800
Message-ID: <crb01v$hp4$1@news.hub.org> (raw)
In-Reply-To: <1104717243.41d8a5bb9cb9b@webmail.moph.go.th>
References: <1104634472.41d762681b548@webmail.moph.go.th>
	<20050102140828.GA21826@pobox.com>
	<1104683293.41d8211d62221@webmail.moph.go.th>
	<41D827C1.3050707@fastcrypt.com>
	<1104717243.41d8a5bb9cb9b@webmail.moph.go.th>

amrit@health2.moph.go.th wrote:
> I will try to reduce shared buffer to 1536 [1.87 Mb].

1536 is probaby too low. I've tested a bunch of different settings on my 
  8GB Opteron server and 10K seems to be the best setting.


>>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].

To figure out your effective cache size, run top and add free+cached.


>>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?

Pre 2.6, the kernel does not know the difference between logical and 
physical CPUs. Hence, in a dual processor system with hyperthreading, it 
actually sees 4 CPUs. And when assigning processes to CPUs, it may 
assign to 2 logical CPUs in the same physical CPU.


> 
> 
>>I presume you are vacuuming on a regular basis?
> 
> Yes , vacuumdb daily.

Do you vacuum table by table or the entire DB? I find over time, the 
system tables can get very bloated and cause a lot of slowdowns just due 
to schema queries/updates. You might want to try a VACUUM FULL ANALYZE 
just on the system tables.



view thread (38+ messages)  latest in thread

Message-ID: <crb01v$hp4$1@news.hub.org>
Permalink:  ../crb01v$hp4$1@news.hub.org/
Also on:    postgresql.org/message-id/crb01v$hp4$1@news.hub.org

 · 

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: wyu@talisys.com
  Subject: Re: Low Performance for big hospital server ..
  In-Reply-To: <crb01v$hp4$1@news.hub.org>

* 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