From: Nicolas Pitre <nico@cam.org>
To: Chris Mason <mason@suse.com>
Cc: Geert Bosch <bosch@adacore.com>,
Linus Torvalds <torvalds@osdl.org>, Alon Ziv <alonz@nolaviz.org>,
git@vger.kernel.org
Subject: Re: [PATCH] add the ability to create and retrieve delta objects
Date: Wed, 04 May 2005 23:10:47 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0505042259150.14033@localhost.localdomain> (raw)
In-Reply-To: <200505041834.19053.mason@suse.com>
On Wed, 4 May 2005, Chris Mason wrote:
> On Wednesday 04 May 2005 17:47, Geert Bosch wrote:
> > From your tests it would seem that the zdelta version is the only one
> > to provide a uniform improvement over plain git. As it also seems the
> > simplest approach, I wonder why the consensus is that using xdiff
> > would be better?
>
> zdelta seems to be a research project. It does compress better than the xdiff
> lib, but the speed improvements against xdiff(1) are probably because the
> resulting tree is smaller. I favor the xdiff code because it's so much
> smaller, and seems easier for us to maintain.
Yep. And compression can be improved without changing de decompressor
since the decompressor is only a replay of what the compressor found to
be redundent. That redundency searching can probably be improved wrt to
the current code. And FRankly considering about 300 lines of code to
create a delta and 60 lines to expand it is hard to beat maintenance
wise.
> For performance, there's still quite a bit of tuning that can be done in terms
> of when and how we delta.
Indeed.
Nicolas
next prev parent reply other threads:[~2005-05-05 3:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 3:57 RFC: adding xdelta compression to git Alon Ziv
2005-05-03 4:12 ` Nicolas Pitre
2005-05-03 4:52 ` Linus Torvalds
2005-05-03 5:30 ` Davide Libenzi
2005-05-03 15:52 ` C. Scott Ananian
2005-05-03 17:35 ` Linus Torvalds
2005-05-03 18:10 ` Davide Libenzi
2005-05-03 8:06 ` [PATCH] add the ability to create and retrieve delta objects Nicolas Pitre
2005-05-03 11:24 ` Chris Mason
2005-05-03 12:51 ` Nicolas Pitre
2005-05-03 15:07 ` Linus Torvalds
2005-05-03 16:09 ` Chris Mason
2005-05-03 15:57 ` C. Scott Ananian
2005-05-03 16:35 ` Chris Mason
2005-05-03 14:13 ` Chris Mason
2005-05-03 14:24 ` Nicolas Pitre
2005-05-03 14:37 ` Chris Mason
2005-05-03 15:04 ` Nicolas Pitre
2005-05-03 16:54 ` Chris Mason
2005-05-03 14:48 ` Linus Torvalds
2005-05-03 15:52 ` Nicolas Pitre
2005-05-04 15:56 ` Chris Mason
2005-05-04 16:12 ` C. Scott Ananian
2005-05-04 17:44 ` Chris Mason
2005-05-04 22:03 ` Linus Torvalds
2005-05-04 22:43 ` Chris Mason
2005-05-05 3:25 ` Nicolas Pitre
2005-05-04 21:47 ` Geert Bosch
2005-05-04 22:34 ` Chris Mason
2005-05-05 3:10 ` Nicolas Pitre [this message]
2005-05-03 12:48 ` RFC: adding xdelta compression to git Dan Holmsand
2005-05-03 15:50 ` C. Scott Ananian
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=Pine.LNX.4.62.0505042259150.14033@localhost.localdomain \
--to=nico@cam.org \
--cc=alonz@nolaviz.org \
--cc=bosch@adacore.com \
--cc=git@vger.kernel.org \
--cc=mason@suse.com \
--cc=torvalds@osdl.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).