pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Carey <scott@richrelevance.com>
To: Greg Smith <gsmith@gregsmith.com>
Cc: Mark Wong <markwkm@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Cc: Gabrielle Roth <gorthx@gmail.com>
Cc: Selena Deckelmann <selenamarie@gmail.com>
Subject: Re: Effects of setting linux block device readahead size
Date: Wed, 10 Sep 2008 09:26:25 -0700
Message-ID: <a1ec7d000809100926w28a4a57dy7c13f2942edc57ff@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.64.0809101023520.15181@westnet.com>
References: <70c01d1d0809092353r4ae687a3ycf3d99d43a5680cf@mail.gmail.com>
	<Pine.GSO.4.64.0809101023520.15181@westnet.com>

How does that readahead tunable affect random reads or mixed random /
sequential situations?  In many databases, the worst case scenarios aren't
when you have a bunch of concurrent sequential scans but when there is
enough random read/write concurrently to slow the whole thing down to a
crawl.   How the file system behaves under this sort of concurrency

I would be very interested in a mixed fio profile with a "background writer"
doing moderate, paced random and sequential writes combined with concurrent
sequential reads and random reads.

-Scott

On Wed, Sep 10, 2008 at 7:49 AM, Greg Smith <gsmith@gregsmith.com> wrote:

> On Tue, 9 Sep 2008, Mark Wong wrote:
>
>  I've started to display the effects of changing the Linux block device
>> readahead buffer to the sequential read performance using fio.
>>
>
> Ah ha, told you that was your missing tunable.  I'd really like to see the
> whole table of one disk numbers re-run when you get a chance.  The reversed
> ratio there on ext2 (59MB read/92MB write) was what tipped me off that
> something wasn't quite right initially, and until that's fixed it's hard to
> analyze the rest.
>
> Based on your initial data, I'd say that the two useful read-ahead settings
> for this system are 1024KB (conservative but a big improvement) and 8192KB
> (point of diminishing returns).  The one-disk table you've got (labeled with
> what the default read-ahead is) and new tables at those two values would
> really flesh out what each disk is capable of.
>
> --
> * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
>
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>

view thread (27+ messages)  latest in thread

Message-ID: <a1ec7d000809100926w28a4a57dy7c13f2942edc57ff@mail.gmail.com>
Permalink:  ../a1ec7d000809100926w28a4a57dy7c13f2942edc57ff@mail.gmail.com/
Also on:    postgresql.org/message-id/a1ec7d000809100926w28a4a57dy7c13f2942edc57ff@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: scott@richrelevance.com, gsmith@gregsmith.com, markwkm@gmail.com, gorthx@gmail.com, selenamarie@gmail.com
  Subject: Re: Effects of setting linux block device readahead size
  In-Reply-To: <a1ec7d000809100926w28a4a57dy7c13f2942edc57ff@mail.gmail.com>
  References: <70c01d1d0809092353r4ae687a3ycf3d99d43a5680cf@mail.gmail.com> <Pine.GSO.4.64.0809101023520.15181@westnet.com> <a1ec7d000809100926w28a4a57dy7c13f2942edc57ff@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