From: Jens Axboe <axboe@kernel.dk>
To: Matthew Eaton <m.eaton82@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: Possible bug when setting compression
Date: Fri, 14 Mar 2014 14:56:43 -0600 [thread overview]
Message-ID: <53236D0B.5040507@kernel.dk> (raw)
In-Reply-To: <CAF+0mv=q-nEGkeQdJgwH78_3n6novRHAWfRwp=QHa8dFinYd3Q@mail.gmail.com>
On 03/14/2014 02:53 PM, Matthew Eaton wrote:
>> So that wont work as-is, since the parser will bypass the store when the
>> callback is specified. It needs a one-liner, please try this updated one
>> instead.
>>
>> --
>> Jens Axboe
>>
>
> Ok, so it looks like everything works now except for zero_buffers.
>
> fio-2.1.6.1-11-g0574 + patch
>
> buffer_compress_percentage=100
> iops=83457
>
> buffer_compress_percentage=50
> iops=78836
>
> buffer_compress_percentage=1
> iops=52785
>
> buffer_compress_percentage=0
> iops=51013
>
> zero_buffers
> iops=69465
>
> scramble_buffers=0
> zero_buffers
> iops=83451
zero_buffers and buffer_compres_percentage=100 are essentially the same
thing, for both cases it writes buffers just fill of zeroes. So I'm not
sure what you were expecting here since you don't think it works as it
should?
If you have both zero_buffers and scramble set, then the result will be
a bit less compressible. The goal of scramble_buffers is to defeat basic
dedupe attempts. So even if you don't fully refill your buffers every
time, the blocks will be a bit different.
--
Jens Axboe
next prev parent reply other threads:[~2014-03-14 20:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 15:52 Possible bug when setting compression Matthew Eaton
2014-03-14 18:26 ` Jens Axboe
2014-03-14 19:45 ` Matthew Eaton
2014-03-14 20:09 ` Jens Axboe
2014-03-14 20:23 ` Jens Axboe
2014-03-14 20:53 ` Matthew Eaton
2014-03-14 20:56 ` Jens Axboe [this message]
2014-03-14 21:06 ` Matthew Eaton
2014-03-14 21:33 ` Jens Axboe
2014-03-14 22:26 ` Matthew Eaton
2014-03-15 1:39 ` 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=53236D0B.5040507@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