pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Marty Scholes <marty@outputservices.com>
To: Olivier Sirven <osirven@elma.fr>
Cc: herve@elma.fr, pgsql-performance@postgresql.org, Marty Scholes <marty@outputservices.com>
Subject: Re: PostgreSQL clustering VS MySQL clustering
Date: Mon, 31 Jan 2005 08:24:55 -0700
Message-ID: <41FE4DC7.7060903@outputservices.com> (raw)
References: <41F144FE.30902@outputservices.com>
	<41F14758.4030602@outputservices.com>
	<200501311616.07955.osirven@elma.fr>

 > 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 
benchmarking with 8.0 under Solaris, I am convinced that our major choke 
point is WAL synchronization, at least for applications with a high 
commit rate.

We have noticed a substantial improvement in performance with 8.0 vs 
7.4.6.  All of the update/insert problems seem to have gone away, save 
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 écrit :
> 
>>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.  Also
>>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.
> 
> Tell me if I am wrong but it sounds to me like like an endless problem....This 
> solution may work with small indexes (less than 4GB) but what appends when 
> the indexes grow ? You would add more memory to your server ? But there will 
> be a moment were you can not add more so what's next ?






view thread (131+ messages)  latest in thread

Message-ID: <41FE4DC7.7060903@outputservices.com>
Permalink:  ../41FE4DC7.7060903@outputservices.com/
Also on:    postgresql.org/message-id/41FE4DC7.7060903@outputservices.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: marty@outputservices.com, osirven@elma.fr
  Subject: Re: PostgreSQL clustering VS MySQL clustering
  In-Reply-To: <41FE4DC7.7060903@outputservices.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox