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 225BA3A47CA for ; Thu, 20 Jan 2005 14:44:10 +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 08781-03 for ; Thu, 20 Jan 2005 14:43:57 +0000 (GMT) Received: from relay.snowman.net (relay.snowman.net [66.92.160.56]) by svr1.postgresql.org (Postfix) with ESMTP id DC7893A4741 for ; Thu, 20 Jan 2005 14:44:00 +0000 (GMT) Received: from ns.snowman.net (ns.snowman.net [10.10.0.2]) by relay.snowman.net (8.13.1/8.13.1/Debian-19) with ESMTP id j0KEhw4d018031 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 20 Jan 2005 09:43:59 -0500 Received: from ns.snowman.net (localhost [127.0.0.1]) by ns.snowman.net (8.13.1/8.13.1/Debian-19) with ESMTP id j0KEiHpk011070 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 20 Jan 2005 09:44:17 -0500 Received: (from sfrost@localhost) by ns.snowman.net (8.13.1/8.13.1/Submit) id j0KEiGTf011068; Thu, 20 Jan 2005 09:44:16 -0500 Date: Thu, 20 Jan 2005 09:44:16 -0500 From: Stephen Frost To: =?iso-8859-1?Q?Herv=E9?= Piedvache Cc: pgsql-performance@postgresql.org Subject: Re: PostgreSQL clustering VS MySQL clustering Message-ID: <20050120144416.GO10437@ns.snowman.net> Mail-Followup-To: =?iso-8859-1?Q?Herv=E9?= Piedvache , pgsql-performance@postgresql.org References: <200501201503.31241.herve@elma.fr> <20050120143045.GN10437@ns.snowman.net> <200501201539.49874.herve@elma.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="shuwmd2AqwYbirob" Content-Disposition: inline In-Reply-To: <200501201539.49874.herve@elma.fr> X-Editor: Vim http://www.vim.org/ X-Info: http://www.snowman.net X-Operating-System: Linux/2.4.24ns.3.0 (i686) X-Uptime: 09:41:02 up 355 days, 9:36, 8 users, load average: 0.19, 0.69, 0.42 User-Agent: Mutt/1.5.6+20040907i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.016 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200501/278 X-Sequence-Number: 9968 --shuwmd2AqwYbirob Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * 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, though > > I'm not sure it's to the point you need it at yet, depends on if you can > > handle some delay before an insert makes it to the slave select systems. >=20 > I think not ... pgpool or slony are replication solutions ... but as I ha= ve=20 > said to Christopher Kings-Lynne how I'll manage the scalabilty of the=20 > database ? I'll need several servers able to load a database growing and= =20 > 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. > > > 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. >=20 > But I'll arrive to limitation of a box size quickly I thing a 4 processor= s=20 > with 64 Gb of RAM ... and after ? 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 --shuwmd2AqwYbirob Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFB78PArzgMPqB3kigRAoutAJ9a+B3BgJNh09kqkWfOELn+hnK2LgCfbu0P mJzxz3WHXJ3hvOlGbKXyJpA= =iUHg -----END PGP SIGNATURE----- --shuwmd2AqwYbirob--