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 477198B9C54 for ; Mon, 31 Jan 2005 15:36:07 +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 86225-06 for ; Mon, 31 Jan 2005 15:35:51 +0000 (GMT) Received: from outputservices.com (outputt1130.customer.frii.net [216.17.159.130]) by svr1.postgresql.org (Postfix) with ESMTP id 576158B9C47 for ; Mon, 31 Jan 2005 15:25:02 +0000 (GMT) Received: from outputservices.com (outputservices.com [137.106.76.15]) by outputservices.com (8.10.2+Sun/8.11.3) with ESMTP id j0VFOuJ07698; Mon, 31 Jan 2005 08:24:56 -0700 (MST) Message-ID: <41FE4DC7.7060903@outputservices.com> Date: Mon, 31 Jan 2005 08:24:55 -0700 From: Marty Scholes User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:0.9.9) Gecko/20020517 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Olivier Sirven Cc: herve@elma.fr, pgsql-performance@postgresql.org, Marty Scholes Subject: Re: PostgreSQL clustering VS MySQL clustering References: <41F144FE.30902@outputservices.com> <41F14758.4030602@outputservices.com> <200501311616.07955.osirven@elma.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.05 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200501/631 X-Sequence-Number: 10321 > Tell me if I am wrong but it sounds to me like like > an endless problem.... Agreed. Such it is with caching. After doing some informal=20 benchmarking with 8.0 under Solaris, I am convinced that our major choke = point is WAL synchronization, at least for applications with a high=20 commit rate. We have noticed a substantial improvement in performance with 8.0 vs=20 7.4.6. All of the update/insert problems seem to have gone away, save=20 WAL syncing. I may have to take back what I said about indexes. Olivier Sirven wrote: > Le Vendredi 21 Janvier 2005 19:18, Marty Scholes a =E9crit : >=20 >>The indexes can be put on a RAM disk tablespace and that's the end of >>index problems -- just make sure you have enough memory available. Als= o >>make sure that the machine can restart correctly after a crash: the >>tablespace is dropped and recreated, along with the indexes. This will= >>cause a machine restart to take some time. >=20 > Tell me if I am wrong but it sounds to me like like an endless problem.= =2E..This=20 > solution may work with small indexes (less than 4GB) but what appends w= hen=20 > the indexes grow ? You would add more memory to your server ? But there= will=20 > be a moment were you can not add more so what's next ?