X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 860693A2C45 for ; Sun, 2 Jan 2005 16:56:45 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 28978-03 for ; Sun, 2 Jan 2005 16:56:40 +0000 (GMT) Received: from net2.micro-automation.com (net2.micro-automation.com [64.7.141.29]) by svr1.postgresql.org (Postfix) with SMTP id 433CD3A19BF for ; Sun, 2 Jan 2005 16:56:39 +0000 (GMT) Received: (qmail 12460 invoked from network); 2 Jan 2005 16:56:11 -0000 Received: from dcdsl.ebox.com (HELO ?192.168.1.36?) (davec@64.7.143.116) by net2.micro-automation.com with SMTP; 2 Jan 2005 16:56:11 -0000 Message-ID: <41D827C1.3050707@fastcrypt.com> Date: Sun, 02 Jan 2005 11:56:33 -0500 From: Dave Cramer Reply-To: pg@fastcrypt.com Organization: Postgres International User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: amrit@health2.moph.go.th Cc: pgsql-performance@postgresql.org Subject: Re: Low Performance for big hospital server .. References: <1104634472.41d762681b548@webmail.moph.go.th> <20050102140828.GA21826@pobox.com> <1104683293.41d8211d62221@webmail.moph.go.th> In-Reply-To: <1104683293.41d8211d62221@webmail.moph.go.th> Content-Type: text/plain; charset=TIS-620; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/5 X-Sequence-Number: 9695 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