From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: git@vger.kernel.org
Subject: Re: git-fetching from a big repository is slow
Date: Thu, 14 Dec 2006 16:45:59 +0100 [thread overview]
Message-ID: <458171B7.1020702@xs4all.nl> (raw)
In-Reply-To: <200612141518.05770.andyparkins@gmail.com>
Andy Parkins escreveu:
> On Thursday 2006 December 14 13:53, Andreas Ericsson wrote:
>
>> This seems to happen if your repository consists of many large binary
>> files, especially many large binary files of several versions that do
>> not deltify well against each other. Perhaps it's worth adding gzip
>
> It's actually just every released patch to the linux kernel ever issued.
> Almost entirely ASCII and every revision (save the first) created by patching
> the previous.
I just noticed that git-fetch now runs git-show-ref --verify on every
tag it encounters. This seems to slow down fetch over here.
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2006-12-14 15:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 13:40 git-fetching from a big repository is slow Andy Parkins
2006-12-14 13:53 ` Andreas Ericsson
2006-12-14 14:14 ` Johannes Schindelin
2006-12-14 15:06 ` Andreas Ericsson
2006-12-14 19:05 ` Geert Bosch
2006-12-14 19:46 ` Shawn Pearce
2006-12-14 22:12 ` Horst H. von Brand
2006-12-14 22:38 ` Shawn Pearce
2006-12-15 21:49 ` Pazu
2006-12-16 13:32 ` Robin Rosenberg
2006-12-14 23:01 ` Geert Bosch
2006-12-14 23:15 ` Johannes Schindelin
2006-12-14 23:29 ` Shawn Pearce
2006-12-15 0:07 ` Johannes Schindelin
2006-12-15 0:42 ` Shawn Pearce
2006-12-15 2:26 ` Nicolas Pitre
2006-12-14 22:28 ` Andreas Ericsson
2006-12-14 15:18 ` Andy Parkins
2006-12-14 15:45 ` Han-Wen Nienhuys [this message]
2006-12-14 16:20 ` Andy Parkins
2006-12-14 16:34 ` Johannes Schindelin
2006-12-14 20:41 ` Junio C Hamano
2006-12-14 23:26 ` Johannes Schindelin
2006-12-15 0:38 ` Junio C Hamano
2006-12-14 18:14 ` Nicolas Pitre
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=458171B7.1020702@xs4all.nl \
--to=hanwen@xs4all.nl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.