From: Jens Lehmann <Jens.Lehmann@web.de>
To: Stefan Zager <szager@google.com>
Cc: git@vger.kernel.org, gitster@pobox.com, hvoigt@hvoigt.net
Subject: Re: [PATCH] Enable parallelism in git submodule update.
Date: Sat, 03 Nov 2012 20:07:02 +0100 [thread overview]
Message-ID: <50956B56.1010603@web.de> (raw)
In-Reply-To: <501558AD.6010402@web.de>
Am 29.07.2012 17:37, schrieb Jens Lehmann:
> Am 27.07.2012 20:37, schrieb Stefan Zager:
>> The --jobs parameter may be used to set the degree of per-submodule
>> parallel execution.
>
> I think this is a sound idea, but it would be good to see some
> actual measurements. What are the performance numbers with and
> without this change? Which cases do benefit and are there some
> which run slower when run in parallel?
ping?
next prev parent reply other threads:[~2012-11-03 19:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-27 18:37 [PATCH] Enable parallelism in git submodule update Stefan Zager
2012-07-27 21:38 ` Junio C Hamano
[not found] ` <CAHOQ7J_jYAe7r1q6Cg9OJb8f+79UfS=JfRk9NrS4R4a+oLM8LA@mail.gmail.com>
2012-07-27 23:25 ` Junio C Hamano
2012-07-28 10:52 ` Heiko Voigt
2012-07-29 21:59 ` Junio C Hamano
2012-07-28 10:22 ` Heiko Voigt
2012-07-28 12:19 ` [PATCH] cleanup argument passing in submodule status command Heiko Voigt
2012-07-29 6:22 ` Junio C Hamano
2012-07-29 15:29 ` Jens Lehmann
2012-07-29 21:57 ` Junio C Hamano
2012-07-29 15:37 ` [PATCH] Enable parallelism in git submodule update Jens Lehmann
2012-11-03 19:07 ` Jens Lehmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-30 18:03 szager
2012-10-30 18:03 szager
2012-10-30 18:11 ` Stefan Zager
2012-11-02 21:49 ` Stefan Zager
2012-11-03 15:42 ` Jens Lehmann
2012-11-03 18:44 ` Phil Hord
2012-11-03 19:13 ` 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=50956B56.1010603@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=szager@google.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).