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? > > 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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Tue Jul 04 14:21:11 2006
This archive was generated by hypermail 2.1.8 : 2006-07-04 14:21:37 EST