From: Martin Uecker <muecker@gmx.de>
To: git@vger.kernel.org
Cc: Martin Uecker <muecker@gmx.de>
Subject: Re: space compression (again)
Date: Tue, 19 Apr 2005 14:39:35 +0200 [thread overview]
Message-ID: <20050419123935.GA8091@macavity> (raw)
In-Reply-To: <20050416173702.GA12605@macavity>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Sat, Apr 16, 2005 at 07:37:02PM +0200, Martin Uecker wrote:
> On Sat, Apr 16, 2005 at 11:11:00AM -0400, C. Scott Ananian wrote:
> > The rsync approach does not use fixed chunk boundaries; this is necessary
> > to ensure good storage reuse for the expected case (ie; inserting a single
> > line at the start or in the middle of the file, which changes all the
> > chunk boundaries).
>
> Yes. The chunk boundaries should be determined deterministically
> from local properties of the data. Use a rolling checksum over
> some small window and split the file it it hits a special value (0).
> This is what the rsyncable patch to zlib does.
This is certainly uninteresting for source code repositories
but for people who manage repositories of rsyncable binary
packages this would save a lot of space, bandwidth and
cpu time (compared to rsync because the scanning phase is
not necessary anymore).
Martin
--
One night, when little Giana from Milano was fast asleep,
she had a strange dream.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-04-19 12:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 17:19 space compression (again) C. Scott Ananian
2005-04-15 18:34 ` Linus Torvalds
2005-04-15 18:45 ` C. Scott Ananian
2005-04-15 19:00 ` Derek Fawcus
2005-04-15 19:11 ` Linus Torvalds
2005-04-16 14:39 ` Martin Uecker
2005-04-16 15:11 ` C. Scott Ananian
2005-04-16 17:37 ` Martin Uecker
2005-04-19 12:39 ` Martin Uecker [this message]
2005-04-15 18:50 ` Derek Fawcus
-- strict thread matches above, loose matches on Subject: below --
2005-04-15 19:33 Ray Heasman
2005-04-16 12:29 ` David Lang
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=20050419123935.GA8091@macavity \
--to=muecker@gmx.de \
--cc=git@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).