From: Junio C Hamano <junkio@cox.net>
To: Darrin Thompson <darrint@progeny.com>
Cc: git@vger.kernel.org
Subject: Re: Dump http servers still slow?
Date: Thu, 28 Jul 2005 19:24:47 -0700 [thread overview]
Message-ID: <7vy87qpcwg.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: 1122584423.12374.11.camel@localhost.localdomain
Darrin Thompson <darrint@progeny.com> writes:
> I just ran git clone against the mainline git repository using both http
> and rsync. http was still quite slow compared to rsync. I expected that
> the http time would be much faster than in the past due to the pack
> file.
>
> Is there something simple I'm missing?
No, the only thing you missed was that I did not write it to
make it fast, but just to make it work ;-). The commit walker
simply does not work against a dumb http server repository that
is packed and prune-packed, which is already the case for both
kernel and git repositories.
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 ...
next prev parent reply other threads:[~2005-07-29 2:25 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 [this message]
2005-07-29 14:03 ` Darrin Thompson
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vy87qpcwg.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=darrint@progeny.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).