Date: Wed, 05 Apr 2006 20:41:16 -0700
From: Robert Lor <Robert.Lor@Sun.COM>
Subject: Re: Sun Fire T2000 and PostgreSQL 8.1.3
In-reply-to: <12500.1144263844@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "Juan Casero (FL FLC)" <Juan.Casero@wholefoods.com>,
	pgsql-performance@postgresql.org
Message-id: <44348DDC.60505@sun.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.7) Gecko/20050913
References: <7583B3F1891CC0429FA4A44952AA539C66FA2C@wfm-exchprd2.wfm.pvt>
	<12500.1144263844@sss.pgh.pa.us>

Tom is right. Unless your workload can generate lots of simultaneous 
queries, you will not reap the full benefit of the Sun Fire T2000 
system. I have tested 8.1.3 with an OLTP workload on an 8 cores system. 
With 1500-2000 client connections, the CPU was only about 30% utilized. 
The UltraSPARC T1 processor was designed for throughput with many cores 
running at lower frequency (1-1.2 GHz) to reduce power consumption. To 
speed up a single big query, you'd be better off with a parallelize DB 
or an Opteron system with higher clock speed like this one 
http://www.sun.com/servers/entry/x4200/

Regards,
-Robert

Tom Lane wrote:

>"Juan Casero \(FL FLC\)" <Juan.Casero@wholefoods.com> writes:
>  
>
>>... This box has a single Ultrasparc T1 cpu with six execution
>>piplelines that can each handle 4 threads.  With the Unix top utility
>>the postgresql server appears to bounce around between the available
>>threads on the system.
>>    
>>
>
>Try sending it more than one query at a time?  If you're testing with
>just one client connection issuing queries, that's about what I'd expect.
>
>			regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: explain analyze is your friend
>  
>