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 D3D543A5982 for ; Tue, 11 Jan 2005 15:39: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 07710-10 for ; Tue, 11 Jan 2005 15:39:13 +0000 (GMT) Received: from stark.xeocode.com (gsstark.mtl.istop.com [66.11.160.162]) by svr1.postgresql.org (Postfix) with ESMTP id B44C03A5970 for ; Tue, 11 Jan 2005 15:39:03 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=stark.xeocode.com) by stark.xeocode.com with smtp (Exim 3.36 #1 (Debian)) id 1CoO6o-00029S-00; Tue, 11 Jan 2005 10:39:02 -0500 To: "Merlin Moncure" Cc: , Subject: Re: which dual-CPU hardware/OS is fastest for PostgreSQL? References: <6EE64EF3AB31D5448D0007DD34EEB3412A75A3@Herge.rcsinc.local> In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3412A75A3@Herge.rcsinc.local> From: Greg Stark Organization: The Emacs Conspiracy; member since 1992 Date: 11 Jan 2005 10:39:01 -0500 Message-ID: <87zmzg0ycq.fsf@stark.xeocode.com> Lines: 25 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.049 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/140 X-Sequence-Number: 9830 "Merlin Moncure" writes: > heh, our apps do tend to be CPU bound. Generally, I think the extra CPU > horsepower is worth the investment until you get to the really high end > cpus. I find that while most applications I work with shouldn't be cpu intensive they do seem end up being cpu bound quite frequently. What happens is that 90% of the workload has a working set that fits in RAM. So the system ends up being bound by the memory bus speed. That appears exactly the same as cpu-bound, though I'm unclear whether increasing the cpu clock will help. It's quite possible to have this situation at the same time as other queries are i/o bound. It's quite common to have 95% of your workload be frequently executed fast queries on commonly accessed data and 5% be bigger data warehouse style queries that need to do large sequential reads. Incidentally, the same was true for Oracle on Solaris. If we found excessive cpu use typically meant some frequently executed query was using a sequential scan on a small table. Small enough to fit in RAM but large enough to consume lots of cycles reading it. -- greg