Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Jeff Furlong <jeff.furlong@hgst.com>,
	Andrey Kuzmin <andrey.v.kuzmin@gmail.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Specify range and distribution of accesses
Date: Mon, 7 Mar 2016 14:08:55 -0700	[thread overview]
Message-ID: <56DDEDE7.9020603@kernel.dk> (raw)
In-Reply-To: <BN3PR0401MB1457E708CC129BD01FE8B94EF7B10@BN3PR0401MB1457.namprd04.prod.outlook.com>

On 03/07/2016 01:46 PM, Jeff Furlong wrote:
> Thanks for the suggestions and patches.  Using the latest fio version, the JESD219 workload is possible:
>
> # fio -version
> fio-2.6-27-gd283
>
> # fio --name=JESD219 --ioengine=libaio --direct=1 --rw=randrw --norandommap --randrepeat=0 --rwmixread=40 --rwmixwrite=60 --iodepth=256 --size=100% --numjobs=4 --bssplit=512/4:1024/1:1536/1:2048/1:2560/1:3072/1:3584/1:4k/67:8k/10:16k/7:32k/3:64k/3 --random_distribution=zoned:50/5:30/15:20/80 --overwrite=1 --filename=/dev/nvme0n1 --group_reporting --runtime=5m --time_based --output=JESD219
>
> A quick statistical analysis of the results shows:
>
> Found 20380582 IOs
>
>   Found 39.9903152913% reads
>   Found 60.0096847087% writes
>
>   Found 4.00492979052% 512
>   Found 1.00495658073% 1024
>   Found 1.00079575745% 1536
>   Found 1.00046701316% 2048
>   Found 0.998764412125% 2560
>   Found 0.998043137335% 3072
>   Found 0.999520033334% 3584
>   Found 67.0145778958% 4096
>   Found 9.98662844859% 8192
>   Found 6.99898560306% 16384
>   Found 2.99961993235% 32768
>   Found 2.99271139558% 65536
>
>   Found 49.9895734086% 0-5%
>   Found 30.0126463513% 5-20%%
>   Found 19.99778024% 20-100%
>
> So we can confirm (with a reasonable tolerance) that the read/write distribution, the blocksize distribution, and the zoned distribution hold true.  Feel free to modify the fio cmd for your actual JESD219 workload (duration, logs, etc.).

Thanks for posting this Jeff, looks great!

-- 
Jens Axboe



  parent reply	other threads:[~2016-03-07 21:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 20:53 Specify range and distribution of accesses Jeff Furlong
2016-02-27  9:14 ` Andrey Kuzmin
2016-03-03 16:18   ` Jens Axboe
2016-03-03 20:04     ` Jens Axboe
2016-03-07 20:46       ` Jeff Furlong
2016-03-07 21:02         ` Andrey Kuzmin
2016-03-07 21:08           ` Jens Axboe
2016-03-08  2:41           ` Jens Axboe
2016-03-07 21:08         ` Jens Axboe [this message]
2016-03-07 21:19         ` Elliott, Robert (Persistent Memory)
2016-03-07 21:45           ` Jens Axboe
2016-03-12  2:07       ` Vladislav Bolkhovitin
2016-03-03 16:16 ` 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=56DDEDE7.9020603@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=andrey.v.kuzmin@gmail.com \
    --cc=fio@vger.kernel.org \
    --cc=jeff.furlong@hgst.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox