X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id AAEADDB902 for ; Wed, 16 Nov 2005 12:02:07 -0400 (AST) 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 28023-03 for ; Wed, 16 Nov 2005 16:02:05 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from hosting.commandprompt.com (128.commandprompt.com [207.173.200.128]) by svr1.postgresql.org (Postfix) with ESMTP id ED20DDB90A for ; Wed, 16 Nov 2005 12:02:04 -0400 (AST) Received: from [10.30.1.41] ([72.16.194.3]) (authenticated bits=0) by hosting.commandprompt.com (8.13.4/8.13.4) with ESMTP id jAGFv0HB000683; Wed, 16 Nov 2005 07:57:03 -0800 Message-ID: <437B5859.9040805@commandprompt.com> Date: Wed, 16 Nov 2005 08:03:37 -0800 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: William Yu CC: pgsql-performance@postgresql.org Subject: Re: Hardware/OS recommendations for large databases ( References: <3E37B936B592014B978C4415F90D662D01995F7B@MI8NYCMAIL06.Mi8.com> <33c6269f0511152115v1a34ab81j30f1f5df5a6c6956@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (hosting.commandprompt.com [192.168.1.101]); Wed, 16 Nov 2005 07:57:03 -0800 (PST) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0 required=5 tests=[AWL=0.000] X-Spam-Score: 0 X-Spam-Level: X-Archive-Number: 200511/283 X-Sequence-Number: 15540 > > The only questions would be: > (1) Do you need a SMP server at all? I'd claim yes -- you always need > 2+ cores whether it's DC or 2P to avoid IO interrupts blocking other > processes from running. I would back this up. Even for smaller installations (single raid 1, 1 gig of ram). Why? Well because many applications are going to be CPU bound. For example we have a PHP application that is a CMS. On a single CPU machine, RAID 1 it takes about 300ms to deliver a single page, point to point. We are not IO bound. So what happens is that under reasonable load we are actually waiting for the CPU to process the code. A simple upgrade to an SMP machine literally doubles our performance because we are still not IO bound. I strongly suggest that everyone use at least a single dual core because of this experience. > > (3) Do you need an insane amount of memory? Well here's the case where > the more expensive motherboard will serve you better since each CPU > slot has its own bank of memory. Spend more money on memory, get > cheaper single-core CPUs. Agreed. A lot of times the slowest dual-core is 5x what you actually need. So get the slowest, and bulk up on memory. If nothing else memory is cheap today and it might not be tomorrow. > Of course, this doesn't apply if you are an Intel/Dell-only shop. Xeon > DCs, while cheaper than their corresponding single-core SMPs, don't > have the same performance profile of Opteron DCs. Basically, you're > paying a bit extra so your server can generate a ton more heat. > Well if you are an Intel/Dell shop running PostgreSQL you have bigger problems ;) Sincerely, Joshua D. Drake > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend