pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: PFC <lists@peufeu.com>
To: Chris <dmagick@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Postgres Benchmark Results
Date: Mon, 28 May 2007 08:41:51 +0200
Message-ID: <op.ts0x71w7cigqcu@apollo13> (raw)
In-Reply-To: <465A522C.4030701@gmail.com>
References: <op.tsmrv71ecigqcu@apollo13>
	<87hcq5l1c7.fsf@oxford.xeocode.com>
	<op.tsp3u1becigqcu@apollo13>
	<465A522C.4030701@gmail.com>

On Mon, 28 May 2007 05:53:16 +0200, Chris <dmagick@gmail.com> wrote:

>
>>     I am re-running it with other tuning, notably cost-based vacuum  
>> delay and less frequent checkpoints, and it is a *lot* smoother.
>>     These take a full night to run, so I'll post more results when I  
>> have usefull stuff to show.
>>     This has proven to be a very interesting trip to benchmarkland...
>
> [ rather late in my reply but I had to ]
>
> Are you tuning mysql in a similar fashion ?

	Well, the tuning knobs are different, there are no check points or  
vacuum... but yes I tried to tune MySQL too, but the hardest part was  
simply making it work without deadlocking continuously.
	





view thread (29+ messages)  latest in thread

Message-ID: <op.ts0x71w7cigqcu@apollo13>
Permalink:  ../op.ts0x71w7cigqcu@apollo13/
Also on:    postgresql.org/message-id/op.ts0x71w7cigqcu@apollo13

 · 

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: lists@peufeu.com, dmagick@gmail.com
  Subject: Re: Postgres Benchmark Results
  In-Reply-To: <op.ts0x71w7cigqcu@apollo13>

* 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