From: Linus Torvalds <torvalds@osdl.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: Why so much time in the kernel?
Date: Fri, 16 Jun 2006 09:09:14 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0606160906250.5498@g5.osdl.org> (raw)
In-Reply-To: <9e4733910606160825hb538d6fo4c9f1d7d9768e100@mail.gmail.com>
On Fri, 16 Jun 2006, Jon Smirl wrote:
>
> I am using cvs-1.11.21-3.2
> I can try running their development tree.
No, don't. We already know that 1.12 leaks memory and makes the cvsimport
not work at all.
> >
> > AND it's git-cvsimport forking and exec'ing git helper processes.
>
> Is it worthwhile to make a library version of these? Svn has lib
> versions and they barely show up in oprofile. cvsimport is only using
> 4-5 low level git funtions.
Eventually, I think that's where we'll get. We're already at the stage
where most of the core could just be written as a library.
> > I guess mozilla really does use a fair number of branches?
>
> Is 1,800 a lot?
Yeah. Although even just two is enough, if you just alternate committing
on them ;)
So it's actually not number of branches, it's more about frequency of
the branch changing in the cvsps output. And yes, you could probably
improve performance by sorting the changesets differently, but Martin's
change to use separate index files should make it all pretty moot.
Linus
next prev parent reply other threads:[~2006-06-16 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-16 14:49 Why so much time in the kernel? Jon Smirl
2006-06-16 15:06 ` Linus Torvalds
2006-06-16 15:25 ` Jon Smirl
2006-06-16 16:09 ` Linus Torvalds [this message]
2006-06-16 17:00 ` Jon Smirl
2006-06-16 17:09 ` Jakub Narebski
2006-06-16 17:29 ` Keith Packard
2006-06-16 17:44 ` Jon Smirl
2006-06-16 18:02 ` Keith Packard
2006-06-16 18:07 ` Nicolas Pitre
2006-06-16 18:32 ` Linus Torvalds
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0606160906250.5498@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=jonsmirl@gmail.com \
/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.
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 NNTP newsgroup(s).