git/list[1] front-page[2] threads[3] people[4] search[5] about
 

how to analyze binary delta compression

From
NKNeal Kreitzinger <nkreitzinger@gmail.com>
Date
Apr 25, 2012, 21:15 UTC
Message-ID
<jn9phl$t7s$1@dough.gmane.org>

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: Junio C Hamano
Message 1 of 2 in “how to analyze binary delta compression”
  1. Neal KreitzingerApr 25, 2012
  2. Junio C HamanoApr 25, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.