From: Johannes Berg <johannes@sipsolutions.net>
To: backports@vger.kernel.org
Subject: Re: [PATCH] backports: speed up building with bash
Date: Tue, 03 Dec 2019 16:21:08 +0100 [thread overview]
Message-ID: <757c854e78543992b5110208517cd8d3ca8e9414.camel@sipsolutions.net> (raw)
In-Reply-To: <1bef9e95439caedef7dd2252b5414035e370f7b7.camel@sipsolutions.net> (sfid-20191203_161831_359846_43C56C36)
On Tue, 2019-12-03 at 16:18 +0100, Johannes Berg wrote:
> On Tue, 2019-12-03 at 16:06 +0100, Johannes Berg wrote:
> > From: Johannes Berg <johannes.berg@intel.com>
> >
> > When building with /bin/sh -> bash, things are SUPER slow (at least
> > for me), because bash takes a LOOONG time to look at the environment
> > variables (and we typically have around 6k), adding ~300ms to each
> > bash invocation for me.
>
> The real results are like this:
>
> Completely clean build, after git clean -fdxq, but I have ccache primed
> so all the stuff is build overhead - gcc is ccache and just returns
> directly from the cache.
>
> without the patch:
> real 9m17.180s
> user 24m38.063s
> sys 0m32.138s
>
>
> with the patch:
> real 0m18.157s
> user 0m24.553s
> sys 0m13.342s
That was with bash, with dash:
without the patch:
real 0m33.018s
user 0m56.248s
sys 0m22.898s
with the patch:
real 0m18.113s
user 0m18.036s
sys 0m12.903s
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
prev parent reply other threads:[~2019-12-03 15:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-03 15:06 [PATCH] backports: speed up building with bash Johannes Berg
2019-12-03 15:15 ` Johannes Berg
2019-12-03 15:18 ` Johannes Berg
2019-12-03 15:21 ` Johannes Berg [this message]
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=757c854e78543992b5110208517cd8d3ca8e9414.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@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.
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).