All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Libor Klepáč" <libor.klepac@bcom.cz>
To: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs send to send out metadata and data separately
Date: Fri, 29 Jul 2016 13:14:44 +0000	[thread overview]
Message-ID: <8930800.y3r4nzIv9U@libor-nb> (raw)
In-Reply-To: <07e7aea4-ebc7-1c47-34fb-daaae42ab245@gmx.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 878 bytes --]

Hello,

just a little question on receiver point 0), see bellow

Dne pátek 29. července 2016 20:40:38 CEST, Qu Wenruo napsal(a):
> Hi Filipe, and maintainers,
> 
> Receive will do the following thing first before recovering the
> subvolume/snapshot:
> 
> 0) Create temporary dir for data extents
>     Create a new dir with temporary name($data_extent), to put data
> extents into it.

These are the directories in format "o4095916-21925-0" on receiver side?

I'm in middle of send/receive and i have over 300 thousand of them already.
I was always told, that directory with lots of items suffers on performance 
(but i newer used btrfs before :), is that true?

Should it be little structured (subdirs based on extent number, for example) ?

Libor
ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±ý»k~ÏâžØ^n‡r¡ö¦zË\x1aëh™¨è­Ú&£ûàz¿äz¹Þ—ú+€Ê+zf£¢·hšˆ§~†­†Ûiÿÿïêÿ‘êçz_è®\x0fæj:+v‰¨þ)ߣøm

  reply	other threads:[~2016-07-29 13:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29 12:40 Btrfs send to send out metadata and data separately Qu Wenruo
2016-07-29 13:14 ` Libor Klepáč [this message]
2016-08-01  1:22   ` Qu Wenruo
2016-07-30 18:49 ` g.btrfs
2016-08-01  1:39   ` Qu Wenruo
2016-08-01 18:00 ` Filipe Manana
2016-08-02  1:20   ` Qu Wenruo
2016-08-03  9:05     ` Filipe Manana
2016-08-04  1:52       ` Qu Wenruo
2016-08-24  2:36         ` Qu Wenruo
2016-08-24  8:53           ` Filipe Manana

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=8930800.y3r4nzIv9U@libor-nb \
    --to=libor.klepac@bcom.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.