From: Martin Fick <mfick@codeaurora.org>
To: "João Victor Bonfim" <JoaoVictorBonfim@protonmail.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: Fw: Curiosity
Date: Thu, 16 Dec 2021 14:33:28 -0700 [thread overview]
Message-ID: <54fe7ba20109f974b61a7e6c24ba8264@codeaurora.org> (raw)
In-Reply-To: <xndBIO9EtrXaA932eF-0YkvHCAOL1GOKQQlIigssmcwhtZWqGxhc6I_A-lXt7vMK-j1oDrQMHUIuExlpqFS4v88nWci32qx3W5Xi1_hPpUM=@protonmail.com>
On 2021-12-16 14:20, João Victor Bonfim wrote:
>> To expand on this, if what you're storing is already compressed, like
>> Ogg Vorbis files or PNGs, like are found in that repository, then
>> generally they will not delta well. This is also true of things like
>> Microsoft Office or OpenOffice documents, because they're essentially
>> Zip files.
>>
>> The delta algorithm looks for similarities between files to compress
>> them. If a file is already compressed using something like Deflate,
>> used in PNGs and Zip files, then even very similar files will
>> generally
>> look very different, so deltification will generally be ineffective.
...
> Maybe I am thinking too outside the box, but wouldn't it be quite more
> effective for git to identify compressed files, specially on edge cases
> where the compression doesn't have a good chemistry with delta
> compression,
> decompress them for repo storage while also storing the compression
> algorithm as some metadata tag (like a text string or an ID code
> decided
> beforehand), and, when creating the work mirrors, return the
> compression
> to its default state before checkout?
I suspect that for most algorithms and their implementations, this would
not result in repeatable "recompressed" results. Thus the checked-out
files might be different every time you checked them out. :(
-Martin
--
The Qualcomm Innovation Center, Inc. is a member of Code
Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2021-12-16 21:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Wlh_w2gSCDQ2ieJnIY7TStWrzxbwP98SNRIFMTYpva7SRFipqk63HEYFVF7wFn1oSHOkQNsjWGOa5L49vyRlvSLbuZqpmvOaDOHmFkdt2zw=@protonmail.com>
2021-12-15 3:52 ` Fw: Curiosity João Victor Bonfim
2021-12-15 18:07 ` Junio C Hamano
2021-12-15 23:45 ` João Victor Bonfim
2021-12-16 2:19 ` brian m. carlson
2021-12-16 21:20 ` João Victor Bonfim
2021-12-16 21:33 ` Martin Fick [this message]
2021-12-16 21:42 ` Junio C Hamano
2021-12-18 0:17 ` João Victor Bonfim
2021-12-18 0:15 ` João Victor Bonfim
2021-12-18 0:24 ` Junio C Hamano
2021-12-18 0:50 ` João Victor Bonfim
2021-12-18 1:06 ` Martin Fick
2021-12-18 1:34 ` brian m. carlson
2021-12-18 1:40 ` João Victor Bonfim
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=54fe7ba20109f974b61a7e6c24ba8264@codeaurora.org \
--to=mfick@codeaurora.org \
--cc=JoaoVictorBonfim@protonmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
/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).