From: Troels Arvin <troels@arvin.dk>
To: fio@vger.kernel.org
Subject: Re: Does fio write only 0x00s?
Date: Tue, 16 Mar 2010 12:27:33 +0100 [thread overview]
Message-ID: <4B9F6B25.7070807@arvin.dk> (raw)
In-Reply-To: <20100316080528.GX5768@kernel.dk>
Hello,
Den 16-03-2010 09:05, skrev Jens Axboe:
> I think what you are missing is that the random writes will create a
> large sparse file. The Output is 10G, and you are doing a lot of reads.
> So you could end up writing only 30% of the 10G, the rest would be
> sparse holes in the file.
Yes, that part about the file sparseness was I had to grasp.
Expressed in another way: If I filter out the null-bytes from fio's
work-file (cat iometer.1.0 | tr -d '\0'), then the remainder doesn't
compress at all using gzip with default options.
So I'll stop worrying about storage-side compression/de-duplication when
interpreting fio's results.
Thanks.
--
Regards,
Troels Arvin <troels@arvin.dk>
http://troels.arvin.dk/
prev parent reply other threads:[~2010-03-16 11:27 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
2010-03-16 8:05 ` Jens Axboe
2010-03-16 11:27 ` Troels Arvin [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=4B9F6B25.7070807@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox