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 B68ADD1E949 for ; Mon, 19 Apr 2004 14:39:03 -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 26384-04 for ; Mon, 19 Apr 2004 14:39:02 -0300 (ADT) Received: from lorax.kcilink.com (lorax.kciLink.com [206.112.95.1]) by svr1.postgresql.org (Postfix) with ESMTP id CD11CD1E812 for ; Mon, 19 Apr 2004 14:39:01 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by lorax.kcilink.com (Postfix) with ESMTP id CEDED3F44 for ; Mon, 19 Apr 2004 13:39:01 -0400 (EDT) Received: from lorax.kcilink.com ([127.0.0.1]) by localhost (lorax.kcilink.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 25357-03-2 for ; Mon, 19 Apr 2004 13:39:01 -0400 (EDT) Received: by lorax.kcilink.com (Postfix, from userid 8) id 533453F1D; Mon, 19 Apr 2004 13:39:01 -0400 (EDT) To: pgsql-performance@postgresql.org Path: not-for-mail From: Vivek Khera Newsgroups: ml.postgres.performance Subject: Re: possible improvement between G4 and G5 Date: Mon, 19 Apr 2004 13:39:00 -0400 Organization: Khera Communications, Inc., Rockville, MD Lines: 26 Message-ID: References: <009901c41b48$8357c860$2500fa0a@CardServices.TCI.com> <200404061152.17997.josh@agliodbs.com> <200404061441.53598.josh@agliodbs.com> NNTP-Posting-Host: yertle.kcilink.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: lorax.kcilink.com 1082396341 55887 65.205.34.180 (19 Apr 2004 17:39:01 GMT) X-Complaints-To: daemon@kciLink.com NNTP-Posting-Date: Mon, 19 Apr 2004 17:39:01 +0000 (UTC) User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Reasonable Discussion, berkeley-unix) Cancel-Lock: sha1:z/lJLpuNc9JdR8uVFivUP1NvE5Q= X-Virus-Scanned: by amavisd-new at kcilink.com X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/275 X-Sequence-Number: 6575 >>>>> "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/