From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Recent slowdown in single object builds
Date: Mon, 18 Nov 2019 09:40:16 +0900 [thread overview]
Message-ID: <CAK7LNARUzJx==c1gh33obme21JiRR1CrKELkGpmPJQANx0LqSw@mail.gmail.com> (raw)
In-Reply-To: <8caa1edf-9c6f-15e4-218d-c266013f8e28@kernel.dk>
On Sun, Nov 17, 2019 at 1:57 AM Jens Axboe <axboe@kernel.dk> wrote:
>
> On 11/16/19 12:17 AM, Masahiro Yamada wrote:
> > On Sat, Nov 16, 2019 at 8:10 AM Jens Axboe <axboe@kernel.dk> wrote:
> >>
> >> Hi,
> >>
> >> I've noticed that current -git is a lot slower at doing single object
> >> builds than earlier kernels. Here's an example, building the exact same
> >> file on 5.2 and -git:
> >>
> >> $ time make fs/io_uring.o
> >> real 0m5.953s
> >> user 0m5.402s
> >> sys 0m0.649s
> >>
> >> vs 5.2 based (with all the backports, identical file):
> >>
> >> $ time make fs/io_uring.o
> >> real 0m3.218s
> >> user 0m2.968s
> >> sys 0m0.520s
> >>
> >> Any idea what's going on here? It's almost twice as slow, which is
> >> problematic...
BTW, I am using a cheap machine based on Intel Core i7-6700K.
I can build fs/io_uring.o (based on x86_64_defconfig) much faster.
The slowdown (1.990 sec -> 2.861 sec) is not terrible for me.
masahiro@pug:~/ref/linux$ git describe
v5.2
masahiro@pug:~/ref/linux$ touch fs/io_uring.c; time make fs/io_uring.o
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
DESCEND objtool
CC fs/io_uring.o
real 0m1.990s
user 0m1.723s
sys 0m0.427s
masahiro@pug:~/ref/linux-next$ git describe
next-20191115
masahiro@pug:~/ref/linux-next$ touch fs/io_uring.c; time make fs/io_uring.o
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
DESCEND objtool
CC fs/io_uring.o
real 0m2.861s
user 0m2.373s
sys 0m0.642s
Snippet from my /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 94
model name : Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
stepping : 3
microcode : 0xd4
cpu MHz : 800.023
cache size : 8192 KB
> >
> >
> > This is necessary cost
> > to do single builds
> > (394053f4a4b3e3eeeaa67b67fc886a9a75bd9e4d)
> > but, it is much better in linux-next.
>
> Very sad that it's now twice as slow as before, that's a real problem.
> This isn't a marginal slowdown.
>
> I've never had issues with single object builds before, and in fact
> it's often useful to build stuff that's disabled as a single object.
> Where's the report that led to this commit being necessary?
>
> --
> Jens Axboe
>
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2019-11-18 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 23:10 Recent slowdown in single object builds Jens Axboe
2019-11-16 7:17 ` Masahiro Yamada
2019-11-16 16:57 ` Jens Axboe
2019-11-18 0:40 ` Masahiro Yamada [this message]
2019-11-18 2:34 ` Jens Axboe
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='CAK7LNARUzJx==c1gh33obme21JiRR1CrKELkGpmPJQANx0LqSw@mail.gmail.com' \
--to=yamada.masahiro@socionext.com \
--cc=axboe@kernel.dk \
--cc=linux-kernel@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).