From: Roman Mamedov <rm@romanrm.ru>
To: "Michael Kjörling" <michael@kjorling.se>
Cc: cwillu <cwillu@cwillu.com>,
Ahmet Inan <ainan@mathematik.uni-freiburg.de>,
linux-btrfs@vger.kernel.org
Subject: Re: Why btrfs inline small file by default?
Date: Wed, 31 Oct 2012 19:44:11 +0600 [thread overview]
Message-ID: <20121031194411.3ee694f5@natsu> (raw)
In-Reply-To: <20121031115639.GB26070@yeono.kjorling.se>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
On Wed, 31 Oct 2012 11:56:39 +0000
Michael Kjörling <michael@kjorling.se> wrote:
> On 31 Oct 2012 04:57 -0600, from cwillu@cwillu.com (cwillu):
> > 9.08GB + 992.48MB*2 == 11.02GB
> >
> > 10.85GB + 518MB*2 == 11.86GB
> >
> > That's nearly a GB smaller.
>
> That, too; I missed the "DUP". Not quite as pronounced as in my
> calculations, then, but still a significant enough difference.
There is also a number of cases which justify disabling DUP for metadata, e.g.
- underlying block device is an internally deduplicating SSD (i.e. possibly
most of them)
- or the block device is a RAID incorporating redundancy
- or simply one wants increase performance at the cost of some reliability
With non-DUP metadata your calculations showing inlining being more efficient
remain correct.
--
With respect,
Roman
~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-10-31 13:53 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 11:04 Why btrfs inline small file by default? ching
2012-10-30 12:04 ` Felix Pepinghege
2012-10-30 12:17 ` cwillu
2012-10-30 21:40 ` ching
2012-10-30 22:14 ` Hugo Mills
2012-10-30 22:19 ` Hugo Mills
2012-10-30 23:47 ` ching
2012-10-31 0:12 ` David Sterba
2012-10-31 21:07 ` ching
2012-10-31 0:18 ` cwillu
2012-10-31 8:48 ` Ahmet Inan
2012-10-31 9:39 ` cwillu
2012-10-31 10:48 ` Ahmet Inan
2012-10-31 10:55 ` Michael Kjörling
2012-10-31 11:10 ` Ahmet Inan
2012-10-31 10:57 ` cwillu
2012-10-31 11:56 ` Michael Kjörling
2012-10-31 13:27 ` Ahmet Inan
2012-10-31 13:44 ` Roman Mamedov [this message]
2012-10-31 21:05 ` ching
2012-10-30 22:16 ` cwillu
2012-10-30 23:41 ` ching
2012-10-30 21:39 ` ching
2012-10-30 12:11 ` Felix Pepinghege
2012-10-30 12:13 ` Mitch Harder
2012-10-30 16:38 ` 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=20121031194411.3ee694f5@natsu \
--to=rm@romanrm.ru \
--cc=ainan@mathematik.uni-freiburg.de \
--cc=cwillu@cwillu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=michael@kjorling.se \
/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).