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 70CF7D1B538 for ; Wed, 22 Oct 2003 10:26:08 +0000 (GMT) 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 84018-01 for ; Wed, 22 Oct 2003 07:25:39 -0300 (ADT) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by svr1.postgresql.org (Postfix) with ESMTP id F358DD1B4EF for ; Wed, 22 Oct 2003 07:25:35 -0300 (ADT) Received: from myrealbox.com shridhar_daithankar@smtp-send.myrealbox.com [202.54.11.72] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.42 $ on Novell NetWare via secured & encrypted transport (TLS); Wed, 22 Oct 2003 04:25:29 -0600 Message-ID: <3F965B12.5010901@myrealbox.com> Date: Wed, 22 Oct 2003 15:55:22 +0530 From: Shridhar Daithankar User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Hilary Forbes Cc: pgsql-performance@postgresql.org Subject: Re: Processors vs Memory References: <5.1.0.14.0.20031022110951.085d0d70@mailserver.ipl.co.uk> In-Reply-To: <5.1.0.14.0.20031022110951.085d0d70@mailserver.ipl.co.uk> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/568 X-Sequence-Number: 4316 Hilary Forbes wrote: > If I have a fixed amount of money to spend as a general rule >is it better to buy one processor and lots of memory or two >processors and less memory for a system which is transactional >based (in this case it's handling reservations). I realise the >answer will be a generalised one but all the performance bits >I've read seem to talk about adjusting memory allocation. >The client has received the general advice from their hardware >supplier that 2 Xeon processors and less memory is better but >for postgresql I'm thinking they might be better off with a single >processor and loads of memory. The OS is Red Hat Linux. Well it depends. If your projected database size is say 2 gigs, then you should buy 2Gigsof RAM and spend rest of the money on processor. But if your database size(max of currrent and projected) is 100GB, obviously you can not buy 100GB of memory that cheaply. So you should look for fast storage. The order of priority is IO, memory and CPU. If database is just big enough to fit in a gig or two, you should get RAM first. Processor is hardly ever a concern w.r.t database unless you are doing a lot in database business logic. HTH Shridhar