From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Using Btrfs on single drives
Date: Thu, 26 Nov 2015 16:27:44 +0000 (UTC) [thread overview]
Message-ID: <pan$aef24$6d93700d$fffc9f7c$ca227eb6@cox.net> (raw)
In-Reply-To: 201511251820.25758.russell@coker.com.au
Russell Coker posted on Wed, 25 Nov 2015 18:20:25 +1100 as excerpted:
> On Sun, 15 Nov 2015 03:01:57 PM Duncan wrote:
>> That looks to me like native drive limitations.
>>
>> Due to the fact that a modern hard drive spins at the same speed no
>> matter where the read/write head is located, when it's reading/writing
>> to the first part of the drive -- the outside -- much more linear drive
>> distance will pass under the read/write heads in say a tenth of a
>> second than will be the case as the last part of the drive is filled --
>> the inside -- and throughput will be much higher at the first of the
>> drive.
>
> http://www.coker.com.au/bonnie++/zcav/results.html
>
> The above page has the results of my ZCAV benchmark (part of the
> Bonnie++ suite) which shows this. You can safely tun ZCAV in read mode
> on a device that's got a filesystem on it so it's not too late to test
> these things.
Thanks. Those graphs are pretty clear.
As you, I'd have thought there'd be far fewer zones (3-4) than it turns
out there are (8ish).
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2015-11-26 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 10:43 Using Btrfs on single drives audio muze
2015-11-14 11:09 ` Goffredo Baroncelli
2015-11-14 16:35 ` Duncan
2015-11-15 3:27 ` audio muze
2015-11-15 4:01 ` Duncan
2015-11-15 6:30 ` Marc Joliet
2015-11-25 7:20 ` Russell Coker
2015-11-26 16:27 ` Duncan [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='pan$aef24$6d93700d$fffc9f7c$ca227eb6@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@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