Message-ID: <44D743E4.6050109@tweakers.net>
Date: Mon, 07 Aug 2006 15:45:08 +0200
From: Arjen van der Meijden <acmmailing@tweakers.net>
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
To: Markus Schaber <schabi@logix-tt.com>
CC: 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> <44D73DA3.7080701@logix-tt.com>
In-Reply-To: <44D73DA3.7080701@logix-tt.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit

Hi Markus,

As said, our environment really was a read-mostly one. So we didn't do 
much inserts/updates and thus spent no time tuning those values and left 
them as default settings.

Best regards,

Arjen

Markus Schaber wrote:
> 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
> 
>