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 641343A4C58 for ; Fri, 21 Jan 2005 23:23:44 +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 25140-06 for ; Fri, 21 Jan 2005 23:23:32 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by svr1.postgresql.org (Postfix) with ESMTP id 3D8B93A4CFE for ; Fri, 21 Jan 2005 23:23:31 +0000 (GMT) Received: from sysexperts.com (c-24-6-183-218.client.comcast.net[24.6.183.218]) by comcast.net (rwcrmhc12) with ESMTP id <2005012123233101400hm7c1e>; Fri, 21 Jan 2005 23:23:31 +0000 Received: from localhost (localhost [127.0.0.1]) (uid 1000) by filer with local; Fri, 21 Jan 2005 15:23:30 -0800 id 00045215.41F18EF2.00003C1A Date: Fri, 21 Jan 2005 15:23:30 -0800 From: Kevin Brown To: pgsql-performance@postgresql.org Subject: Re: PostgreSQL vs. Oracle vs. Microsoft Message-ID: <20050121232329.GA7164@filer> Mail-Followup-To: Kevin Brown , pgsql-performance@postgresql.org References: <1105333466.41e20cda39716@webmail.rawbw.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: Organization: Frobozzco International User-Agent: Mutt/1.5.6+20040907i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/401 X-Sequence-Number: 10091 Randolf Richardson wrote: > > The best DB platform is what they currently have, regardless of what > > they have, unless there is a very compelling reason to switch. > [sNip] > > Have you heard the saying "Nobody ever got fired for picking IBM?" It > is one of those situations where if they don't spend the money in their > budget, then they lose it the next time around (no suggestions are needed > on this issue, but thanks anyway). If that's their situation, then they're almost certainly better off throwing the additional money at beefier hardware than at a more expensive database engine, because the amount of incremental performance they'll get is almost certainly going to be greater with better hardware than with a different database engine. In particular, they're probably best off throwing the money at the highest performance disk subsystem they can afford. But that, like anything else, depends on what they're going to be doing. If it's likely to be a small database with lots of processor-intensive analysis, then a beefier CPU setup would be in order. But in my (limited) experience, the disk subsystem is likely to be a bottleneck long before the CPU is in the general case, especially these days as disk subsystems haven't improved in performance nearly as quickly as CPUs have. -- Kevin Brown kevin@sysexperts.com