X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 5F590D1B49B for ; Mon, 19 Apr 2004 17:41:09 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 94623-09 for ; Mon, 19 Apr 2004 17:41:08 -0300 (ADT) Received: from hotmail.com (bay9-dav33.bay9.hotmail.com [64.4.46.90]) by svr1.postgresql.org (Postfix) with ESMTP id 72086D1DB5B for ; Mon, 19 Apr 2004 17:41:05 -0300 (ADT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 19 Apr 2004 13:41:07 -0700 Received: from 67.81.102.201 by bay9-dav33.bay9.hotmail.com with DAV; Mon, 19 Apr 2004 20:41:06 +0000 X-Originating-IP: [67.81.102.201] X-Originating-Email: [awerman@hotmail.com] X-Sender: awerman@hotmail.com From: "Aaron Werman" To: References: <200311251419.36771.josh@agliodbs.com> <407EFC95.5070805@aeccom.com> <11437.1082324861@sss.pgh.pa.us> <200404191050.12833.josh@agliodbs.com> Subject: Re: possible improvement between G4 and G5 Date: Mon, 19 Apr 2004 16:41:22 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Message-ID: X-OriginalArrivalTime: 19 Apr 2004 20:41:07.0060 (UTC) FILETIME=[A3CC5B40:01C4264E] X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/302 X-Sequence-Number: 6602 There are a few things that you can do to help force yourself to be I/O bound. These include: - RAID 5 for write intensive applications, since multiple writes per synch write is good. (There is a special case for logging or other streaming sequential writes on RAID 5) - Data journaling file systems are helpful in stress testing your checkpoints - Using midsized battery backed up write through buffering controllers. In general, if you have a small cache, you see the problem directly, and a huge cache will balance out load and defer writes to quieter times. That is why a midsized cache is so useful in showing stress in your system only when it is being stressed. Only partly in jest, /Aaron BTW - I am truly curious about what happens to your system if you use separate RAID 0+1 for your logs, disk sorts, and at least the most active tables. This should reduce I/O load by an order of magnitude. "Vivek Khera" wrote in message news:x7smez7tqj.fsf@yertle.int.kciLink.com... > >>>>> "JB" == Josh Berkus writes: > > JB> Aaron, > >> I do consulting, so they're all over the place and tend to be complex. Very > >> few fit in RAM, but still are very buffered. These are almost all backed > >> with very high end I/O subsystems, with dozens of spindles with battery > >> backed up writethrough cache and gigs of buffers, which may be why I worry > >> so much about CPU. I have had this issue with multiple servers. > > JB> Aha, I think this is the difference. I never seem to be able to > JB> get my clients to fork out for adequate disk support. They are > JB> always running off single or double SCSI RAID in the host server; > JB> not the sort of setup you have. > > Even when I upgraded my system to a 14-spindle RAID5 with 128M cache > and 4GB RAM on a dual Xeon system, I still wind up being I/O bound > quite often. > > I think it depends on what your "working set" turns out to be. My > workload really spans a lot more of the DB than I can end up caching. > > -- > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Vivek Khera, Ph.D. Khera Communications, Inc. > Internet: khera@kciLink.com Rockville, MD +1-301-869-4449 x806 > AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend >