From: Sedat Dilek <sedat.dilek@gmail.com>
To: "Derrick, Jonathan" <jonathan.derrick@intel.com>
Cc: "willy@infradead.org" <willy@infradead.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dhowells@redhat.com" <dhowells@redhat.com>
Subject: Re: Parallel compilation performance regression
Date: Sat, 20 Jun 2020 09:44:12 +0200 [thread overview]
Message-ID: <CA+icZUWTTdR42atb9FNYa90wwuvfFngksBWJBn2BLarkJsztxA@mail.gmail.com> (raw)
In-Reply-To: <bf968a2887536459293eaeb40d354fb365b1438d.camel@intel.com>
On Sat, Jun 20, 2020 at 5:53 AM Derrick, Jonathan
<jonathan.derrick@intel.com> wrote:
>
> On Thu, 2020-06-18 at 18:05 -0700, Matthew Wilcox wrote:
> > On Thu, Jun 18, 2020 at 11:52:55PM +0000, Derrick, Jonathan wrote:
> > > Hi David,
> > >
> > > I've been experiencing a performance regression when running a parallel
> > > compilation (eg, make -j72) on recent kernels.
> >
> > I bet you're using a version of make which predates 4.3:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0ddad21d3e99c743a3aa473121dc5561679e26bb
> >
>
> I am!
>
> # make --version
> GNU Make 4.2.1
>
>
> Thank you Matthew!
Check your distribution and included patches on top of a vanilla make v4.2.
Debian had some important ones I described in [1].
When proposing "make version 4.3" for tc-build - an opportunity to
build a llvm-toolchain the easy way - we saw different numbers.
I pointed in [1] to the Linus patch Matthew did here.
Personally, with switching to Debian's make version 4.3-3 I have seen
no big differences when using "make -j3" to build Linux v5.7+.
That might be different with "make -j72"...
...can I have SSH access to this machine, please :-),
You forgot to tell which Linux version you use.
If you are interested please look at closed tc-build issue #72 for our analysis.
For tc-build it did not matter - (Debian's) make v4.2 had some
slightly better performance.
BTW, with that pipe improvements in Linux v5.7 I see some better
numbers when using pipebench to benchmark my devices:
Example: SanDisk iSSD 16GB
root# cat /dev/sdb | pipebench > /dev/null
Summary:
Piped 14.91 GB in 00h01m25.20s: 179.23 MB/second
Before: approx. 100MB/s
BTW, I heard of hyperfine benchmark tool the first time when dealing
with make performance (see [2]) in ClangBuiltLinux.
I would like to see some benchmark numbers with hyperfine from you if
you do not mind.
Stay OPEN minded and curious.
Thanks.
- Sedat -
[1] https://github.com/ClangBuiltLinux/tc-build/issues/72
[2] https://github.com/sharkdp/hyperfine
[3] https://github.com/sharkdp/hyperfine/releases
prev parent reply other threads:[~2020-06-20 7:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 23:52 Parallel compilation performance regression Derrick, Jonathan
2020-06-19 1:05 ` Matthew Wilcox
2020-06-19 14:59 ` Derrick, Jonathan
2020-06-20 7:44 ` Sedat Dilek [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=CA+icZUWTTdR42atb9FNYa90wwuvfFngksBWJBn2BLarkJsztxA@mail.gmail.com \
--to=sedat.dilek@gmail.com \
--cc=dhowells@redhat.com \
--cc=jonathan.derrick@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.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).