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 50F0F3A2C0C for ; Mon, 3 Jan 2005 06:16:17 +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 75990-07 for ; Mon, 3 Jan 2005 06:16:05 +0000 (GMT) Received: from mail.coretech.co.nz (coretech.co.nz [202.36.204.41]) by svr1.postgresql.org (Postfix) with ESMTP id 92CEC3A2D9B for ; Mon, 3 Jan 2005 06:16:04 +0000 (GMT) Received: (qmail 11590 invoked from network); 3 Jan 2005 06:16:02 -0000 Received: from 218-101-14-25.paradise.net.nz (HELO ?192.168.1.11?) (218.101.14.25) by 0 with SMTP; 3 Jan 2005 06:16:02 -0000 Message-ID: <41D8E406.1090501@coretech.co.nz> Date: Mon, 03 Jan 2005 19:19:50 +1300 From: Mark Kirkwood User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: amrit@health2.moph.go.th 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> <1104728050.41d8cff2b2b29@webmail.moph.go.th> In-Reply-To: <1104728050.41d8cff2b2b29@webmail.moph.go.th> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200501/9 X-Sequence-Number: 9699 amrit@health2.moph.go.th wrote: >>>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 ? > > > shared_buffers = 12000 will use 12000*8192 bytes (i.e about 96Mb). It is shared, so no matter how many connections you have it will only use 96M. >>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? > > > I would leave it at the figure you proposed (128897), and monitor your performance. (you can always increase it later and see what the effect is). regards Mark