X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 636403A5C15 for ; Thu, 27 Jan 2005 07:59:12 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 08782-05 for ; Thu, 27 Jan 2005 07:59:08 +0000 (GMT) Received: from mail.tecarta.com (66.238.115.135.ptr.us.xo.net [66.238.115.135]) by svr1.postgresql.org (Postfix) with ESMTP id BA5DF3A5BCE for ; Thu, 27 Jan 2005 07:59:08 +0000 (GMT) Received: from mail pickup service by mail.tecarta.com with Microsoft SMTPSVC; Thu, 27 Jan 2005 00:01:42 -0800 Received: from mail.tecarta.com ([192.168.160.2]) by mail.tecarta.com with Microsoft SMTPSVC(6.0.3790.0); Thu, 27 Jan 2005 00:01:35 -0800 Received: from barracuda.tecarta.com ([192.168.160.200]) by mail.tecarta.com (SAVSMTP 3.1.0.29) with SMTP id M2005012700013402756 for ; Thu, 27 Jan 2005 00:01:34 -0800 X-ASG-Debug-ID: 1106812740-7300-1-0 X-Barracuda-URL: http://192.168.160.200:8000/cgi-bin/mark.cgi Received: from mail2 (mail2.hq.corp [192.168.160.6]) by barracuda.tecarta.com (Spam Firewall) with SMTP id 8E53120147EF for ; Wed, 26 Jan 2005 23:59:00 -0800 (PST) Received: from [192.168.0.13] ([63.206.203.145]) by mail.tecarta.com with Microsoft SMTPSVC(6.0.3790.0); Thu, 27 Jan 2005 00:01:33 -0800 Message-ID: <41F82CA2.5070604@sfnet.cc> Date: Wed, 26 Jan 2005 23:49:54 +0000 From: Steve Poe User-Agent: Mozilla Thunderbird 1.0 (X11/20041228) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Josh Berkus Cc: pgsql-performance@postgresql.org X-ASG-Orig-Subj: Re: [PERFORM] Ideal disk setup for Postgresql 7.4? Subject: Re: Ideal disk setup for Postgresql 7.4? References: <41F63424.1060904@sfnet.cc> <200501261003.15267.josh@agliodbs.com> <41F79610.20003@sfnet.cc> <200501261849.15176.josh@agliodbs.com> In-Reply-To: <200501261849.15176.josh@agliodbs.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 27 Jan 2005 08:01:33.0674 (UTC) FILETIME=[6AD8C4A0:01C50446] X-Virus-Scanned: by Barracuda Spam Firewall at tecarta.com X-Barracuda-Spam-Score: -0.65 X-Barracuda-Spam-Status: No, SCORE=-0.65 using global scores of TAG_LEVEL=4.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 tests=BAYES_10, DATE_IN_PAST_06_12 X-Barracuda-Spam-Report: Code version 2.64, rules version 2.1.963 Rule breakdown below pts rule name description ---- ---------------------- ------------------------------------------- -1.50 BAYES_10 BODY: Bayesian spam probability is 10 to 20% [score: 0.1967] 0.85 DATE_IN_PAST_06_12 Date: is 6 to 12 hours before Received: date X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.268 tagged_above=0 required=5 tests=AWL, DATE_IN_PAST_06_12, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/525 X-Sequence-Number: 10215 Josh, Thanks again for the feedback. >Well, the list of ones which are good is shorter: pretty much LSI and 3Ware >(for SATA). You can suffer with Adaptec if you have to. > > > Good. We don't plan on using IDE, but I've pondered Firewire. >>If we went with a single CPU, like Athlon/Opertron64, would CS >>storming go away? >> >> > >Yes. And then you might be able to use SW Raid. Of course, you may lose >performance in other areas with the 1 processor. > > > Good to know. You mentioned earlier that to get around the CS bug, avoid the query structures which trigger it. Dumb question: How do you isolate this? Is there a way in a Postgresql query to only look at 1 processor only in a dual-CPU setup? FYI:Our company has an near-identical server (SCSI and IDE)for testing purposes of the animal hopsital application that is used. If there are any test patches to Postgresql to deal with CS storm, we can test it out if this is possible. Any likelyhood this CS storm will be understood in the next couple months? Thanks. Steve Poe