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 0116455F07 for ; Thu, 10 Mar 2005 19:47:06 +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 37852-04 for ; Thu, 10 Mar 2005 19:47:03 +0000 (GMT) Received: from mailgate2.nau.edu (mailgate2.nau.edu [134.114.96.59]) by svr1.postgresql.org (Postfix) with ESMTP id D76C5565A0 for ; Thu, 10 Mar 2005 19:47:02 +0000 (GMT) Received: from CONVERSION-DAEMON.mailgate2.nau.edu by mailgate2.nau.edu (PMDF V6.2-X17 #30770) id <0ID500G01IY816@mailgate2.nau.edu> for pgsql-performance@postgresql.org; Thu, 10 Mar 2005 12:47:01 -0700 (MST) Received: from k2.cet.nau.edu (net9-213.cet.nau.edu [134.114.9.213]) by mailgate2.nau.edu (PMDF V6.2-X17 #30770) with ESMTP id <0ID500F1RIXV37@mailgate2.nau.edu>; Thu, 10 Mar 2005 12:46:43 -0700 (MST) Date: Thu, 10 Mar 2005 12:50:31 -0700 From: Karim Nassar Subject: Re: What's better: Raid 0 or disk for seperate pg_xlog In-reply-to: <4230673B.3020400@arbash-meinel.com> To: John A Meinel Cc: pgsql-performance@postgresql.org Message-id: <1110484232.9252.211.camel@k2.cet.nau.edu> MIME-version: 1.0 X-Mailer: Evolution 2.0.2 Content-type: text/plain Content-transfer-encoding: 7BIT References: <1110440684.6368.163.camel@k2.cet.nau.edu> <4230673B.3020400@arbash-meinel.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200503/182 X-Sequence-Number: 10887 Thanks to all for the tips. On Thu, 2005-03-10 at 09:26 -0600, John A Meinel wrote: > How critical is your data? How update heavy versus read heavy, etc are you? Large, relatively infrequent uploads, with frequent reads. The application is a web front-end to scientific research data. The scientists have their own copy of the data, so if something went really bad, we could probably get them to upload again. > Do you have a way to restore the database if something fails? If > you do nightly pg_dumps, will you survive if you lose a days worth of > transactions? For now, we have access to a terabyte backup server, and the DB is small enough that my sysadmin lets me have hourly pg_dumps for last 24 hours backed up nightly. Veritas is configured to save daily pg_dumps for the last week, a weekly dump for the last month and a monthly version for the last 6 months. > In general I would recommend RAID1, because that is the safe bet. If > your db is the bottleneck, and your data isn't all that critical, and > you are read heavy, I would probably go with RAID1, if you are write > heavy I would say 2 independent disks. I feel that we have enough data safety such that I want to go for speed. Some of the queries are very large joins, and I am going for pure throughput at this point - unless someone can find a hole in my backup tactic. Of course, later we will have money to throw at more spindles. But for now, I am trying gaze in to the future and maximize my current capabilities. Seems to me that the "best" solution would be: * disk 0 partition 1..n - os mounts partition n+1 - /var/lib/postgres/data/pg_xlog * disk 1 partition 1 - /var/lib/postgres/data * Further (safe) performance gains can be had by adding more spindles as such: - first disk: RAID1 to disk 1 - next 2 disks: RAID 0 across the above Do I grok it? Thanks again, -- Karim Nassar Department of Computer Science Box 15600, College of Engineering and Natural Sciences Northern Arizona University, Flagstaff, Arizona 86011 Office: (928) 523-5868 -=- Mobile: (928) 699-9221