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 4E8BC55456 for ; Thu, 10 Mar 2005 19:56:17 +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 40815-02 for ; Thu, 10 Mar 2005 19:56:15 +0000 (GMT) Received: from ct.radiology.uiowa.edu (ct.radiology.uiowa.edu [129.255.60.186]) by svr1.postgresql.org (Postfix) with ESMTP id D9463545E9 for ; Thu, 10 Mar 2005 19:56:13 +0000 (GMT) Received: from [192.168.1.11] (12-217-241-0.client.mchsi.com [12.217.241.0]) by ct.radiology.uiowa.edu (8.11.6/8.11.6) with ESMTP id j2AJu8311748; Thu, 10 Mar 2005 13:56:08 -0600 Message-ID: <4230A653.4090708@arbash-meinel.com> Date: Thu, 10 Mar 2005 13:56:03 -0600 From: John Arbash Meinel User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: Karim Nassar , pgsql-performance@postgresql.org Subject: Re: What's better: Raid 0 or disk for seperate pg_xlog References: <1110440684.6368.163.camel@k2.cet.nau.edu> <4230673B.3020400@arbash-meinel.com> <1110484232.9252.211.camel@k2.cet.nau.edu> In-Reply-To: <1110484232.9252.211.camel@k2.cet.nau.edu> X-Enigmail-Version: 0.90.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig8BCB7333F80A668AA336961B" 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/183 X-Sequence-Number: 10888 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8BCB7333F80A668AA336961B Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Karim Nassar wrote: >Thanks to all for the tips. > > ... >>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 >> >> ^^^^^ -> RAID0 >>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 > > Sounds decent to me. I did make the mistake that you might want to consider a RAID0. But the performance gains might be small, and you potentially lose everything. But your update strategy seems dead on. >Do I grok it? > >Thanks again, > > John =:-> --------------enig8BCB7333F80A668AA336961B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFCMKZUJdeBCYSNAAMRAm0EAKCJ5w9IjmpQcxiBVqi0xxVKAhQtxgCgoXIQ Qx5E1GrX2AvGh2g14XI2tIk= =2pCv -----END PGP SIGNATURE----- --------------enig8BCB7333F80A668AA336961B--