From: "Shawn O. Pearce" <spearce@spearce.org>
To: git@vger.kernel.org
Subject: Re: db/fetch-pack topic (was: What's cooking in git.git (topics))
Date: Sun, 16 Sep 2007 00:03:21 -0400 [thread overview]
Message-ID: <20070916040321.GC3099@spearce.org> (raw)
In-Reply-To: <20070915074759.GA3099@spearce.org>
> "Shawn O. Pearce" <spearce@spearce.org> wrote:
> > Junio C Hamano <gitster@pobox.com> 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.
next prev parent reply other threads:[~2007-09-16 4:03 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 8:52 What's cooking in git.git (topics) Junio C Hamano
[not found] ` <7v1wd1d0le.fsf@gitster.siamese.dyndns.org>
2007-09-14 18:30 ` Shawn O. Pearce
2007-09-15 7:47 ` db/fetch-pack topic (was: What's cooking in git.git (topics)) Shawn O. Pearce
2007-09-16 4:03 ` Shawn O. Pearce [this message]
2007-09-14 23:47 ` What's cooking in git.git (topics) Johannes Schindelin
2007-09-26 21:07 ` Carlos Rica
2007-09-26 20:05 ` Junio C Hamano
2007-09-26 21:44 ` Johannes Schindelin
2007-09-26 21:53 ` Tom Clarke
2007-09-27 2:36 ` Jeff King
2007-09-27 6:08 ` David Kastrup
2007-09-27 6:43 ` David Kastrup
2007-09-27 13:30 ` Jeff King
2007-09-27 13:46 ` David Kastrup
2007-10-02 4:16 ` Jeff King
2007-10-02 5:01 ` Junio C Hamano
2007-10-02 5:08 ` Jeff King
2007-10-02 5:13 ` Jeff King
2007-10-02 6:10 ` David Kastrup
2007-10-02 16:11 ` Jeff King
2007-10-02 16:31 ` David Kastrup
2007-10-02 17:39 ` Jeff King
2007-10-02 18:44 ` David Kastrup
2007-10-03 2:28 ` Linus Torvalds
2007-10-03 6:54 ` Jeff King
2007-10-03 16:13 ` Linus Torvalds
2007-10-03 8:20 ` David Kastrup
2007-10-03 16:59 ` Jeff King
2007-10-03 17:53 ` Linus Torvalds
2007-10-03 18:09 ` David Kastrup
2007-10-04 7:10 ` Junio C Hamano
2007-09-28 3:24 ` Daniel Barkalow
2007-10-02 5:53 ` Junio C Hamano
2007-10-02 6:41 ` Steven Grimm
2007-10-02 6:44 ` Steffen Prohaska
2007-10-02 7:03 ` Matthieu Moy
2007-10-02 7:21 ` Junio C Hamano
2007-10-02 8:01 ` David Kågedal
2007-10-02 8:07 ` Matthieu Moy
2007-10-02 17:44 ` Junio C Hamano
2007-10-03 5:30 ` [PATCH] rebase: make the warning more useful when the work tree is unclean Junio C Hamano
2007-10-03 9:02 ` Matthieu Moy
2007-10-02 12:52 ` What's cooking in git.git (topics) Johannes Schindelin
2007-10-02 17:00 ` Daniel Barkalow
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=20070916040321.GC3099@spearce.org \
--to=spearce@spearce.org \
--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).