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 6C2F63A4269 for ; Thu, 20 Jan 2005 21:02:05 +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 75911-01 for ; Thu, 20 Jan 2005 21:01:56 +0000 (GMT) Received: from mail.coretech.co.nz (coretech.co.nz [202.36.204.41]) by svr1.postgresql.org (Postfix) with ESMTP id 31F833A1CF7 for ; Thu, 20 Jan 2005 21:01:56 +0000 (GMT) Received: (qmail 24772 invoked from network); 20 Jan 2005 21:01:53 -0000 Received: from 218-101-14-86.paradise.net.nz (HELO ?192.168.1.11?) (218.101.14.86) by 0 with SMTP; 20 Jan 2005 21:01:53 -0000 Message-ID: <41F01D2B.9030902@coretech.co.nz> Date: Fri, 21 Jan 2005 10:05:47 +1300 From: Mark Kirkwood User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20041016 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Herv=E9_Piedvache?= Cc: Bruno Almeida do Lago , pgsql-performance@postgresql.org Subject: Re: PostgreSQL clustering VS MySQL clustering References: <005701c4ff1b$42c0ada0$e883f40a@br.gedasgrp> <200501202000.03853.herve@elma.fr> In-Reply-To: <200501202000.03853.herve@elma.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit 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/344 X-Sequence-Number: 10034 Hervé Piedvache wrote: > > > Dealing about the hardware, for the moment we have only a bi-pentium Xeon > 2.8Ghz with 4 Gb of RAM ... and we saw we had bad performance results ... so > we are thinking about a new solution with maybe several servers (server > design may vary from one to other) ... to get a kind of cluster to get better > performance ... > The poor performance may not necessarily be: i) attributable to the hardware or, ii) solved by clustering. I would recommend determining *why* you got the slowdown. A few possible reasons are: i) not vacuuming often enough, freespacemap settings too small. ii) postgresql.conf setting very non optimal. iii) index and/or data design not optimal for PG. My suspicions would start at iii). Other posters have pointed out that 250000000 records in itself is not necessarily a problem, so this sort of data size is manageable. regards Mark