X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 06FC8D1EC6E for ; Tue, 23 Mar 2004 18:51:54 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 23603-08 for ; Tue, 23 Mar 2004 14:51:51 -0400 (AST) Received: from bayswater1.ymogen.net (host-154-240-27-217.pobox.net.uk [217.27.240.154]) by svr1.postgresql.org (Postfix) with ESMTP id 29835D1EC69 for ; Tue, 23 Mar 2004 14:51:49 -0400 (AST) Received: from solent (82-68-95-1.dsl.in-addr.zen.co.uk [82.68.95.1]) by bayswater1.ymogen.net (Postfix) with ESMTP id D1B509AC9D; Tue, 23 Mar 2004 18:51:46 +0000 (GMT) From: "Matt Clark" To: "Subbiah, Stalin" , "'Andrew Sullivan'" , Subject: Re: [ADMIN] Benchmarking postgres on Solaris/Linux Date: Tue, 23 Mar 2004 18:51:43 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/319 X-Sequence-Number: 6175 If it's going to be write intensive then the RAID controller will be the most important thing. A dual p3/500 with a write-back cache will smoke either of the boxes you mention using software RAID on write performance. As for the compute intensive side (complex joins & sorts etc), the Dell will most likely beat the Sun by some distance, although what the Sun lacks in CPU power it may make up a bit in memory bandwidth/latency. Matt > -----Original Message----- > From: pgsql-performance-owner@postgresql.org > [mailto:pgsql-performance-owner@postgresql.org]On Behalf Of Subbiah, > Stalin > Sent: 23 March 2004 18:41 > To: 'Andrew Sullivan'; 'pgsql-performance@postgresql.org' > Subject: Re: [PERFORM] [ADMIN] Benchmarking postgres on Solaris/Linux > > > We are looking into Sun V210 (2 x 1 GHz cpu, 2 gig ram, 5.8Os) vs. Dell 1750 > (2 x 2.4 GHz xeon, 2 gig ram, RH3.0). database will mostly be > write intensive and disks will be on raid 10. Wondering if 64bit 1 GHz to > 32bit 2.4 GHz make a big difference here. > > Thanks! > > -----Original Message----- > From: pgsql-performance-owner@postgresql.org > [mailto:pgsql-performance-owner@postgresql.org]On Behalf Of Andrew > Sullivan > Sent: Tuesday, March 23, 2004 9:37 AM > To: 'pgsql-performance@postgresql.org' > Subject: Re: [PERFORM] [ADMIN] Benchmarking postgres on Solaris/Linux > > > On Mon, Mar 22, 2004 at 04:05:45PM -0800, Subbiah, Stalin wrote: > > being the key performance booster for postgres. what is the preferred OS > > for postgres deployment if given an option between linux and solaris. As > > One thing this very much depends on is what you're trying to do. > Suns have a reputation for greater reliability. While my own > experience with Sun hardware has been rather shy of sterling, I _can_ > say that it stands head and shoulders above a lot of the x86 gear you > can get. > > If you're planning to use Solaris on x86, don't bother. Solaris is a > slow, bloated pig compared to Linux, at least when it comes to > managing the largish number of processes that Postgres requires. > > If pure speed is what you're after, I have found that 2-way, 32 bit > Linux on P-IIIs compares very favourably to 4 way 64 bit Ultra SPARC > IIs. > > A > > -- > Andrew Sullivan | ajs@crankycanuck.ca > The fact that technology doesn't work is no bar to success in the > marketplace. > --Philip Greenspun > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org) > > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if your > joining column's datatypes do not match >