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 1B6E03A484C for ; Thu, 20 Jan 2005 21:44:32 +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 83324-08 for ; Thu, 20 Jan 2005 21:44:20 +0000 (GMT) Received: from floppy.pyrenet.fr (floppy.pyrenet.fr [194.250.190.2]) by svr1.postgresql.org (Postfix) with ESMTP id 2F1D43A4269 for ; Thu, 20 Jan 2005 21:44:21 +0000 (GMT) Received: by floppy.pyrenet.fr (Postfix, from userid 106) id D835A319C2; Thu, 20 Jan 2005 22:44:21 +0100 (MET) From: Ron Mayer X-Newsgroups: pgsql.performance Subject: Re: PostgreSQL clustering VS MySQL clustering Date: Thu, 20 Jan 2005 13:46:06 -0800 Organization: Hub.Org Networking Services Lines: 30 Message-ID: <41F0269E.3040406@cheapcomplexdevices.com> References: <6EE64EF3AB31D5448D0007DD34EEB3412A75C9@Herge.rcsinc.local> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org To: Merlin Moncure User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en In-Reply-To: <6EE64EF3AB31D5448D0007DD34EEB3412A75C9@Herge.rcsinc.local> To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200501/349 X-Sequence-Number: 10039 Merlin Moncure wrote: > ...You need to build a bigger, faster box with lots of storage... > Clustering ... > B: will cost you more, not less Is this still true when you get to 5-way or 17-way systems? My (somewhat outdated) impression is that up to about 4-way systems they're price competitive; but beyond that, I thought multiple cheap servers scales much more afordably than large servers. Certainly at the point of a 129-CPU system I bet you're better off with a network of cheap servers. > A: a headache Agreed if you mean clustering as-in making it look like one single database to the end user. However in my experience a few years ago, if you can partition the data in a way managed by the application, it'll not only be less of a headache, but probably provide a more flexable solution. Currently I'm working on a pretty big GIS database, that we're looking to partition our data in a manner similar to the microsoft whitepaper on scaling terraserver that can be found here: http://research.microsoft.com/research/pubs/view.aspx?msr_tr_id=MSR-TR-2002-53 I think this paper is a very nice analysis of many aspects of larger-server&SAN vs. application-partitioned-clusters, including looking at cost, reliability, managability, etc. After reading that paper, we started very seriously looking into application-level partitioning.