From: Dave Cramer <pg@fastcrypt.com>
To: amrit@health2.moph.go.th
Cc: pgsql-performance@postgresql.org
Subject: Re: Low Performance for big hospital server ..
Date: Sun, 02 Jan 2005 11:56:33 -0500
Message-ID: <41D827C1.3050707@fastcrypt.com> (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>
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.
also effective cache is the sum of kernel buffers + shared_buffers so it
should be bigger than shared buffers.
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.
I presume you are vacuuming on a regular basis?
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.
>>
>>
>
>Can you give me an idea why should I use the SMP kernel instead of Bigmen kernel
>[turn off the hyperthreading]? Will it be better to turn off ?
>
>
>
>>>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. =)
>>
>>
>
>I think so that there may be some query load on our programe and I try to locate
>it.
>But if I reduce the config to :
>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?
>
>Thanks for all comment.
>Amrit
>Thailand
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
>
>
>
--
Dave Cramer
http://www.postgresintl.com
519 939 0336
ICQ#14675561
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: pg@fastcrypt.com, amrit@health2.moph.go.th
Subject: Re: Low Performance for big hospital server ..
In-Reply-To: <41D827C1.3050707@fastcrypt.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