From: Darrin Thompson <darrint@progeny.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Dump http servers still slow?
Date: Fri, 29 Jul 2005 09:03:41 -0500 [thread overview]
Message-ID: <1122645821.4263.6.camel@localhost.localdomain> (raw)
In-Reply-To: <7vy87qpcwg.fsf@assigned-by-dhcp.cox.net>
On Thu, 2005-07-28 at 19:24 -0700, Junio C Hamano wrote:
> The thing is, the base pack for the git repository is 1.8MB
> currently containing 4500+ objects, while we accumulated 600+
> unpacked objects since then which is about ~5MB. The commit
> walker needs to fetched the latter one by one in the old way.
>
> When packed incrementally on top of the base pack, these 600+
> unpacked objects compress down to something like 400KB, and I
> was hoping we could wait until we accumulate enough to produce
> an incremental about a meg or so ...
Ok... so lets check my assumptions:
1. Pack files should reduce the number of http round trips.
2. What I'm seeing when I check out mainline git is the acquisition of a
single large pack, then 600+ more recent objects. Better than before,
but still hundreds of round trips.
3. If I wanted to further speed up the initial checkout on my own
repositories I could frequently repack my most recent few hundred
objects.
4. If curl had pipelining then less pack management would be needed.
Where is the code for gitweb? (i.e. http://kernel.org/git ) Seems like
it could benefit from some git-send-pack superpowers.
--
Darrin
next prev parent reply other threads:[~2005-07-29 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 21:00 Dump http servers still slow? Darrin Thompson
2005-07-29 2:24 ` Junio C Hamano
2005-07-29 14:03 ` Darrin Thompson [this message]
2005-07-29 14:48 ` Ryan Anderson
2005-07-29 14:57 ` Darrin Thompson
2005-07-29 15:08 ` Radoslaw AstralStorm Szkodzinski
2005-07-29 15:26 ` Darrin Thompson
2005-07-30 2:11 ` Junio C Hamano
2005-07-31 6:51 ` Junio C Hamano
2005-08-01 14:03 ` Darrin Thompson
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=1122645821.4263.6.camel@localhost.localdomain \
--to=darrint@progeny.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).