[gentoo-dev] util-linux build time increase?

[gentoo-dev] util-linux build time increase?

[Joshua Kinard]

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?

'genlop -t util-linux' output on my SGI system (some entries removed for
brevity):

     Thu Feb  1 11:26:33 2018 >>> sys-apps/util-linux-2.31.1
       merge time: 27 minutes and 48 seconds.

     Sat Mar 31 08:07:20 2018 >>> sys-apps/util-linux-2.32
       merge time: 28 minutes and 44 seconds.

     Mon Aug 27 06:21:30 2018 >>> sys-apps/util-linux-2.32.1
       merge time: 32 minutes and 58 seconds.

     Tue Nov 13 10:03:58 2018 >>> sys-apps/util-linux-2.33
       merge time: 1 hour, 19 minutes and 49 seconds.

     Fri Jan 11 09:20:21 2019 >>> sys-apps/util-linux-2.33.1
       merge time: 1 hour, 23 minutes and 37 seconds.

     Thu Feb 21 04:14:33 2019 >>> sys-apps/util-linux-2.33.1
       merge time: 1 hour, 25 minutes and 15 seconds.


-- 
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

Re: [gentoo-dev] util-linux build time increase?

[Guilherme Amadio]

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?
> 
> 'genlop -t util-linux' output on my SGI system (some entries removed for
> brevity):
> 
>      Thu Feb  1 11:26:33 2018 >>> sys-apps/util-linux-2.31.1
>        merge time: 27 minutes and 48 seconds.
> 
>      Sat Mar 31 08:07:20 2018 >>> sys-apps/util-linux-2.32
>        merge time: 28 minutes and 44 seconds.
> 
>      Mon Aug 27 06:21:30 2018 >>> sys-apps/util-linux-2.32.1
>        merge time: 32 minutes and 58 seconds.
> 
>      Tue Nov 13 10:03:58 2018 >>> sys-apps/util-linux-2.33
>        merge time: 1 hour, 19 minutes and 49 seconds.
> 
>      Fri Jan 11 09:20:21 2019 >>> sys-apps/util-linux-2.33.1
>        merge time: 1 hour, 23 minutes and 37 seconds.
> 
>      Thu Feb 21 04:14:33 2019 >>> sys-apps/util-linux-2.33.1
>        merge time: 1 hour, 25 minutes and 15 seconds.

Indeed. Here's what I see in one of my machines at work (Core i7-7820X):

     Fri Jul 20 16:31:38 2018 >>> sys-apps/util-linux-2.32.1
       merge time: 1 minute and 40 seconds.

     Fri Aug  3 14:38:40 2018 >>> sys-apps/util-linux-2.32.1
       merge time: 1 minute and 40 seconds.

     Wed Nov 14 16:49:40 2018 >>> sys-apps/util-linux-2.33
       merge time: 4 minutes and 24 seconds.

     Tue Feb  5 14:21:40 2019 >>> sys-apps/util-linux-2.33.1
       merge time: 4 minutes and 24 seconds.

Not sure what causes it.

Cheers,
-Guilherme

Re: [gentoo-dev] util-linux build time increase?

[Georgy Yakovlev]

[-- Attachment #1: Type: text/plain, Size: 736 bytes --]

On Thursday, February 21, 2019 1:36:24 AM PST 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?
> 

This may be related to this bug:
https://bugs.gentoo.org/447970

I have packages ( cpio and tar for example) that take hours to emerge on arm 
boards with FEATURES=sandbox, and couple of minutes without.
./configure getcwd test takes unreasonably long time under sandbox.

don't have util-linux statistics to show.

-- 
Georgy Yakovlev
Gentoo Linux Developer

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-dev] util-linux build time increase?

[Kristian Fiskerstrand]

[-- Attachment #1.1: Type: text/plain, Size: 1504 bytes --]

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


-- 
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: [gentoo-dev] util-linux build time increase?

[Tobias Klausmann]

Hi! 

On Thu, 21 Feb 2019, Georgy Yakovlev wrote:
> On Thursday, February 21, 2019 1:36:24 AM PST 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?
> > 
> 
> This may be related to this bug:
> https://bugs.gentoo.org/447970
> 
> I have packages ( cpio and tar for example) that take hours to emerge on arm 
> boards with FEATURES=sandbox, and couple of minutes without.
> ./configure getcwd test takes unreasonably long time under sandbox.
> 
> don't have util-linux statistics to show.

See https://bugs.gentoo.org/447970#c18 for an ugly, ugly hack to
prevent the wait time.

Regards,
Tobias

Re: [gentoo-dev] util-linux build time increase?

[Alexander Tsoy]

В Чт, 21/02/2019 в 04:36 -0500, Joshua Kinard пишет:
> 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?
> 
> 'genlop -t util-linux' output on my SGI system (some entries removed
> for
> brevity):
> 
>      Thu Feb  1 11:26:33 2018 >>> sys-apps/util-linux-2.31.1
>        merge time: 27 minutes and 48 seconds.
> 
>      Sat Mar 31 08:07:20 2018 >>> sys-apps/util-linux-2.32
>        merge time: 28 minutes and 44 seconds.
> 
>      Mon Aug 27 06:21:30 2018 >>> sys-apps/util-linux-2.32.1
>        merge time: 32 minutes and 58 seconds.
> 
>      Tue Nov 13 10:03:58 2018 >>> sys-apps/util-linux-2.33
>        merge time: 1 hour, 19 minutes and 49 seconds.
> 
>      Fri Jan 11 09:20:21 2019 >>> sys-apps/util-linux-2.33.1
>        merge time: 1 hour, 23 minutes and 37 seconds.
> 
>      Thu Feb 21 04:14:33 2019 >>> sys-apps/util-linux-2.33.1
>        merge time: 1 hour, 25 minutes and 15 seconds.
> 

2.33 was changed to use python-r1 eclass instead of python-single-r1
eclass. And the increase of build time seems caused by an out-of-source 
build for each python implementation. Some libraries are built several
times (for native abi + for each python implementation).

Re: [gentoo-dev] util-linux build time increase?

[Alexander Tsoy]

В Пн, 25/02/2019 в 13:07 +0300, Alexander Tsoy пишет:
> В Чт, 21/02/2019 в 04:36 -0500, Joshua Kinard пишет:
> > 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?
> > 
> > 'genlop -t util-linux' output on my SGI system (some entries
> > removed
> > for
> > brevity):
> > 
> >      Thu Feb  1 11:26:33 2018 >>> sys-apps/util-linux-2.31.1
> >        merge time: 27 minutes and 48 seconds.
> > 
> >      Sat Mar 31 08:07:20 2018 >>> sys-apps/util-linux-2.32
> >        merge time: 28 minutes and 44 seconds.
> > 
> >      Mon Aug 27 06:21:30 2018 >>> sys-apps/util-linux-2.32.1
> >        merge time: 32 minutes and 58 seconds.
> > 
> >      Tue Nov 13 10:03:58 2018 >>> sys-apps/util-linux-2.33
> >        merge time: 1 hour, 19 minutes and 49 seconds.
> > 
> >      Fri Jan 11 09:20:21 2019 >>> sys-apps/util-linux-2.33.1
> >        merge time: 1 hour, 23 minutes and 37 seconds.
> > 
> >      Thu Feb 21 04:14:33 2019 >>> sys-apps/util-linux-2.33.1
> >        merge time: 1 hour, 25 minutes and 15 seconds.
> > 
> 
> 2.33 was changed to use python-r1 eclass instead of python-single-r1
> eclass. And the increase of build time seems caused by an out-of-
> source 
> build for each python implementation. Some libraries are built
> several
> times (for native abi + for each python implementation).

And there is additional configure run for each python implementation.

Re: [gentoo-dev] util-linux build time increase?

[Joshua Kinard]

On 2/25/2019 05:18, Alexander Tsoy wrote:
> В Пн, 25/02/2019 в 13:07 +0300, Alexander Tsoy пишет:
>> В Чт, 21/02/2019 в 04:36 -0500, Joshua Kinard пишет:
>>> 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?
>>>
>>> 'genlop -t util-linux' output on my SGI system (some entries
>>> removed
>>> for
>>> brevity):
>>>
>>>      Thu Feb  1 11:26:33 2018 >>> sys-apps/util-linux-2.31.1
>>>        merge time: 27 minutes and 48 seconds.
>>>
>>>      Sat Mar 31 08:07:20 2018 >>> sys-apps/util-linux-2.32
>>>        merge time: 28 minutes and 44 seconds.
>>>
>>>      Mon Aug 27 06:21:30 2018 >>> sys-apps/util-linux-2.32.1
>>>        merge time: 32 minutes and 58 seconds.
>>>
>>>      Tue Nov 13 10:03:58 2018 >>> sys-apps/util-linux-2.33
>>>        merge time: 1 hour, 19 minutes and 49 seconds.
>>>
>>>      Fri Jan 11 09:20:21 2019 >>> sys-apps/util-linux-2.33.1
>>>        merge time: 1 hour, 23 minutes and 37 seconds.
>>>
>>>      Thu Feb 21 04:14:33 2019 >>> sys-apps/util-linux-2.33.1
>>>        merge time: 1 hour, 25 minutes and 15 seconds.
>>>
>>
>> 2.33 was changed to use python-r1 eclass instead of python-single-r1
>> eclass. And the increase of build time seems caused by an out-of-
>> source 
>> build for each python implementation. Some libraries are built
>> several
>> times (for native abi + for each python implementation).
> 
> And there is additional configure run for each python implementation.

Hmm, this might explain things, somewhat.  I think there's possibly some
truth to the getcwd bit discussed earlier, but that may be limited to glibc
only.  util-linux-2.33.1 on my uclibc-ng chroot took about ~25mins.  Have to
re-time the glibc build to see if it's something w/ the libc implementation.

Temp workaround I guess is to cut down on the PYTHON_TARGETS before my next
catalyst attempt.  2.7 + 3.7 should be enough...

-- 
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

Re: [gentoo-dev] util-linux build time increase?

[Joshua Kinard]

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

Re: [gentoo-dev] util-linux build time increase?

[Kristian Fiskerstrand]

[-- Attachment #1.1: Type: text/plain, Size: 715 bytes --]

On 2/28/19 10:16 AM, Joshua Kinard wrote:
> 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.

Its just a a quick way to propagate this wrapper on multiple computers;

# cat /usr/local/bin/emerge_time.sh
#!/bin/bash

if [[ $# < 1     ]]; then
        echo "Usage: ${0} <pkgname>";
        exit;
fi

qlop -tHvg "$1"


-- 
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: [gentoo-dev] util-linux build time increase?

[Mart Raudsepp]

[-- Attachment #1: Type: text/plain, Size: 3807 bytes --]

Ühel kenal päeval, N, 28.02.2019 kell 04:13, kirjutas Joshua Kinard:
> On 2/25/2019 05:18, Alexander Tsoy wrote:
> > В Пн, 25/02/2019 в 13:07 +0300, Alexander Tsoy пишет:
> > > В Чт, 21/02/2019 в 04:36 -0500, Joshua Kinard пишет:
> > > > 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?
> > > > 
> > > > 'genlop -t util-linux' output on my SGI system (some entries
> > > > removed
> > > > for
> > > > brevity):
> > > > 
> > > >      Thu Feb  1 11:26:33 2018 >>> sys-apps/util-linux-2.31.1
> > > >        merge time: 27 minutes and 48 seconds.
> > > > 
> > > >      Sat Mar 31 08:07:20 2018 >>> sys-apps/util-linux-2.32
> > > >        merge time: 28 minutes and 44 seconds.
> > > > 
> > > >      Mon Aug 27 06:21:30 2018 >>> sys-apps/util-linux-2.32.1
> > > >        merge time: 32 minutes and 58 seconds.
> > > > 
> > > >      Tue Nov 13 10:03:58 2018 >>> sys-apps/util-linux-2.33
> > > >        merge time: 1 hour, 19 minutes and 49 seconds.
> > > > 
> > > >      Fri Jan 11 09:20:21 2019 >>> sys-apps/util-linux-2.33.1
> > > >        merge time: 1 hour, 23 minutes and 37 seconds.
> > > > 
> > > >      Thu Feb 21 04:14:33 2019 >>> sys-apps/util-linux-2.33.1
> > > >        merge time: 1 hour, 25 minutes and 15 seconds.
> > > > 
> > > 
> > > 2.33 was changed to use python-r1 eclass instead of python-
> > > single-r1
> > > eclass. And the increase of build time seems caused by an out-of-
> > > source 
> > > build for each python implementation. Some libraries are built
> > > several
> > > times (for native abi + for each python implementation).
> > 
> > And there is additional configure run for each python
> > implementation.
> 
> Hmm, this might explain things, somewhat.  I think there's possibly
> some
> truth to the getcwd bit discussed earlier, but that may be limited to
> glibc
> only.

Right, util-linux doesn't conduct that test. coreutils and tar do,
maybe some more.
That doesn't mean running with sandbox doesn't have a slowdown effect -
it most certainly does, just hopefully not so drastic as that
particular case - it involves glibc own generic getcwd being slow with
long paths, and sandbox calling it three times for its access checks
even for mkdir call, just to error with ENAMETOOLONG, in addition to
many getcwd calls the configure check itself does. So it's slow even
without sandbox, but with sandbox that slowness is doubled or more.
That has made me wonder if maybe by having some more ENAMETOOLONGs
earlier, the test would finish earlier, instead of slowly spinning
through paths that are in length between PATH_MAX and PATH_MAX*2, when
it's slow..
But not sure why these m4 macros seems to be calling getcwd after each
mkdir+chdirm etc just to get a boolean configure check result. Didn't
look into the specific case, I only debugged the test case that just
loops mkdir+chdir.
Someone should maybe convert these project to meson and do that check
smarter :D

> util-linux-2.33.1 on my uclibc-ng chroot took about ~25mins.  Have to
> re-time the glibc build to see if it's something w/ the libc
> implementation.
> 
> Temp workaround I guess is to cut down on the PYTHON_TARGETS before
> my next
> catalyst attempt.  2.7 + 3.7 should be enough...

Personally I seem to get by with just USE=-python on util-linux (it's
actually not globally enabled on my systems, it seems). Otherwise,
sure, if the slowness is in configure.


Mart

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

Re: [gentoo-dev] util-linux build time increase?

[Joshua Kinard]

On 3/1/2019 10:01, Mart Raudsepp wrote:
> Ühel kenal päeval, N, 28.02.2019 kell 04:13, kirjutas Joshua Kinard:
>> On 2/25/2019 05:18, Alexander Tsoy wrote:
>>> В Пн, 25/02/2019 в 13:07 +0300, Alexander Tsoy пишет:
>>>> В Чт, 21/02/2019 в 04:36 -0500, Joshua Kinard пишет:
>>>>> 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?
>>>>>
>>>>> 'genlop -t util-linux' output on my SGI system (some entries
>>>>> removed
>>>>> for
>>>>> brevity):
>>>>>
>>>>>      Thu Feb  1 11:26:33 2018 >>> sys-apps/util-linux-2.31.1
>>>>>        merge time: 27 minutes and 48 seconds.
>>>>>
>>>>>      Sat Mar 31 08:07:20 2018 >>> sys-apps/util-linux-2.32
>>>>>        merge time: 28 minutes and 44 seconds.
>>>>>
>>>>>      Mon Aug 27 06:21:30 2018 >>> sys-apps/util-linux-2.32.1
>>>>>        merge time: 32 minutes and 58 seconds.
>>>>>
>>>>>      Tue Nov 13 10:03:58 2018 >>> sys-apps/util-linux-2.33
>>>>>        merge time: 1 hour, 19 minutes and 49 seconds.
>>>>>
>>>>>      Fri Jan 11 09:20:21 2019 >>> sys-apps/util-linux-2.33.1
>>>>>        merge time: 1 hour, 23 minutes and 37 seconds.
>>>>>
>>>>>      Thu Feb 21 04:14:33 2019 >>> sys-apps/util-linux-2.33.1
>>>>>        merge time: 1 hour, 25 minutes and 15 seconds.
>>>>>
>>>>
>>>> 2.33 was changed to use python-r1 eclass instead of python-
>>>> single-r1
>>>> eclass. And the increase of build time seems caused by an out-of-
>>>> source 
>>>> build for each python implementation. Some libraries are built
>>>> several
>>>> times (for native abi + for each python implementation).
>>>
>>> And there is additional configure run for each python
>>> implementation.
>>
>> Hmm, this might explain things, somewhat.  I think there's possibly
>> some
>> truth to the getcwd bit discussed earlier, but that may be limited to
>> glibc
>> only.
> 
> Right, util-linux doesn't conduct that test. coreutils and tar do,
> maybe some more.
> That doesn't mean running with sandbox doesn't have a slowdown effect -
> it most certainly does, just hopefully not so drastic as that
> particular case - it involves glibc own generic getcwd being slow with
> long paths, and sandbox calling it three times for its access checks
> even for mkdir call, just to error with ENAMETOOLONG, in addition to
> many getcwd calls the configure check itself does. So it's slow even
> without sandbox, but with sandbox that slowness is doubled or more.
> That has made me wonder if maybe by having some more ENAMETOOLONGs
> earlier, the test would finish earlier, instead of slowly spinning
> through paths that are in length between PATH_MAX and PATH_MAX*2, when
> it's slow..
> But not sure why these m4 macros seems to be calling getcwd after each
> mkdir+chdirm etc just to get a boolean configure check result. Didn't
> look into the specific case, I only debugged the test case that just
> loops mkdir+chdir.
> Someone should maybe convert these project to meson and do that check
> smarter :D
> 
>> util-linux-2.33.1 on my uclibc-ng chroot took about ~25mins.  Have to
>> re-time the glibc build to see if it's something w/ the libc
>> implementation.
>>
>> Temp workaround I guess is to cut down on the PYTHON_TARGETS before
>> my next
>> catalyst attempt.  2.7 + 3.7 should be enough...
> 
> Personally I seem to get by with just USE=-python on util-linux (it's
> actually not globally enabled on my systems, it seems). Otherwise,
> sure, if the slowness is in configure.
> 
> 
> Mart

Yeah, I forgot I had a global 'python' USE set on the Octane.  It's not been
fun trying to disentangle the mess after removing it.  But...

Before:
     Thu Feb 21 04:14:33 2019 >>> sys-apps/util-linux-2.33.1
       merge time: 1 hour, 25 minutes and 15 seconds.

After:
     Sun Mar  3 03:22:26 2019 >>> sys-apps/util-linux-2.33.1
       merge time: 18 minutes and 35 seconds.


The above is also with sandbox disabled for now until the getcwd issue is
fixed.  If I'd known that sandbox slowed stuff down that much, I'd have
stopped using it a long time ago.  This machine is top of its class, but
it's taking longer to build stuff as new versions come out due to new
features being added, compiler taking longer, etc.  I miss the days when
this thing could build gcc in 3-4 hours.  More like 14hrs now.

-- 
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