> "Shawn O. Pearce" <spearce@xxxxxxxxxxx> wrote:
> > Junio C Hamano <gitster@xxxxxxxxx> wrote:
> > > * db/fetch-pack (Fri Sep 14 03:31:25 2007 -0400) 22 commits
> > ...
> > > This is Daniel's fetch-pack in C plus fixups from Shawn.
> > > Unfortunately the fixups breaks t3200 ("*** glibc detected ***
> > > fetch: free(): invalid pointer xxx ***"), which I haven't looked
> > > into yet.
With all of my fixups applied I took some performance measurements
today from two of my larger day-job repositories:
A.git (356 branches):
Current Fetch New "Builtin" Fetch
------------------ --------------------
real 3m19.921s real 0m9.969s
user 1m58.050s user 0m1.449s
sys 2m4.747s sys 0m4.465s
B.git (24 branches):
Current Fetch New "Builtin" Fetch
------------------ --------------------
real 0m21.250s real 0m4.735s
user 0m10.981s user 0m0.510s
sys 0m12.387s sys 0m1.481s
All runs were a no-op fetch over SSH on the LAN. The system running
git-fetch was a Cygwin/Windows 2000 box and the server was Solaris 9.
Just starting an SSH connection (`ssh solsrv echo hi`) takes me on
average 1 second so a 4.7s no-op fetch on the smaller repository
is very respectable.
3m19s vs. 9s? I'll take 9s, thankyouverymuch. Even if I have
more testing and debugging to do. Especially since the two repos
above are only a sampling of the actual set I have to deal with on
a daily basis.
--
Shawn.
-
To unsubscribe from this list: 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
