All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: AIO, FIO and Threads ...
Date: Wed, 21 Mar 2007 08:40:14 +0100	[thread overview]
Message-ID: <20070321074014.GD14389@kernel.dk> (raw)
In-Reply-To: <Pine.LNX.4.64.0703202146570.28960@alien.or.mcafeemobile.com>

On Tue, Mar 20 2007, Davide Libenzi wrote:
> 
> I was looking at Jens FIO stuff, and I decided to cook a quick patch for 
> FIO to support GUASI (Generic Userspace Asyncronous Syscall Interface):
> 
> http://www.xmailserver.org/guasi-lib.html
> 
> I then ran a few tests on my Dual Opteron 252 with SATA drives (sata_nv) 
> and 8GB of RAM.
> Mind that I'm not FIO expert, like at all, but I got some interesting 
> results when comparing GUASI with libaio at 8/1000/10000 depths.
> If I read those result correctly (Jens may help), GUASI output is more 
> then double the libaio one.
> Lots of context switches, yes. But the throughput looks like 2+ times.
> Can someone try to repeat the measures and/or spot the error?
> Or tell me which other tests to run?
> This is kinda a suprise for me ...

I don't know guasi at all, but libaio requires O_DIRECT to be async. I'm
sure you know this, but you may not know that fio default to buffered IO
so you have to tell it to use O_DIRECT :-)

So try adding a --direct=1 (or --buffered=0, same thing) as an extra
option when comparing depths > 1.

I'll add your guasi engine, but disable it. Unfortunately fio still
doesn't have a nifty configure setup, so these things are still
manual...

-- 
Jens Axboe


  parent reply	other threads:[~2007-03-21  7:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21  4:58 AIO, FIO and Threads Davide Libenzi
2007-03-21  6:54 ` Davide Libenzi
2007-03-21  7:40 ` Jens Axboe [this message]
2007-03-21 15:23   ` Davide Libenzi
2007-03-22  6:47     ` Jens Axboe
2007-03-22  2:02   ` Davide Libenzi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070321074014.GD14389@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=davidel@xmailserver.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.