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 765423A5B07 for ; Wed, 26 Jan 2005 08:02:13 +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 83535-04 for ; Wed, 26 Jan 2005 08:02:07 +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 66E0E3A3E21 for ; Wed, 26 Jan 2005 08:02:07 +0000 (GMT) Received: from mail pickup service by mail.tecarta.com with Microsoft SMTPSVC; Wed, 26 Jan 2005 00:04:41 -0800 Received: from mail.tecarta.com ([192.168.160.2]) by mail.tecarta.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 26 Jan 2005 00:04:39 -0800 Received: from barracuda.tecarta.com ([192.168.160.200]) by mail.tecarta.com (SAVSMTP 3.1.0.29) with SMTP id M2005012600043831837 for ; Wed, 26 Jan 2005 00:04:38 -0800 X-ASG-Debug-ID: 1106726523-9611-2-0 X-Barracuda-URL: http://192.168.160.200:8000/cgi-bin/mark.cgi Received: from mail1 (mail1.hq.corp [192.168.160.5]) by barracuda.tecarta.com (Spam Firewall) with SMTP id BE2A3201429D for ; Wed, 26 Jan 2005 00:02:03 -0800 (PST) Received: from [192.168.0.13] ([63.206.203.145]) by mail.tecarta.com with Microsoft SMTPSVC(6.0.3790.0); Wed, 26 Jan 2005 00:04:32 -0800 Message-ID: <41F6DBD8.2050008@sfnet.cc> Date: Tue, 25 Jan 2005 23:52:56 +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> <200501251903.09734.josh@agliodbs.com> In-Reply-To: <200501251903.09734.josh@agliodbs.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 26 Jan 2005 08:04:32.0190 (UTC) FILETIME=[AAD665E0:01C5037D] X-Virus-Scanned: by Barracuda Spam Firewall at tecarta.com X-Barracuda-Spam-Score: -0.06 X-Barracuda-Spam-Status: No, SCORE=-0.06 using global scores of TAG_LEVEL=4.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=7.0 tests=BAYES_30, DATE_IN_PAST_06_12 X-Barracuda-Spam-Report: Code version 2.64, rules version 2.1.954 Rule breakdown below pts rule name description ---- ---------------------- ------------------------------------------- -0.90 BAYES_30 BODY: Bayesian spam probability is 30 to 40% [score: 0.3530] 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.272 tagged_above=0 required=5 tests=AWL, DATE_IN_PAST_06_12, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/491 X-Sequence-Number: 10181 Josh, Thanks for your feedback, I appreciate it. >Check what I have to say at http://www.powerpostgresql.com/PerfList > > Will do. >>They're currently on a two-disk Adaptec RAID1 with Postgresql 7.4.2. >> >> > >And you've not upgraded to 7.4.6 because .... ? > > > Because the proprietary application running the business has not certified on it. Unfortunately, I am at the mercy of their support in case something goes wrong. >>The drive array is a 7-disk fibre channel on a Qlogic 2100 controller. I >>am currently testing RAID5 (sw). >> >> > >In general, RAID 5 is not so great for databases. See the article for more. > > > Okay, thanks. Even with 7-disks? I trust that. So, RAID 1+0 (sw) is probably the best option. I've run sw RAID personally for years without issue. I am a bit hesitant in doing sw RAID for a production server for a database --- probably because its not my server. Any thoughts on sw RAID for Postgresql? >>The main reason of moving to a drive array is the high level of context >>switches we get during the day (>30K for 20 mins per hour). The OS and >>database exist on the same disk but seperate parition (which probably >>makes little difference) >> >> > >Unfortunately, the context switches are probably due to a known issue in >PostgreSQL, and changing the drive array won't help this issue (it may help >other issues though). Search the archives of this list, and pgsql-hackers, >for "Context Switch Bug". > >For the CS bug, the only workaround right now is to avoid the query structures >that trigger it. > > Okay. Darn. While I don't write the queries for the application, I do interact with the company frequently. Their considering moving the queries into the database with PL/pgSQL. Currently their queries are done through ProvIV development using ODBC. Will context switching be minimized here by using PL/pgSQL? > > >>Server Info: >>Centos 3.3 (RHEL 3.x equivelent) >>4GB RAM >>Adaptec 2100S RAID >>Qlogic QLA2100 Fibre >> >> > >CPU? > > Dual Xeon 2.8 CPUs with HT turned off. Thanks again. Steve Poe