Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Matthew Eaton <m.eaton82@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: Question on --buffer_compress_percentage
Date: Mon, 27 May 2013 10:21:47 +0200	[thread overview]
Message-ID: <20130527082147.GC29680@kernel.dk> (raw)
In-Reply-To: <CAF+0mvnU7GMsKrbArcECaD5Z0YtLxA6GtghQjOJtOxZHb=cxjQ@mail.gmail.com>

On Fri, May 24 2013, Matthew Eaton wrote:
> Hello fio group,
> 
> Can anyone tell me if --buffer_compress_percentage fills the buffer
> with random data and reuses that data or if it refills with random
> data for each submit?  If you want the latter behavior should you
> combine with --refill_buffers?

That is actually explained in the man page / HOWTO:

buffer_compress_percentage=int  If this is set, then fio will attempt to
                provide IO buffer content (on WRITEs) that compress to
                the specified level. Fio does this by providing a mix of
                random data and zeroes. Note that this is per block size
                unit, for file/disk wide compression level that matches
                this setting, you'll also want to set refill_buffers.

So the answer to your question is yes. Fio will reuse IO buffers, unless
--refill_buffers is set. If you do not set refill_buffers with
buffer_compress_percentage, then you will have identically compressible
blocks written. And that would only give you the per-block compression
ratio specified, on a broader scale it would compress more.

-- 
Jens Axboe


  reply	other threads:[~2013-05-27  8:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25  1:12 Question on --buffer_compress_percentage Matthew Eaton
2013-05-27  8:21 ` Jens Axboe [this message]
2013-06-02  2:11   ` Matthew Eaton
2013-06-02 12:20     ` 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=20130527082147.GC29680@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=m.eaton82@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