From: Martin Langhoff <martin.langhoff@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Marius Storm-Olsen <mstormo@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Delta compression not so effective
Date: Wed, 1 Mar 2017 16:08:04 -0500 [thread overview]
Message-ID: <CACPiFCKG7K4jGLHRBA5VrdhLwjqj6KPWS2NYtHjmSdfcRhm+2A@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFx7QFqrHw4e72vOdM5z0rw1CCkL2-UX8ej5CLSBWjLNLA@mail.gmail.com>
On Wed, Mar 1, 2017 at 1:30 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> For example, the sorting code thinks that objects with the same name
> across the history are good sources of deltas.
Marius has indicated he is working with jar files. IME jar and war
files, which are zipfiles containing Java bytecode, range from not
delta-ing in a useful fashion, to pretty good deltas.
Depending on the build process (hi Maven!) there can be enough
variance in the build metadata to throw all the compression machinery
off.
On a simple Maven-driven project I have at hand, two .war files
compiled from the same codebase compressed really well in git. I've
also seen projects where storage space is ~101% of the "uncompressed"
size.
my 2c,
m
--
martin.langhoff@gmail.com
- ask interesting questions ~ http://linkedin.com/in/martinlanghoff
- don't be distracted ~ http://github.com/martin-langhoff
by shiny stuff
next prev parent reply other threads:[~2017-03-01 21:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 13:51 Delta compression not so effective Marius Storm-Olsen
2017-03-01 16:06 ` Junio C Hamano
2017-03-01 16:17 ` Junio C Hamano
2017-03-01 17:36 ` Linus Torvalds
2017-03-01 17:57 ` Marius Storm-Olsen
2017-03-01 18:30 ` Linus Torvalds
2017-03-01 21:08 ` Martin Langhoff [this message]
2017-03-02 0:12 ` Marius Storm-Olsen
2017-03-02 0:43 ` Linus Torvalds
2017-03-04 8:27 ` Marius Storm-Olsen
2017-03-06 1:14 ` Linus Torvalds
2017-03-06 13:36 ` Marius Storm-Olsen
2017-03-07 9:07 ` Thomas Braun
2017-03-01 20:19 ` Martin Langhoff
2017-03-01 23:59 ` Marius Storm-Olsen
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACPiFCKG7K4jGLHRBA5VrdhLwjqj6KPWS2NYtHjmSdfcRhm+2A@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=mstormo@gmail.com \
--cc=torvalds@linux-foundation.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).