From: John <john@puckerupgames•com>
To: Nicolas Pitre <nico@fluxnic•net>
Cc: Jeff King <peff@peff•net>, git@vger•kernel.org
Subject: Re: serious performance issues with images, audio files, and other "non-code" data
Date: Sun, 23 May 2010 20:21:12 -0400 [thread overview]
Message-ID: <4BF9C678.6010108@puckerupgames.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1005181557250.12758@xanadu.home>
Just to follow up, the two solutions which have had a noticeable effect are,
first to run daily `gc`s, and, second, to configure a ".gitattributes" file as such:
*.jpg binary -delta
*.png binary -delta
*.psd binary -delta
*.gz binary -delta
*.bz2 binary -delta
.. and so on.
On my first go-round with ".gitattributes" (earlier in this thread), my patterns
were setup incorrectly, as in,
*.{gz,bz2,tgz,psd,png,jpg} binary -delta
Since git does not perform brace expansion, the above patterns never matched.
After revising the .gitattributes file, a ~6 minute gc dropped down to just
under ~3 minutes.
Is there any reason why someone would NOT want the above ".gitattributes"
defined by default?
On 05/18/2010 03:59 PM, Nicolas Pitre wrote:
> On Tue, 18 May 2010, Jeff King wrote:
>
>> On Tue, May 18, 2010 at 03:33:58PM -0400, Nicolas Pitre wrote:
>>
>>>> It will have to write the whole 200M packfile out each time, though.
>>>
>>> No. gc will only create a pack with new loose objects by default.
>>> Only if the number of packs grow too large will it combine them into one
>>> pack.
>>
>> I think that is only "gc --auto".
>
> Argh. You're right. And "gc --auto" is already ran by many commands
> already.
>
> It is "git repack" that doesn't combine packs by default.
>
>
> Nicolas
next prev parent reply other threads:[~2010-05-24 0:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 18:53 serious performance issues with images, audio files, and other "non-code" data John
2010-05-12 19:15 ` Jakub Narebski
2010-05-14 5:10 ` Jeff King
2010-05-14 12:54 ` John
2010-05-14 17:26 ` Dirk Süsserott
2010-05-17 23:16 ` Jeff King
2010-05-17 23:33 ` Sverre Rabbelier
2010-05-18 19:07 ` Jeff King
2010-05-18 19:10 ` Sverre Rabbelier
2010-05-18 19:27 ` Jeff King
2010-05-18 19:37 ` Nicolas Pitre
2010-05-18 18:50 ` John
2010-05-18 18:54 ` Sverre Rabbelier
2010-05-18 19:19 ` Jeff King
2010-05-18 19:33 ` Nicolas Pitre
2010-05-18 19:41 ` Jeff King
2010-05-18 19:59 ` Nicolas Pitre
2010-05-24 0:21 ` John [this message]
2010-05-24 1:16 ` Junio C Hamano
2010-05-24 7:01 ` John
2010-05-25 6:33 ` Jeff King
2010-05-25 7:28 ` Michael J Gruber
2010-05-25 16:12 ` John
2010-05-25 17:18 ` Nicolas Pitre
2010-05-25 17:47 ` John
2010-05-24 5:39 ` Jeff King
2010-05-24 6:44 ` John
2010-05-24 6:45 ` Jeff King
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=4BF9C678.6010108@puckerupgames.com \
--to=john@puckerupgames$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=nico@fluxnic$(echo .)net \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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