All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Kennedy <richard@rsk.demon.co.uk>
To: fio <fio@vger.kernel.org>
Cc: Jens Axboe <jens.axboe@oracle.com>
Subject: fio mmap writes much slower than default writes
Date: Thu, 16 Jul 2009 14:40:07 +0100	[thread overview]
Message-ID: <1247751607.2689.63.camel@localhost.localdomain> (raw)

Running tests of fio write with sizes that are less than the write cache
size I'm seeing a big slow down when using mmap. I'm running the tests
on linux 2.6.31-rc* x86_64. 

Typical results with default writes :- 

fio size=300m rw=write 
  write: io=300MiB, bw=314MiB/s, iops=80,418, runt= 955msec

with mmap :- 

fio size=300m rw=write ioengine=mmap
 write: io=300MiB, bw=55,732KiB/s, iops=13,933, runt= 5512msec


Is this expected or is it indicative of a problem somewhere?

regards
Richard



             reply	other threads:[~2009-07-16 13:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 13:40 Richard Kennedy [this message]
2009-07-18  6:18 ` fio mmap writes much slower than default writes Jens Axboe
2009-07-18 13:58   ` Richard Kennedy
2009-07-18 14:20     ` Jens Axboe
2009-07-18 14:39     ` Jens Axboe
2009-07-18 14:50       ` Richard Kennedy

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=1247751607.2689.63.camel@localhost.localdomain \
    --to=richard@rsk.demon.co.uk \
    --cc=fio@vger.kernel.org \
    --cc=jens.axboe@oracle.com \
    /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.