pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mark Wong <markwkm@gmail.com>
To: Greg Smith <gsmith@gregsmith.com>
Cc: Scott Carey <scott@richrelevance.com>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: henk de wit <henk53602@hotmail.com>
Cc: jesper@krogh.cc <jesper@krogh.cc>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Cc: Selena Deckelmann <selenamarie@gmail.com>
Cc: Gabrielle Roth <gorthx@gmail.com>
Subject: Re: Using IOZone to simulate DB access patterns
Date: Sat, 11 Apr 2009 11:44:33 -0700
Message-ID: <70c01d1d0904111144m50c569bbh7dc32f2bce36195e@mail.gmail.com> (raw)
In-Reply-To: <alpine.GSO.2.01.0904101359490.21946@westnet.com>
References: <C604CBE2.4856%scott@richrelevance.com>
	<alpine.GSO.2.01.0904101359490.21946@westnet.com>

On Fri, Apr 10, 2009 at 11:01 AM, Greg Smith <gsmith@gregsmith.com> wrote:
> On Fri, 10 Apr 2009, Scott Carey wrote:
>
>> FIO with profiles such as the below samples are easy to set up
>
> There are some more sample FIO profiles with results from various
> filesystems at
> http://wiki.postgresql.org/wiki/HP_ProLiant_DL380_G5_Tuning_Guide

There's a couple of potential flaws I'm trying to characterize this
weekend.  I'm having second thoughts about how I did the sequential
read and write profiles.  Using multiple processes doesn't let it
really do sequential i/o.  I've done one comparison so far resulting
in about 50% more throughput using just one process to do sequential
writes.  I just want to make sure there shouldn't be any concern for
being processor bound on one core.

The other flaw is having a minimum run time.  The max of 1 hour seems
to be good to establishing steady system utilization, but letting some
tests finish in less than 15 minutes doesn't provide "good" data.
"Good" meaning looking at the time series of data and feeling
confident it's a reliable result.  I think I'm describing that
correctly...

Regards,
Mark



view thread (22+ messages)  latest in thread

Message-ID: <70c01d1d0904111144m50c569bbh7dc32f2bce36195e@mail.gmail.com>
Permalink:  ../70c01d1d0904111144m50c569bbh7dc32f2bce36195e@mail.gmail.com/
Also on:    postgresql.org/message-id/70c01d1d0904111144m50c569bbh7dc32f2bce36195e@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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: markwkm@gmail.com, gsmith@gregsmith.com, scott@richrelevance.com, josh@agliodbs.com, henk53602@hotmail.com, jesper@krogh.cc, selenamarie@gmail.com, gorthx@gmail.com
  Subject: Re: Using IOZone to simulate DB access patterns
  In-Reply-To: <70c01d1d0904111144m50c569bbh7dc32f2bce36195e@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