From: William Josephson <jkw@eecs.harvard.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil/venti/manber
Date: Mon, 28 Apr 2003 18:13:01 -0400 [thread overview]
Message-ID: <20030428221301.GA17124@mero.morphisms.net> (raw)
In-Reply-To: <69a4c6b7395b8751d482ae47469aed19@plan9.bell-labs.com>
On Mon, Apr 28, 2003 at 05:55:34PM -0400, Russ Cox wrote:
> I think the notes happen to answer your questions, mainly
> because I think they clear up your misunderstandings about
> how applying Manber's idea would actually work.
> If you have questions after reading the notes, I'd be happy
> to address them directly, but I think we're not on the same
> page at the moment.
<snip good discussion of chunking>
For what it is worth, on common datasets (e.g. /usr and /home on Linux
and FreeBSD boxes, the root disk on Windows boxes, and sets containing
a majority of CAD and graphics files), using chunking turns out to be
a significant win compared to fixed size blocks, at least over time.
For the first run (i.e. first write of a set of files) and for small
files, the difference is usually fairly trivial. The chunking
approach is not as big a win as using content-addressed blocks in the
first place, but still a win. Whether or not it makes sense to go to
the effort of implementing it for Plan 9 is another question, of
course. I'm afraid I can't name numbers as I'd like to do, but
suffice it to say that this idea is being pursued commercially....
prev parent reply other threads:[~2003-04-28 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 20:17 FODEMESI Gergely
2003-04-28 21:55 ` Russ Cox
2003-04-28 22:13 ` William Josephson [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=20030428221301.GA17124@mero.morphisms.net \
--to=jkw@eecs.harvard.edu \
--cc=9fans@cse.psu.edu \
/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).