From: Joshua Kinard <kumba@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] util-linux build time increase?
Date: Thu, 28 Feb 2019 04:16:19 -0500 [thread overview]
Message-ID: <69b62838-66ea-28d7-fb31-71a15e6d4f93@gentoo.org> (raw)
In-Reply-To: <bbd29198-e866-1b0a-14e1-d047e2cc6f42@gentoo.org>
On 2/21/2019 16:18, Kristian Fiskerstrand wrote:
> On 2/21/19 1:29 PM, Guilherme Amadio wrote:
>> On Thu, Feb 21, 2019 at 04:36:24AM -0500, Joshua Kinard wrote:
>>> Does anyone have an idea why util-linux's build time would go up
>>> significantly from 2.32.x to 2.33.x? It may be a MIPS thing, as my x86_64
>>> box shows no discernible change in build times between the same versions.
>>> Can any other archs check w/ genlop to see if they see a large jump in build
>>> time?
>>>
>
> At least on a couple of my amd64 there isn't any noticeable slowdown.
> similar to your own observations. E.g this laptop (Linux ares
> 4.9.155-gentoo-kf0 #1 SMP Sun Feb 10 17:01:51 CET 2019 x86_64 Intel(R)
> Xeon(R) CPU E3-1535M v5 @ 2.90GHz GenuineIntel GNU/Linux) says
>
> # /usr/local/bin/emerge_time.sh sys-apps/util-linux
> util-linux-2.28.2: Thu Feb 9 18:52:32 2017: 1 minute, 9 seconds
> util-linux-2.28.2: Thu Feb 9 19:56:31 2017: 1 minute, 37 seconds
> util-linux-2.28.2: Fri Apr 21 20:05:52 2017: 35 seconds
> util-linux-2.30.2: Thu Nov 23 18:59:23 2017: 55 seconds
> util-linux-2.30.2: Mon Dec 4 22:08:07 2017: 38 seconds
> util-linux-2.30.2: Wed Jan 10 20:44:39 2018: 44 seconds
> util-linux-2.30.2-r1: Mon Mar 12 19:20:06 2018: 46 seconds
> util-linux-2.32-r4: Sun Jul 15 15:51:21 2018: 50 seconds
> util-linux-2.33-r1: Sun Jan 6 20:53:29 2019: 46 seconds
> util-linux-2.33-r1: Thu Feb 21 22:16:25 2019: 53 seconds
Is /usr/local/bin/emerge_time.sh a custom script of yours, or is it
available somewhere else? I usually use genlop to measure merge times, but
that package has a lengthy set of perl dependencies that I don't want to
pull into the catalyst seed chroots I am building/updating.
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
rsa6144/5C63F4E3F5C6C943 2015-04-27
177C 1972 1FB8 F254 BAD0 3E72 5C63 F4E3 F5C6 C943
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
next prev parent reply other threads:[~2019-02-28 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 9:36 [gentoo-dev] util-linux build time increase? Joshua Kinard
2019-02-21 12:29 ` Guilherme Amadio
2019-02-21 21:18 ` Kristian Fiskerstrand
2019-02-28 9:16 ` Joshua Kinard [this message]
2019-03-01 14:43 ` Kristian Fiskerstrand
2019-02-21 18:38 ` Georgy Yakovlev
2019-02-25 8:58 ` Tobias Klausmann
2019-02-25 10:07 ` Alexander Tsoy
2019-02-25 10:18 ` Alexander Tsoy
2019-02-28 9:13 ` Joshua Kinard
2019-03-01 15:01 ` Mart Raudsepp
2019-03-03 9:22 ` Joshua Kinard
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=69b62838-66ea-28d7-fb31-71a15e6d4f93@gentoo.org \
--to=kumba@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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