Re: git-fetch per-repository speed issues
- From
Linus Torvalds <torvalds@osdl.org>
- Date
- Jul 4, 2006, 04:19 UTC
- Message-ID
- <Pine.LNX.4.64.0607032115340.12404@g5.osdl.org>
- In-Reply-To
- <1151985747.4723.102.camel@neko.keithp.com>
On Mon, 3 Jul 2006, Keith Packard wrote:
> > Yeah, it says that only once. And, it runs the fetch-pack in about .5 > seconds. And, now the whole process completes in 4.7 seconds; perhaps > the remote server is less loaded than earlier this afternoon?
Well, that's still strange. What takes 4.2 seconds then?
Show 5 quoted lines
> > And then it should leave a "fetch.trace" file in your working directory, > > which should show where that _one_ thing spends its time. > > It looks boring to me and spent 0.55 from start to finish. I can send > along the whole trace if you have an acute desire to peer at it.
No, the 0.5 seconds is what I _expected_. There's something strange going on in your git fetch that it takes any longer than that.
Can you instrument your "git-fetch.sh" script (just add random
(echo $LINENO ; date) >&2
lines all over) to see what is so expensive?
That fetch-pack really should be the most expensive part by far (and half a second sounds right), but it clearly isn't. At 4.7s, your fetch is still taking about ten times longer than it _should_.
Linus