From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: Do not use data_alloc_cluster in ssd mode
Date: Sat, 22 Jul 2017 01:21:03 +0200 [thread overview]
Message-ID: <ac54b35e-d5f0-6da2-bd55-117005ba2588@mendix.com> (raw)
In-Reply-To: <413a6ddf-b71d-678f-3c6b-a6aab6937226@gmail.com>
On 07/21/2017 05:50 PM, Austin S. Hemmelgarn wrote:
> On 2017-07-21 07:47, Hans van Kranenburg wrote:
>> [...]
>>
>> Signed-off-by: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
> Behaves as advertised, and I'm not seeing any issues in my testing (and
> I can confirm from experience that this logic slows things down, I've
> been forcing '-o nossd' on my systems for a while now for the
> performance improvement), so you can add:
> Tested-by: Austin S. Hemmelgarn <ahferroin7@gmail.com>
Thanks for testing!
Would you mind sharing a bit about what kind of test this is, and how
you measure the difference?
Does it mean that you're throwing a lot of data at the disk, and that
you can measure that 'cluster' mode of figuring out where to put the
writes has to spend more effort than the 'tetris' mode, and that it
limits the write speed?
The only relevant difference I was aware of until now is just the
placement of the writes.
--
Hans van Kranenburg
next prev parent reply other threads:[~2017-07-21 23:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 11:47 [PATCH] Btrfs: Do not use data_alloc_cluster in ssd mode Hans van Kranenburg
2017-07-21 14:49 ` Adam Borowski
2017-07-21 15:16 ` Hans van Kranenburg
2017-07-21 15:50 ` Austin S. Hemmelgarn
2017-07-21 23:21 ` Hans van Kranenburg [this message]
2017-07-24 11:23 ` Austin S. Hemmelgarn
2017-07-24 14:25 ` David Sterba
2017-07-24 17:22 ` Hans van Kranenburg
2017-07-24 17:52 ` David Sterba
2017-07-24 17:56 ` Hans van Kranenburg
2017-07-24 18:01 ` Chris Mason
2017-07-24 18:41 ` David Sterba
2017-07-24 18:53 ` Chris Mason
2017-07-24 19:06 ` Austin S. Hemmelgarn
2017-07-24 19:18 ` Chris Mason
2017-07-24 22:42 ` Hans van Kranenburg
2017-07-26 13:27 ` David Sterba
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=ac54b35e-d5f0-6da2-bd55-117005ba2588@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=ahferroin7@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).