pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mark Wong <markwkm@gmail.com>
To: Josh Berkus <josh@agliodbs.com>
Cc: Greg Smith <greg@2ndquadrant.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-performance@postgresql.org, Albe Laurenz <laurenz.albe@wien.gv.at>
Subject: Re: Linux I/O tuning: CFQ vs. deadline
Date: Mon, 8 Feb 2010 17:14:03 -0800
Message-ID: <70c01d1d1002081714n637a5739wddb5260e25eed3bc@mail.gmail.com> (raw)
In-Reply-To: <4B704EA0.3050906@agliodbs.com>
References: <4B6FDD26.9010106@2ndquadrant.com>
	<D960CB61B694CF459DCFB4B0128514C203938157@exadv11.host.magwien.gv.at>
	<4B6FD868020000250002F084@gw.wicourts.gov>
	<4B702E05.1000708@2ndquadrant.com>
	<4B704EA0.3050906@agliodbs.com>

On Mon, Feb 8, 2010 at 9:49 AM, Josh Berkus <josh@agliodbs.com> wrote:
>
>> That's basically what I've been trying to make clear all along:  people
>> should keep an open mind, watch what happens, and not make any
>> assumptions.  There's no clear cut preference for one scheduler or the
>> other in all situations.  I've seen CFQ do much better, you and Albe
>> report situations where the opposite is true.  I was just happy to see
>> another report of someone running into the same sort of issue I've been
>> seeing, because I didn't have very much data to offer about why the
>> standard advice of "always use deadline for a database app" might not
>> apply to everyone.
>
> Damn, you would have to make things complicated, eh?
>
> FWIW, back when deadline was first introduced Mark Wong did some tests
> and found Deadline to be the fastest of 4 on DBT2 ... but only by about
> 5%.  If the read vs. checkpoint analysis is correct, what was happening
> is the penalty for checkpoints on deadline was almost wiping out the
> advantage for reads, but not quite.
>
> Those tests were also done on attached storage.
>
> So, what this suggests is:
> reads:  deadline > CFQ
> writes: CFQ > deadline
> attached storage:  deadline > CFQ
>
> Man, we'd need a lot of testing to settle this.  I guess that's why
> Linux gives us the choice of 4 ...

I wonder what the impact is from the underlying RAID configuration.
Those DBT2 tests were also LVM striped volumes on top of single RAID0
LUNS (no jbod option).

Regards.
Mark



view thread (20+ messages)  latest in thread

Message-ID: <70c01d1d1002081714n637a5739wddb5260e25eed3bc@mail.gmail.com>
Permalink:  ../70c01d1d1002081714n637a5739wddb5260e25eed3bc@mail.gmail.com/
Also on:    postgresql.org/message-id/70c01d1d1002081714n637a5739wddb5260e25eed3bc@mail.gmail.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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: markwkm@gmail.com, josh@agliodbs.com, greg@2ndquadrant.com, Kevin.Grittner@wicourts.gov, laurenz.albe@wien.gv.at
  Subject: Re: Linux I/O tuning: CFQ vs. deadline
  In-Reply-To: <70c01d1d1002081714n637a5739wddb5260e25eed3bc@mail.gmail.com>
  References: <4B6FDD26.9010106@2ndquadrant.com> <D960CB61B694CF459DCFB4B0128514C203938157@exadv11.host.magwien.gv.at> <4B6FD868020000250002F084@gw.wicourts.gov> <4B702E05.1000708@2ndquadrant.com> <4B704EA0.3050906@agliodbs.com> <70c01d1d1002081714n637a5739wddb5260e25eed3bc@mail.gmail.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