X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 65CDD11F60E5 for ; Thu, 27 Apr 2006 04:58:21 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 78383-01 for ; Thu, 27 Apr 2006 04:58:11 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 96E0211F60AE for ; Thu, 27 Apr 2006 04:58:10 -0300 (ADT) Received: from galaxy.systems.pipex.net (galaxy.systems.pipex.net [62.241.162.31]) by svr4.postgresql.org (Postfix) with ESMTP id B7E415B5966 for ; Thu, 27 Apr 2006 07:58:10 +0000 (GMT) Received: from flange.edesix.com (81-86-64-236.dsl.pipex.com [81.86.64.236]) by galaxy.systems.pipex.net (Postfix) with ESMTP id C9B6DE000239 for ; Thu, 27 Apr 2006 08:58:07 +0100 (BST) Received: from host86-131-245-51.range86-131.btcentralplus.com ([86.131.245.51] helo=[192.168.101.208]) by flange.edesix.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.50) id 1FZ1O2-0007Kh-Ai for pgsql-admin@postgresql.org; Thu, 27 Apr 2006 08:58:06 +0100 Message-ID: <44507999.9080400@edesix.com> Date: Thu, 27 Apr 2006 08:58:17 +0100 From: Robin Iddon User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: New system recommendations References: <8511B4970E0D124898E973DF496F9B432515CF@stash.stackdump.local> In-Reply-To: <8511B4970E0D124898E973DF496F9B432515CF@stash.stackdump.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200604/298 X-Sequence-Number: 21467 Hi, > It is currently running on a 3GHz Xeon HT, 2GB RAM, dual 72GB disks > running RAID 1. This server is a 1U without only 2 drive bays, so I > have a potential issue with drive space. > > As a result, I will be moving the db server to a Dell 1650 with 3 146GB > SCSI drives running RAID 0. System is a dual processor, 1.2GHz, with > 4GB RAM. > > > Do you mean RAID0? You face total data loss when the first disk breaks - a 1.2GHz machine is not going to be young, so I assume neither are the disks - a recipe for disaster I think. If your backup strategy is such that you can cope with total data loss and you are more interested in performance I believe you will get better performance by logical splitting of the database across multiple spindles rather than striping. For example if you put the write-ahead-log onto a spindle by itself you will get better performance than running everything on one jumbo RAID0 drive. Databases are usually sensitive to head latency rather than raw transfer rate. Dedicating one drive to the log (which must be written for each and every insert/update) minimizes the latency on writing the log. Is it perhaps an option to take the 146GB drives out of the 1650 and putting them into the Xeon machine? That might get you the best of both worlds (faster CPU, bigger hard disks, RAID1). One final word or warning, whichever O/S you use HT doesn't always work well for postgres. It's hard to pin down exactly what happens, but on a P4 HT system (2.6 kernel again, PG 8.0) we found that we had some very odd performance problems that were hard to reproduce in the lab but occurred in the live environment a lot. Turning off HT made them go away. Hope this helps, Robin