On Sat, 10 Jun 2006, Martin Langhoff wrote: > > So the per-file and per-directory overhead are significant. I can do a > cvs checkout via pserver:localhost but I don't know off-the-cuff how > to measure the traffic. Hints? Over localhost, you won't see the biggest issue, which is just latency. The git protocol should be absolutely <i>wonderful</i> with bad latency, because once the early bakc-and-forth on what each side has is done, there's no synchronization any more - it's all just streaming, with full-frame TCP. If :pserver: does per-file "hey, what are you up to" kind of syncronization, the big killer would be the latency from one end to the other, regardless of any throughput. You can try to approximate the latency by just looking at the number of packets, and using a large MTU (and on localhost, the MTU will be pretty large - roughly 16kB. Don't count packet size at all, just count how many packets each protocol sends (both ways), ignoring packets that are just empty ACK's. I don't know how to build a tcpdump expression for "TCP packet with an empty payload", but I bet it's possible. [ And I won't guarantee that it's a wonderful approximation for "network cost", but I think it's potentially a reasonably good one. It's totally realistic to equate 32kB of _streaming_ data (two packets flowing in one direction with no synchronization) with just a single byte of data going back-and-forth synchronously ] Linus - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html