From: Troels Arvin <troels@arvin.dk>
To: fio@vger.kernel.org
Subject: Re: Does fio write only 0x00s?
Date: Tue, 16 Mar 2010 00:19:10 +0100 [thread overview]
Message-ID: <4B9EC06E.2000101@arvin.dk> (raw)
In-Reply-To: <20100315212219.GQ5768@kernel.dk>
Hello,
On Mar 15, Jens Axboe wrote:
> By default, fio will at init time randomly fill the buffer of the
> allocated IO units. If you are using the sync io engine, then only one
> buffer will be allocated and that will be repeatedly written. So yes,
> that'll compress very nicely.
I'm using libaio. So the data from that shouldn't compress all that much?
> You can enable refill_buffers=1 and
> that'll cause fio to randomly fill it everytime it's submitted instead.
> That should effectively disable compression at the storage end.
Turning refill_buffers on or off doesn't seem to make much of a
difference when compressing fil's work-file with "gzip -2" (201MB vs
198MB). But perhaps, "gzip -2" still compreses more than one can expect
from a storage system?
I'm probably missing something. Here's the job description file I'm
using (in this case only testing a small amount of I/O; when I was
testing the storage systems, I used size=10g and six numjobs=6):
===========================================================
[global]
description=Emulation of Intel IOmeter File Server Access Pattern
[iometer]
bssplit=512/10:1k/5:2k/5:4k/60:8k/2:16k/4:32k/4:64k/10
rw=randrw
rwmixread=70
direct=1
size=1g
ioengine=libaio
iodepth=256
refill_buffers=0
===========================================================
--
Regards,
Troels Arvin <troels@arvin.dk>
http://troels.arvin.dk/
next prev parent reply other threads:[~2010-03-15 23:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 20:50 Does fio write only 0x00s? Troels Arvin
2010-03-15 21:22 ` Jens Axboe
2010-03-15 23:19 ` Troels Arvin [this message]
2010-03-16 8:05 ` Jens Axboe
2010-03-16 11:27 ` Troels Arvin
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=4B9EC06E.2000101@arvin.dk \
--to=troels@arvin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.