pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
To: Adrian Moisey <adrian@careerjunction.co.za>
Cc: pgsql-performance@postgresql.org
Subject: Re: filesystems benchmark
Date: Mon, 15 Dec 2008 15:02:39 +0300
Message-ID: <1d709ecc0812150402v62375a88y121d5515d7210cd2@mail.gmail.com> (raw)
In-Reply-To: <4945FD58.8030604@careerjunction.co.za>
References: <4945FD58.8030604@careerjunction.co.za>

>
> I'm trying to compare different filesystems for postgres using pgbench.
>  The problem I've seen is that my IO wait is very very low.  Is there a way
> I can get pgbench to do more to push that up a little?

Why do you expect to see high IO wait?

Does your database fit in system memory? If you do not modify the data and
it is not large enough, it is unlikely you will hit IO wait.

Do you have write cache enabled for the file system/device? Even if you have
some DML statements, it would not be that easy to saturate write cache
enabled storage (especially, when it fits in memory).


Regards,
Vladimir Sitnikov

view thread (3+ messages)  latest in thread

Message-ID: <1d709ecc0812150402v62375a88y121d5515d7210cd2@mail.gmail.com>
Permalink:  ../1d709ecc0812150402v62375a88y121d5515d7210cd2@mail.gmail.com/
Also on:    postgresql.org/message-id/1d709ecc0812150402v62375a88y121d5515d7210cd2@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: sitnikov.vladimir@gmail.com, adrian@careerjunction.co.za
  Subject: Re: filesystems benchmark
  In-Reply-To: <1d709ecc0812150402v62375a88y121d5515d7210cd2@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