From: Thomas Rast <trast@inf.ethz.ch>
To: John Keeping <john@keeping.me.uk>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Junio C Hamano <gitster@pobox.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: "git grep" parallelism question
Date: Mon, 29 Apr 2013 20:04:10 +0200 [thread overview]
Message-ID: <877gjldxid.fsf@hexa.v.cablecom.net> (raw)
In-Reply-To: <20130429161814.GJ472@serenity.lan> (John Keeping's message of "Mon, 29 Apr 2013 17:18:14 +0100")
John Keeping <john@keeping.me.uk> writes:
> On Mon, Apr 29, 2013 at 07:35:01PM +0530, Ramkumar Ramachandra wrote:
>> On a related note, one place that IO parallelism can provide massive
>> benefits is in executing shell scripts. Accordingly, I always use the
>> following commands to compile and test git respectively:
>>
>> make -j 8 CFLAGS="-g -O0 -Wall"
>> make -j 8 DEFAULT_TEST_TARGET=prove GIT_PROVE_OPTS="-j 16" test
>>
>> i.e. always use 8 threads when the task is known to be CPU intensive,
>> and always use 16 threads when the task is known to be IO intensive.
>
> On this tangent, I recently added a TEST_OUTPUT_DIRECTORY line to my
> config.mak which points into a tmpfs mount. Keeping all of the test
> repositories in RAM makes the tests significantly faster for me and
> works nicely when you have the patches in jk/test-output (without those
> patches the individual tests work but the reporting of aggregate results
> doesn't).
But that's been possible for quite some time now, using --root, or am I
missing something?
(Not that the fix as such is a bad idea, but other readers might not
want to wait for it to hit master.)
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2013-04-29 18:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 17:31 "git grep" parallelism question Linus Torvalds
2013-04-26 18:47 ` Junio C Hamano
2013-04-26 18:54 ` Linus Torvalds
2013-04-26 19:19 ` Junio C Hamano
2013-04-26 20:31 ` Linus Torvalds
2013-04-27 13:46 ` Thomas Rast
2013-04-29 14:05 ` Ramkumar Ramachandra
2013-04-29 16:18 ` John Keeping
2013-04-29 18:04 ` Thomas Rast [this message]
2013-04-29 18:08 ` John Keeping
2013-04-29 22:22 ` Junio C Hamano
2013-04-30 8:08 ` John Keeping
2013-04-30 15:59 ` Jeff King
2013-04-30 16:12 ` John Keeping
2013-04-30 16:14 ` Jeff King
2013-05-05 15:40 ` Pete Wyckoff
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=877gjldxid.fsf@hexa.v.cablecom.net \
--to=trast@inf.ethz.ch \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=john@keeping.me.uk \
--cc=torvalds@linux-foundation.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.