From: Mark Wong <markwkm@gmail.com>
To: Scott Carey <scott@richrelevance.com>
Cc: Greg Smith <gsmith@gregsmith.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 10:38:30 -0700
Message-ID: <70c01d1d0809101038q62e1f0ecnd2adb03ecf35ad41@mail.gmail.com> (raw)
In-Reply-To: <a1ec7d000809100926w28a4a57dy7c13f2942edc57ff@mail.gmail.com>
References: <70c01d1d0809092353r4ae687a3ycf3d99d43a5680cf@mail.gmail.com>
<Pine.GSO.4.64.0809101023520.15181@westnet.com>
<a1ec7d000809100926w28a4a57dy7c13f2942edc57ff@mail.gmail.com>
On Wed, Sep 10, 2008 at 9:26 AM, Scott Carey <scott@richrelevance.com> wrote:
> 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.
The data for the other fio profiles we've been using are on the wiki,
if your eyes can take the strain. We are working on presenting the
data in a more easily digestible manner. I don't think we'll add any
more fio profiles in the interest of moving on to doing some sizing
exercises with the dbt2 oltp workload. We're just going to wrap up a
couple more scenarios first and get through a couple of conference
presentations. The two conferences in particular are the Linux
Plumbers Conference, and the PostgreSQL Conference: West 08, which are
both in Portland, Oregon.
Regards,
Mark
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: markwkm@gmail.com, scott@richrelevance.com, gsmith@gregsmith.com, gorthx@gmail.com, selenamarie@gmail.com
Subject: Re: Effects of setting linux block device readahead size
In-Reply-To: <70c01d1d0809101038q62e1f0ecnd2adb03ecf35ad41@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