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 CDFD256506 for ; Wed, 23 Feb 2005 20:25:22 +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 25554-03 for ; Wed, 23 Feb 2005 20:25:17 +0000 (GMT) Received: from server07.icaen.uiowa.edu (server07.icaen.uiowa.edu [128.255.17.47]) by svr1.postgresql.org (Postfix) with ESMTP id 48DD156508 for ; Wed, 23 Feb 2005 20:25:16 +0000 (GMT) Received: from server11.icaen.uiowa.edu (server11.icaen.uiowa.edu [128.255.17.51]) by server07.icaen.uiowa.edu (8.13.2/8.12.9) with ESMTP id j1NKPH3I003574; (envelope-from ) Wed, 23 Feb 2005 14:25:17 -0600 (CST) Received: from [192.168.1.174] (67-41-93-122.cdrr.qwest.net [67.41.93.122]) (authenticated user=jfmeinel) by server11.icaen.uiowa.edu (8.13.2/smtp-serv-1.7) with ESMTP id j1NKOveC025933 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256); (envelope-from ) Wed, 23 Feb 2005 14:25:13 -0600 (CST) Message-ID: <421CE699.1060300@arbash-meinel.com> Date: Wed, 23 Feb 2005 14:24:57 -0600 From: John Arbash Meinel User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Allgood Cc: pgsql-performance@postgresql.org Subject: Re: Peformance Tuning Opterons/ Hard Disk Layout References: <421cca80.3da18bb5.6940.3b12@smtp.gmail.com> <21021.1109183848@sss.pgh.pa.us> <421CD668.7010503@turbocorp.com> <421CDD83.3070609@arbash-meinel.com> <421CE1FD.80003@turbocorp.com> In-Reply-To: <421CE1FD.80003@turbocorp.com> X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig58874C2859034230FAA51461" X-Virus-Scanned: ClamAV 0.80/682/Mon Jan 24 12:53:43 2005 clamav-milter version 0.80j on clamav.icaen.uiowa.edu X-Virus-Scanned: ClamAV 0.80/706/Sun Feb 13 18:14:02 2005, clamav-milter version 0.75 on clamav.icaen.uiowa.edu X-Virus-Status: Clean X-Virus-Status: Clean 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: 200502/339 X-Sequence-Number: 10668 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig58874C2859034230FAA51461 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit John Allgood wrote: > This some good info. The type of attached storage is a Kingston 14 bay > Fibre Channel Infostation. I have 14 36GB 15,000 RPM drives. I think > the way it is being explained that I should build a mirror with two > disk for the pg_xlog and the striping and mirroring the rest and put > all my databases into one cluster. Also I might mention that I am > running clustering using Redhat Clustering Suite. So are these 14-disks supposed to be shared across all of your 9 databases? It seems to me that you have a few architectural issues here. First, you can't really have 2 masters writing to the same disk array. I'm not sure if Redhat Clustering gets around this. But second is that you can't run 2 postgres engines on the same database. Postgres doesn't support a clustered setup. There are too many issues with concurancy and keeping everyone in sync. Since you seem to be okay with having a bunch of smaller localized databases, which update a master database 1/day, I would think you would want hardware to go something like this. 1 master server, at least dual opteron with access to lots of disks (likely the whole 14 if you can get away with it). Put 2 as a RAID1 for the OS, 4 as a RAID10 for pg_xlog, and then the other 8 as RAID10 for the rest of the database. 8-9 other servers, these don't need to be as powerful, since they are local domains. Probably a 4-disk RAID10 for the OS and pg_xlog is plenty good, and whatever extra disks you can get for the local database. The master database holds all information for all domains, but the other databases only hold whatever is the local information. Every night your script sequences through the domain databases one-by-one, updating the master database, and synchronizing whatever data is necesary back to the local domain. I would guess that this script could actually just continually run, going to each local db in turn, but you may want nighttime only updating depending on what kind of load they have. John =:-> --------------enig58874C2859034230FAA51461 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.4.0 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCHOaZJdeBCYSNAAMRAv/JAJ0e5Zs4cPApbFr99sQmMgQ+36WhRACdH8BB AhtJaz6Tof8qILgHI2FBUms= =DAxU -----END PGP SIGNATURE----- --------------enig58874C2859034230FAA51461--