linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fadhil Kurnia <fikurnia@cs.umass.edu>
To: linux-btrfs@vger.kernel.org
Subject: The complexity of btrfs incremental send vs rsync in batch mode
Date: Wed, 26 Jul 2023 14:03:35 -0400	[thread overview]
Message-ID: <3e6376bf18be789f8f1cefa6970c9c1b@cs.umass.edu> (raw)

Hi btrfs developer,

I am using btrfs-send with the hope that it has logarithmic
complexity compared to linear complexity of rsync in batch mode.

In rsync, to compare what changes between two directory
(or files), it needs to do a linear scan in both the original
and the copy directory to get the differences between them.

In incremental btrfs-send, my expectation is that it can compare
two subvolumes in logarithmic complexity (not linear) since under
the hood the subvolumes are represented in B+Tree; both subvolumes
(snapshots) also share many blocks in the tree. The expected
complexity is logarithmic as in the comparison between
two merkle-tree.

Could anyone confirm my expectation that btrfs-send run in
logarithmic complexity is correct?

Thanks,
Fadhil I. Kurnia
CS PhD Candidate,
University of Massachusetts Amherst

                 reply	other threads:[~2023-07-26 18:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3e6376bf18be789f8f1cefa6970c9c1b@cs.umass.edu \
    --to=fikurnia@cs.umass.edu \
    --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).