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 6D8DE3A2D7A for ; Mon, 3 Jan 2005 10:07:51 +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 43227-08 for ; Mon, 3 Jan 2005 10:07:32 +0000 (GMT) Received: from boutiquenumerique.com (boutiquenumerique.com [82.67.9.10]) by svr1.postgresql.org (Postfix) with ESMTP id 0F4C23A1996 for ; Mon, 3 Jan 2005 10:07:33 +0000 (GMT) Received: (qmail 8088 invoked from network); 3 Jan 2005 11:07:42 +0100 Received: from unknown (HELO musicbox) (boutiquenumerique-lists@192.168.0.2) by boutiquenumerique.com with SMTP; 3 Jan 2005 11:07:42 +0100 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> <41D8E406.1090501@coretech.co.nz> <1104740336.41d8fff03ff3a@webmail.moph.go.th> Message-ID: Date: Mon, 03 Jan 2005 11:08:32 +0100 From: =?iso-8859-15?Q?Pierre-Fr=E9d=E9ric_Caillaud?= Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?= Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <1104740336.41d8fff03ff3a@webmail.moph.go.th> User-Agent: Opera M2/7.54 (Linux, build 751) 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/14 X-Sequence-Number: 9704 > Decrease the sort mem too much [8196] make the performance much slower > so I use > sort_mem = 16384 > and leave effective cache to the same value , the result is quite better > but I > should wait for tomorrow morning [official hour] to see the end result. You could also profile your queries to see where those big sorts come from, and maybe add some indexes to try to replace sorts by index-scans-in-order, which use no temporary memory. Can you give an example of your queries which make use of big sorts like this ?