X-Original-To: pgsql-performance-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 209FD9FB20F for ; Mon, 7 Aug 2006 10:18:26 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 01344-02 for ; Mon, 7 Aug 2006 10:18:16 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.logix-tt.com (mail.logix-tt.com [212.211.145.186]) by postgresql.org (Postfix) with ESMTP id 658639FB22C for ; Mon, 7 Aug 2006 10:18:16 -0300 (ADT) Received: from kingfisher.intern.logix-tt.com (p549D25A1.dip0.t-ipconnect.de [84.157.37.161]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.logix-tt.com (Postfix) with ESMTP id B97CB656B8; Mon, 7 Aug 2006 15:20:12 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id E3979185CD0DC; Mon, 7 Aug 2006 15:18:27 +0200 (CEST) Message-ID: <44D73DA3.7080701@logix-tt.com> Date: Mon, 07 Aug 2006 15:18:27 +0200 From: Markus Schaber Organization: Logical Tracking and Tracing International AG, Switzerland User-Agent: Thunderbird 1.5.0.4 (X11/20060713) MIME-Version: 1.0 To: Arjen van der Meijden , pgsql-performance@postgresql.org Subject: Re: PostgreSQL scalability on Sun UltraSparc T1 References: <44CB7896.8030501@oli.tudelft.nl> <44CB8235.9070903@commandprompt.com> <44CB8DC1.4040105@tweakers.net> <44CB9472.9060206@commandprompt.com> <44CB9D52.8040409@tweakers.net> In-Reply-To: <44CB9D52.8040409@tweakers.net> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.175 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200608/68 X-Sequence-Number: 20253 Hi, Arjen, Arjen van der Meijden wrote: > It was the 8core version with 16GB memory... but actually that's just > overkill, the active portions of the database easily fits in 8GB and a > test on another machine with just 2GB didn't even show that much > improvements when going to 7GB (6x1G, 2x 512M), it was mostly in the > range of 10% improvement or less. I'd be interested in the commit_siblings and commit_delay settings, tuning them could give a high increase on throughput for highly concurrent insert/update workloads, at the cost of latency (and thus worse results for low concurrency situations). Different fsync method settings can also make a difference (I presume that syncing was enabled). HTH, Markus -- Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org