X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 8C013D1B8CF for ; Thu, 28 Aug 2003 14:09:39 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 21614-03 for ; Thu, 28 Aug 2003 11:09:10 -0300 (ADT) Received: from wired.hub.org (u173n10.eastlink.ca [24.224.173.10]) by svr1.postgresql.org (Postfix) with ESMTP id 631B1D1B8AE for ; Thu, 28 Aug 2003 11:09:05 -0300 (ADT) Received: from [192.168.1.3] ([192.168.1.3]) by wired.hub.org (8.12.9/8.12.9) with ESMTP id h7SE87N2003385; Thu, 28 Aug 2003 11:08:07 -0300 (ADT) (envelope-from excalibur@hub.org) Subject: Re: Hardware recommendations to scale to silly load From: Chris Bowlby Reply-To: excalibur@hub.org To: Ron Johnson Cc: PgSQL Performance ML In-Reply-To: <1061953146.18108.291.camel@haggis> References: <1061948112.15800.53.camel@gibraltar.mattclark.net> <1061953146.18108.291.camel@haggis> Content-Type: text/plain Organization: Hub.Org Networking Services Message-Id: <1062079515.88334.24.camel@morpheus> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Thu, 28 Aug 2003 11:05:17 -0300 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/412 X-Sequence-Number: 3228 On Tue, 2003-08-26 at 23:59, Ron Johnson wrote: > What a fun exercises. Ok, lets see: > Postgres 7.3.4 > RH AS 2.1 > 12GB RAM > motherboard with 64 bit 66MHz PCI slots > 4 - Xenon 3.0GHz (1MB cache) CPUs > 8 - 36GB 15K RPM as RAID10 on a 64 bit 66MHz U320 controller > having 512MB cache (for database) > 2 - 36GB 15K RPM as RAID1 on a 64 bit 66MHz U320 controller > having 512MB cache (for OS, swap, WAL files) > 1 - library tape drive plugged into the OS' SCSI controller. I > prefer DLT, but that's my DEC bias. > 1 - 1000 volt UPS. Be careful here, we've seen that with the P4 Xeon's that are hyper-threaded and a system that has very high disk I/O causes the system to be sluggish and slow. But after disabling the hyper-threading itself, our system flew.. -- Chris Bowlby Hub.Org Networking Services