From: "Lakshmipathi.G" <lakshmipathi.g@giis.co.in>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Large no.of extents for a single small file with a fresh RAID5 setup
Date: Tue, 21 Feb 2017 15:44:01 +0530 [thread overview]
Message-ID: <20170221101401.GA5498@giis.co.in> (raw)
In-Reply-To: <1b567b5e-8035-33ce-ddd2-2e19065044c6@cn.fujitsu.com>
>
> >I'm using Ubuntu(16.04) desktop version (not server) running Xorg and others. May be its possible its
> >flushing data to disk at constant time. If you like to give it a try again with servers, below is the
> >exact script along with its timing & multiextent output.
>
> Archlinux here, with my btrfs vm and browser and music player, still one
> extent.
>
looks like I have better setup to produce single-extent files than yours :-)
> Are you under heavy memory usage?
>
no, not as per top and free. 'top' shows mem.usage as:
KiB Mem : 7092516 total, 5961796 free, 794836 used, 335884 buff/cache
where 'compiz' process uses around 2.5% of memory and 'free' command reports
almost 5gb as free. May be some 'sysctl' or others needs to be adjusted on my setup?
> >
> >one more curious thing, is it fine to have extents with size 4096 on RAID5 setup?
> >
>
> Sure, why not?
>
> Any size aligned to sector size is valid, no matter the profile.
>
> For 4K extent, RAID5/6 will do read-modify-write, which is very common.
>
> Thanks,
> Qu
>
While looking into mapping from logical->physical chunks on RAID5. I was wondering
how these 4KB extents will fit into 64KB data-stripe?
I didn't have idea about read-modify-write, just found few wiki links on it, will
check. thanks
Cheers.
Lakshmipathi.G
prev parent reply other threads:[~2017-02-21 10:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 2:07 Large no.of extents for a single small file with a fresh RAID5 setup Lakshmipathi.G
[not found] ` <678a9608-8f42-119c-7fd3-69fbae31bfab@cn.fujitsu.com>
2017-02-20 14:07 ` Lakshmipathi.G
[not found] ` <af2aba3e-467d-6546-e9a0-e8bcc460fbd2@cn.fujitsu.com>
2017-02-21 9:22 ` Lakshmipathi.G
[not found] ` <1b567b5e-8035-33ce-ddd2-2e19065044c6@cn.fujitsu.com>
2017-02-21 10:14 ` Lakshmipathi.G [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=20170221101401.GA5498@giis.co.in \
--to=lakshmipathi.g@giis.co.in \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@cn.fujitsu.com \
/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).