Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: "N. Harake" <hussein@cscs.ch>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: memory caching
Date: Tue, 15 Mar 2011 21:55:43 +0100	[thread overview]
Message-ID: <4D7FD24F.1020307@fusionio.com> (raw)
In-Reply-To: <8512BC127909424EB483ED236E6AC3C003D6E6@MBX20.d.ethz.ch>

On 2011-03-15 21:46, N. Harake wrote:
> 
> Thanks for your reply, indeed my interest to get the max iops but on a
> filesystem not a raw device, I understand the penalty but that would
> be more realstic for production systems. I will try these changes and
> keep you updated .

It's always a good idea to do the raw block device test first, that'll
at least give you an idea of the best possible result. On a file system,
you'll get the best results with O_DIRECT if the file has been
pre-allocated first. Otherwise you end up punting to buffered IO for
filling new blocks.

So that would mean adding --overwrite=1. And get rid of the O_SYNC. If
your workload will utilize lots of processes or threads, use what you
already have with a high numjobs. But an libaio with fewer threads and
higher depth will get you better performance.

-- 
Jens Axboe


  reply	other threads:[~2011-03-15 20:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15  8:27 memory caching N. Harake
2011-03-15 12:36 ` N. Harake
2011-03-15 20:28   ` Jens Axboe
2011-03-15 20:46     ` N. Harake
2011-03-15 20:55       ` Jens Axboe [this message]
2011-03-15 20:54     ` N. Harake
2011-03-15 20:56       ` Jens Axboe
2011-03-15 20:20 ` Jens Axboe

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=4D7FD24F.1020307@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=fio@vger.kernel.org \
    --cc=hussein@cscs.ch \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox