git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fredrik Gustafsson <iveqy@iveqy.com>
To: Thomas Braun <thomas.braun@virtuell-zuhause.de>
Cc: "Armbruster Joachim (BEG/EMS1)" <Joachim.Armbruster@de.bosch.com>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Why is git submodule slow under windows
Date: Fri, 18 Jul 2014 15:02:41 +0200	[thread overview]
Message-ID: <20140718130241.GD14720@paksenarrion.iveqy.com> (raw)
In-Reply-To: <53C90E44.6030702@virtuell-zuhause.de>

On Fri, Jul 18, 2014 at 02:08:36PM +0200, Thomas Braun wrote:
> Am 18.07.2014 12:14, schrieb Armbruster Joachim (BEG/EMS1):
> > Hello,
> > 
> > We split a monolithic repository into ~50 submodules. The stored data
> > has the same size. In the 1:1 comparison to the monolithic
> > repository, the submodule handling is very slow. Under Linux
> > everything remains fast, but windows is slow.
> > 
> > So, why is git getting slow when it has to deal with a lot of
> > submodules? I read something about the lack of the underlying cygwin
> > to handle NTFS in a efficient way. Is this the root cause, or are
> > there other causes also?
> > 
> 
> Hi,
> 
> I assume you are using the latetst git from https://msysgit.github.io on
> windows.
> 
> I would guess that submodules on windows are slow because
> git-submodules.sh is a shell script, and bash on windows is not really
> that fast.

My guess is that because the shell script uses fork() heavily and fork()
is an expensive operation on Windows, that alone causes the slowddown.

I did a quick test a while back when I rewrote part of git-submodule.sh
in lua and runned it on my repo with ~45 submodules. The speedup was
significant and should be even bigger on windows.

-- 
Med vänlig hälsning
Fredrik Gustafsson

tel: 0733-608274
e-post: iveqy@iveqy.com

  reply	other threads:[~2014-07-18 12:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 10:14 Why is git submodule slow under windows Armbruster Joachim (BEG/EMS1)
2014-07-18 12:08 ` Thomas Braun
2014-07-18 13:02   ` Fredrik Gustafsson [this message]
2014-07-18 18:01     ` Jens Lehmann

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=20140718130241.GD14720@paksenarrion.iveqy.com \
    --to=iveqy@iveqy.com \
    --cc=Joachim.Armbruster@de.bosch.com \
    --cc=git@vger.kernel.org \
    --cc=thomas.braun@virtuell-zuhause.de \
    /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).