Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 06FBF9FC260 for ; Tue, 30 Oct 2007 16:21:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 60352-07 for ; Tue, 30 Oct 2007 16:21:12 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sd-2317.dedibox.fr (sd-2317.dedibox.fr [88.191.17.192]) by postgresql.org (Postfix) with ESMTP id A65979FC267 for ; Tue, 30 Oct 2007 16:21:14 -0300 (ADT) Received: from sd-2317.dedibox.fr (localhost.localdomain [127.0.0.1]) by sd-2317.dedibox.fr (Postfix) with ESMTP id 55300C23A; Tue, 30 Oct 2007 20:21:10 +0100 (CET) Received: from [192.168.10.1] (ASte-Genev-Bois-153-1-10-209.w83-112.abo.wanadoo.fr [83.112.72.209]) by sd-2317.dedibox.fr (Postfix) with ESMTP id 104FDB455; Tue, 30 Oct 2007 20:21:10 +0100 (CET) Message-ID: <47278421.6010906@lelarge.info> Date: Tue, 30 Oct 2007 20:21:05 +0100 From: Guillaume Lelarge User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: Christian Rengstl CC: pgsql-performance@postgresql.org Subject: Re: Optimizing PostgreSQL for Windows References: <4727402E.90AD.0080.0@klinik.uni-regensburg.de> In-Reply-To: <4727402E.90AD.0080.0@klinik.uni-regensburg.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/366 X-Sequence-Number: 27388 Christian Rengstl a écrit : > My OS is Windows 2003 with 4GB Ram and Xeon Duo with 3.2 GHz; > shared_buffers is set to 32MB (as I read it should be fairly low on > Windows) and work_mem is set to 2500MB, but nevertheless the query takes > about 38 seconds to finish. The table "table1" contains approx. 3 > million tuples and table2 approx. 500.000 tuples. If anyone could give > an advice on either how to optimize the settings in postgresql.conf or > anything else to make this query run faster, I really would appreciate. > 32MB for shared_buffers seems really low to me but 2500MB for work_mem seems awfully high. The highest I've seen for work_mem was something like 128MB. I think the first thing you have to do is to really lower work_mem. Something like 64MB seems a better bet at first. Regards. -- Guillaume. http://www.postgresqlfr.org http://dalibo.com