Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Fio 2.3 released
Date: Wed, 23 Dec 2015 09:47:46 -0700	[thread overview]
Message-ID: <567AD032.1070807@kernel.dk> (raw)
In-Reply-To: <567ACF12.1050404@kernel.dk>

On 12/23/2015 09:42 AM, Jens Axboe wrote:
> Hi,
>
> Just in time for Christmas, I've spun a new release. You might have
> noticed that it has a different numbering than expected. The previous
> release was 2.2.13, so this should have been 2.2.14. But I've decided to
> switch to a simpler versioning scheme, so we'll just bump the Y of the
> X.Y numbering going forward.
>
> As usual, report any weirdness in testing this newer release.
>
> Happy Holidays!

Shortlog of the release can be found here:

http://brick.kernel.dk/snaps/fio-2.3.shortlog.txt

Notable new features is a rewrite of the client/server message handling, 
so it should be more stable now. It should also be a bit more fault 
tolerant, it can recover from certain lost messages. It also supports 
transmitting of the logs now, so you don't have to grab those from the 
server side. If you use fio in client/server mode, testing would be great.

There's a rewrite of the hdfs IO engine.

And there's support for a new job primitive, 'wait_for'. This is a bit 
more flexible than 'stonewall' in that you can wait for specific jobs, 
instead of just inserting a barrier in your job file.

-- 
Jens Axboe



      reply	other threads:[~2015-12-23 16:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23 16:42 Fio 2.3 released Jens Axboe
2015-12-23 16:47 ` Jens Axboe [this message]

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=567AD032.1070807@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    /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