All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erwan Velu <erwan@enovance.com>
To: Kim Holmebakken <kim.holmebakken@hotmail.com>
Cc: fio@vger.kernel.org
Subject: Re: Fio giving iops results that are equal to RAM speeds
Date: Wed, 07 May 2014 10:02:14 +0200	[thread overview]
Message-ID: <5369E886.1030100@enovance.com> (raw)
In-Reply-To: <BLU436-SMTP9791A8BB35991D92CA0E06E54E0@phx.gbl>


Le 07/05/2014 09:45, Kim Holmebakken a �crit :
> Hey,
>
> Im currently working on a bachelor thesis where I need to measure iops 
> on my storage solution.
>
> I have set up a "frontend" server(ubuntu server 13.10) which has zfs 
> on linux running, and is connected to an iSCSI RAID(SAN).
>
> When I use this command:
>
> fio --directory=/pool  --size=128M --direct=0 --fallocate=none 
> --rw=randrw --refill_buffers --norandommap --randrepeat=0 
> --ioengine=sync --bs=4k --rwmixread=100 --iodepth=16 --numjobs=16 
> --runtime=60 --group_reporting --name=4krandreadtest

[...]
> These values are extremly high and I suspect that these are the RAM 
> speed being returned to me.
>
> Is there anyway to get a more realistic result?

You do cached IOs (as direct=0), only 128M of data and everything into a 
file. As a result, yes everything is getting into the host's cache.

If you want to determine the ISCSI performance byitself, I suggest not 
using file but the block device and do direct IOs (direct=1).

If you want to keep your filesystem you have two options : enabling the 
direct=1 and/or making IOs at twice the size of your host memory.

Hope this helps,
Erwan

  reply	other threads:[~2014-05-07  8:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07  7:45 Fio giving iops results that are equal to RAM speeds Kim Holmebakken
2014-05-07  8:02 ` Erwan Velu [this message]
     [not found]   ` <BLU436-SMTP1086A621DD12787F2EECD40E54E0@phx.gbl>
2014-05-07  8:27     ` Erwan Velu
     [not found]       ` <BLU436-SMTP218F8CEFE3A8ED088644478E54E0@phx.gbl>
2014-05-07  9:12         ` Erwan Velu
2014-05-07 14:21       ` Jens Axboe
2014-05-07  8:10 ` puvi

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=5369E886.1030100@enovance.com \
    --to=erwan@enovance.com \
    --cc=fio@vger.kernel.org \
    --cc=kim.holmebakken@hotmail.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.