pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Hervé Piedvache <herve@elma.fr>
To: pgsql-performance@postgresql.org
Cc: Shridhar Daithankar <shridhar@frodo.hserus.net>
Cc: Hervé Piedvache <footcow@noos.fr>
Subject: Re: Insert are going slower ...
Date: Sun, 18 Jul 2004 10:23:21 -0700
Message-ID: <200407181023.22004.josh@agliodbs.com> (raw)
In-Reply-To: <200407161317.02515.herve@elma.fr>
References: <200407131850.52095.herve@elma.fr>
	<200407151109.16466.josh@agliodbs.com>
	<200407161317.02515.herve@elma.fr>

Herve'

> Hum ... it's only for speed aspect ... I was using postgresql with this
> option since 7.01 ... and for me fsync=on was so slow ...
> Is it really no time consuming for the system to bring it ON now with
> v7.4.3 ??

Well, I wouldn't do it until you've figured out the current performance 
problem.

The issue with having fsync=off is that, if someone yanks the power cord on 
your server, there is a significant chance that you will have to restore the 
database from backup becuase it will be corrupted.   But clearly you've been 
living with that risk for some time.

It *is* true that there is significantly less performance difference between 
7.4 with fsync off and on than there was between 7.1 with fsync off and on.  
But there is still a difference.   In 7.0 and 7.1 (I think), when you turned 
fsync off it turned WAL off completely, resulting in a substantial difference 
in disk activity.   Now, it just stops checkpointing WAL but WAL is still 
recording -- meaning that disk activity decreases some but not a lot.   The 
difference is more noticable the more vulnerable to contention your disk 
system is.

The other reason not to think of fsync=off as a permanent performance tweak is 
that we're likely to remove the option sometime in the next 2 versions, since 
an increasing number of features depend on WAL behavior, and the option is 
largely a legacy of the 7.0 days, when WAL was sometimes buggy and needed to 
be turned off to get the database to start.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (17+ messages)  latest in thread

Message-ID: <200407181023.22004.josh@agliodbs.com>
Permalink:  ../200407181023.22004.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200407181023.22004.josh@agliodbs.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: josh@agliodbs.com, herve@elma.fr, shridhar@frodo.hserus.net, footcow@noos.fr
  Subject: Re: Insert are going slower ...
  In-Reply-To: <200407181023.22004.josh@agliodbs.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