Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "Michal Šmucr" <msmucr@gmail.com>
Cc: Alan Hagge <Alan.Hagge@warnerbros.com>, fio@vger.kernel.org
Subject: Re: How to re-use default sequential filenames?
Date: Mon, 8 Apr 2013 13:17:45 +0200	[thread overview]
Message-ID: <20130408111745.GC12244@kernel.dk> (raw)
In-Reply-To: <CAHBo9gn2t6khrMGBsL4omOmiFoGZzfRCOmS9KfLRmRjPa4F-3w@mail.gmail.com>

On Mon, Apr 08 2013, Michal Šmucr wrote:
> 2013/4/5 Jens Axboe <axboe@kernel.dk>:
> > and then 'write' and 'read' job would be sharing those files. Let me
> > know if it works for you.
> 
> Thank you for patch Jens.
> Re-using files working for me and i also like that string format
> specification. Compiled with last git and tested on Mac OS X and
> Centos 5.
> I played with fio and sequence tests, it already helps me to get
> figures much closer to real world utilization. I always struggled with
> generic synthetic benchmarks as it usually don't work with sequences.
> So i can roughly set IO sizes, modes, but for example can't simulate
> performance differences caused by different file allocation between
> one huge file (with few extents due to filesystem internal
> optimization) and thousands of files.
> Great!

Thanks for testing and confirming that it both works and that the
semantics make sense. I tagged 2.0.15 this morning and kept a few
pending features/fixes in a 'next' branch, all have been pulled into the
master branch. So the filename_format option is now in current -git,
though it did not make 2.0.15 final.

> P.S.: Here is what i tried as single thread HD video job. (and as
> example where application read whole frame at once, so bs is
> uncommonly equal filesize).
> 
> [global]
> ioengine=sync
> buffered=0
> filesize=8305664
> bs=8305664
> nrfiles=3000
> openfiles=1
> filename_format=HD_sequence_test.$filenum.dpx
> file_service_type=sequential
> directory=/mnt/test/io
> 
> [2min-sequence-write]
> rw=write
> 
> [2min-sequence-read]
> stonewall
> rw=read

Looks sane!

-- 
Jens Axboe


  reply	other threads:[~2013-04-08 11:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 16:28 How to re-use default sequential filenames? Alan Hagge
2013-04-04 18:19 ` Jens Axboe
2013-04-04 18:41   ` Jens Axboe
2013-04-04 23:59     ` Michal Šmucr
2013-04-05  8:40       ` Jens Axboe
2013-04-05 19:24         ` Michal Šmucr
2013-04-05 19:31           ` Jens Axboe
2013-04-05  8:39     ` Jens Axboe
2013-04-07 23:28       ` Michal Šmucr
2013-04-08 11:17         ` Jens Axboe [this message]
2013-04-10 17:46           ` Alan Hagge
2013-04-11 11:18             ` Jens Axboe
2013-04-04 18:33 ` Matt Hayward
2013-04-04 19:02   ` Carl Zwanzig

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=20130408111745.GC12244@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=Alan.Hagge@warnerbros.com \
    --cc=fio@vger.kernel.org \
    --cc=msmucr@gmail.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