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 C9D223A48DA for ; Thu, 20 Jan 2005 17:31:02 +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 49665-03 for ; Thu, 20 Jan 2005 17:30:54 +0000 (GMT) Received: from www.postgresql.com (unknown [200.46.204.209]) by svr1.postgresql.org (Postfix) with ESMTP id 915B63A4729 for ; Thu, 20 Jan 2005 17:30:54 +0000 (GMT) Received: from mail2.dbitech.ca (radius.wavefire.com [64.141.13.252]) by www.postgresql.com (Postfix) with SMTP id E172D739219 for ; Thu, 20 Jan 2005 17:30:52 +0000 (GMT) Received: (qmail 14884 invoked from network); 20 Jan 2005 18:46:37 -0000 Received: from dbitech.wavefire.com (HELO ?64.141.15.253?) (darcy@64.141.15.253) by radius.wavefire.com with SMTP; 20 Jan 2005 18:46:37 -0000 From: Darcy Buskermolen Organization: Wavefire Technologies Corp. To: "Joshua D. Drake" Subject: Re: PostgreSQL clustering VS MySQL clustering Date: Thu, 20 Jan 2005 09:29:37 -0800 User-Agent: KMail/1.6.2 Cc: Stephen Frost , =?iso-8859-1?q?Herv=E9_Piedvache?= , pgsql-performance@postgresql.org References: <200501201503.31241.herve@elma.fr> <20050120144416.GO10437@ns.snowman.net> <41EFC514.9090806@commandprompt.com> In-Reply-To: <41EFC514.9090806@commandprompt.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200501200929.37228.darcy@wavefire.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.054 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/326 X-Sequence-Number: 10016 On January 20, 2005 06:49 am, Joshua D. Drake wrote: > Stephen Frost wrote: > >* Herv? Piedvache (herve@elma.fr) wrote: > >>Le Jeudi 20 Janvier 2005 15:30, Stephen Frost a =E9crit : > >>>* Herv? Piedvache (herve@elma.fr) wrote: > >>>>Is there any solution with PostgreSQL matching these needs ... ? > >>> > >>>You might look into pg_pool. Another possibility would be slony, thou= gh > >>>I'm not sure it's to the point you need it at yet, depends on if you c= an > >>>handle some delay before an insert makes it to the slave select system= s. > >> > >>I think not ... pgpool or slony are replication solutions ... but as I > >> have said to Christopher Kings-Lynne how I'll manage the scalabilty of > >> the database ? I'll need several servers able to load a database growi= ng > >> and growing to get good speed performance ... > > > >They're both replication solutions, but they also help distribute the > >load. For example: > > > >pg_pool will distribute the select queries amoung the servers. They'll > >all get the inserts, so that hurts, but at least the select queries are > >distributed. > > > >slony is similar, but your application level does the load distribution > >of select statements instead of pg_pool. Your application needs to know > >to send insert statements to the 'main' server, and select from the > >others. > > You can put pgpool in front of replicator or slony to get load > balancing for reads. Last time I checked load ballanced reads was only available in pgpool if yo= u=20 were using pgpools's internal replication. Has something changed recently? > > >>>>Is there any other solution than a Cluster for our problem ? > >>> > >>>Bigger server, more CPUs/disks in one box. Try to partition up your > >>>data some way such that it can be spread across multiple machines, then > >>>if you need to combine the data have it be replicated using slony to a > >>>big box that has a view which joins all the tables and do your big > >>>queries against that. > >> > >>But I'll arrive to limitation of a box size quickly I thing a 4 > >> processors with 64 Gb of RAM ... and after ? > > Opteron. IBM Z-series, or other big iron. > > >Go to non-x86 hardware after if you're going to continue to increase the > >size of the server. Personally I think your better bet might be to > >figure out a way to partition up your data (isn't that what google > >does anyway?). > > > > Stephen =2D-=20 Darcy Buskermolen Wavefire Technologies Corp. ph: 250.717.0200 fx: 250.763.1759 http://www.wavefire.com