X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id B485ED1B518 for ; Wed, 3 Dec 2003 22:35:45 +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 10759-08 for ; Wed, 3 Dec 2003 18:35:16 -0400 (AST) Received: from redhotpenguin.com (c-24-7-81-19.client.comcast.net [24.7.81.19]) by svr1.postgresql.org (Postfix) with ESMTP id 38D99D1B486 for ; Wed, 3 Dec 2003 18:35:13 -0400 (AST) Received: (qmail 14413 invoked by uid 506); 3 Dec 2003 22:35:14 -0000 Received: from fred@redhotpenguin.com by poster.redhotpenguin.com by uid 502 with qmail-scanner-1.16 (clamscan: 0.65. spamassassin: 2.44. Clear:SA:0(-1.1/5.0):. Processed in 1.006262 secs); 03 Dec 2003 22:35:14 -0000 Received: from c-24-7-81-19.client.comcast.net (HELO harpua) (fred@redhotpenguin.com@24.7.81.19) by 192.168.0.2 with RC4-MD5 encrypted SMTP; 3 Dec 2003 22:35:13 -0000 From: "Fred Moyer" To: "'Sean Shanny'" , Subject: Re: Has anyone run on the new G5 yet Date: Wed, 3 Dec 2003 14:35:45 -0800 Message-ID: <000001c3b9ed$cb1bf2a0$0300a8c0@harpua> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 In-Reply-To: <3FCE5B85.9000406@earthlink.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/59 X-Sequence-Number: 4919 > We are running into issues with IO saturation obviously. Since this > thing is only going to get bigger we are looking for some advice on > how to accommodate DB's of this size. > Second and more radical, has anyone run > postgreSQL on the new Apple G5 with an XRaid system? This seems like > a great value combination. Fast CPU, wide bus, Fibre Channel IO, > 2.5TB all for ~17k. If you are going for I/O performance you are best off with one of the Xserve competitors listed at http://www.apple.com/xserve/raid/. The Xserve is based on IDE drives which have a lower seek time (say 8.9 ms) compared to scsi (3.6 ms for seagate cheetah). For small random read/write operations (like databases) this will give you a noticable improvement in performance over ide drives. Also make sure to get as many drives as possible, more spindles equals better I/O performance. > I keep see references to terabyte postgreSQL installations, I was > wondering if anyone on this list is in charge of one of those and can > offer some advice on how to position ourselves hardware wise. I've gone to about half terabyte size and all I can say is you should plan for at least one quarter to one half a rack of drivespace (assuming 14 drives per 4u that's 42 to 84 drives). Do yourself a favor and get more rather than less, you will really appreciate it. I averaged about 2 mb/s average per drive via the raid controller stats on 14 drive array during I/O bound seek and update operations in 2 raid 10 arrays (half xlogs and half data). That comes out to around 2 hours for a terabyte with 70 drives assuming a constant scaling. You may be able to get more or less depending on your setup and query workload. > Thanks. > > --sean > > > ---------------------------(end of > broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html