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 3474A3A2D4C for ; Mon, 3 Jan 2005 04:51:42 +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 00711-04 for ; Mon, 3 Jan 2005 04:51:33 +0000 (GMT) Received: from webmail.moph.go.th (health.moph.go.th [203.157.0.1]) by svr1.postgresql.org (Postfix) with SMTP id 1F8B63A2CC6 for ; Mon, 3 Jan 2005 04:51:31 +0000 (GMT) Received: (qmail 3020 invoked from network); 3 Jan 2005 04:54:12 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by localhost with SMTP; 3 Jan 2005 04:54:12 -0000 Received: from webmail.moph.go.th ([127.0.0.1]) by localhost (webmail.moph.go.th [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 02219-17 for ; Mon, 3 Jan 2005 11:54:12 +0700 (ICT) Received: (qmail 3007 invoked from network); 3 Jan 2005 04:54:10 -0000 Received: from unknown (HELO localhost) (203.157.0.1) by health.moph.go.th with SMTP; 3 Jan 2005 04:54:10 -0000 Received: from 203.157.100.42 ([203.157.100.42]) by webmail.moph.go.th (IMP) with HTTP for ; Mon, 3 Jan 2005 11:54:10 +0700 Message-ID: <1104728050.41d8cff2b2b29@webmail.moph.go.th> Date: Mon, 3 Jan 2005 11:54:10 +0700 From: amrit@health2.moph.go.th To: Mark Kirkwood Cc: PGsql-performance 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> <41D8AD42.1010806@coretech.co.nz> In-Reply-To: <41D8AD42.1010806@coretech.co.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=TIS-620 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.3 X-Originating-IP: 203.157.100.42 X-Virus-Scanned: by amavisd-new at moph.go.th X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.178 tagged_above=0 required=5 tests=AWL, NO_REAL_NAME X-Spam-Level: X-Archive-Number: 200501/8 X-Sequence-Number: 9698 > >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? > > > > > > > > > I would keep shared_buffers in the 10000->20000 range, as this is > allocated *once* into shared memory, so only uses 80->160 Mb in *total*. You mean that if I increase the share buffer to arround 12000 [160 comnnections ] , this will not affect the mem. usage ? > The lower sort_mem will help reduce memory pressure (as this is > allocated for every backend connection) and this will help performance - > *unless* you have lots of queries that need to sort large datasets. If > so, then these will hammer your i/o subsystem, possibly canceling any > gain from freeing up more memory. So there is a need to understand what > sort of workload you have! Will the increasing in effective cache size to arround 200000 make a little bit improvement ? Do you think so? Any comment please , thanks. Amrit Thailand