From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: git@vger.kernel.org
Subject: how to analyze binary delta compression
Date: Wed, 25 Apr 2012 16:15:32 -0500 [thread overview]
Message-ID: <jn9phl$t7s$1@dough.gmane.org> (raw)
I need to assess the delta compression efficiency of various types of
binaries. Can I do it this way:
(1) Run git diff between two versions of a binary and pipe the result to
a file. (Sample different types of binaries and changes.)
(2) Assess the output by size or format or content to determine how well
it delta differenced? How would I determine this? What are good
absolute delta sizes? What are good delta size ratios compared to total
file size? Is the number of hunks in the delta important?
(3) Compress the delta file with gzip (or something) and then assess the
compression ratio? What is a good compression ratio? What are good
delta compressed absolute sizes? What are good delta compressed
relative sizes to total file size?
I'm sure I may be missing some things here. I'm new to assessing delta
compression efficiency of binaries in general, and specifically for git.
Please advise.
v/r,
neal
next reply other threads:[~2012-04-25 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 21:15 Neal Kreitzinger [this message]
2012-04-25 21:21 ` how to analyze binary delta compression Junio C Hamano
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='jn9phl$t7s$1@dough.gmane.org' \
--to=nkreitzinger@gmail.com \
--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