Re: [gentoo-user] Specific MAKEOPTS for one package

2018-10-01 Thread Walter Dnes
On Mon, Oct 01, 2018 at 12:34:25PM +0100, Klaus Ethgen wrote

> First, cpufreq-set seems to be not available on gentoo anymore. Doesn't
> matter, just giving it a try.

  I wrote up a bash script (Yes!) to do cpu speed control.  As a script,
it has no external dependancies.  The only requirements are that the CPU
supports frequency scaling, and that the appropriate CPU governors are
compiled into the kernel.

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications



Re: [gentoo-user] Specific MAKEOPTS for one package

2018-10-01 Thread Michael Orlitzky
On 10/01/2018 07:34 AM, Klaus Ethgen wrote:
> 
> First, cpufreq-set seems to be not available on gentoo anymore. Doesn't
> matter, just giving it a try.
> 

You want sys-power/cpupower these days.



Re: [gentoo-user] Is this a genlop bug?

2018-10-01 Thread Arve Barsnes
On Mon, 1 Oct 2018 at 14:03, Andrew Udvare  wrote:
> > On 2018-10-01, at 05:25, Peter Humphrey  wrote:
> > This looks like a bug to me.
>
> It is not a bug. The manpage says it takes name or category/name. In the 
> former case it has to match anything named rust. There are two packages named 
> exactly 'rust': dev-lang/rust and virtual/rust.

The '-c' parameter doesn't (need to) take either name or category/name
so I don't see how this isn't a bug. Getting an ETA average for more
than one package and comparing it against the currently merging
package makes no sense.

Cheers,
Arve



Re: [gentoo-user] Is this a genlop bug?

2018-10-01 Thread Andrew Udvare


> On 2018-10-01, at 05:25, Peter Humphrey  wrote:
> 
> Hello list,
> 
> When I run "genlop -c" is it supposed to include the whole cat/pkg name in 
> its 
> calculations, or just the pkgname? I saw this today:
> 
> $ genlop -c   
> Currently merging 8 out of 16
> * dev-lang/rust-1.29.1 
>   current merge time: 13 minutes and 38 seconds.
>   ETA: 1 minute and 58 seconds.
> $ genlop -t rust | grep second
>   merge time: 29 minutes and 26 seconds.
>   merge time: 4 seconds.
>   merge time: 10 seconds.
>   merge time: 32 minutes and 44 seconds.
> $ genlop -t dev-lang/rust | grep second
>   merge time: 29 minutes and 26 seconds.
>   merge time: 32 minutes and 44 seconds.
> 
> This looks like a bug to me.

It is not a bug. The manpage says it takes name or category/name. In the former 
case it has to match anything named rust. There are two packages named exactly 
'rust': dev-lang/rust and virtual/rust.

Andrew


Re: [gentoo-user] Specific MAKEOPTS for one package

2018-10-01 Thread Klaus Ethgen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Am Fr den 28. Sep 2018 um  5:19 schrieb Walter Dnes:
> On Tue, Sep 25, 2018 at 02:25:50PM +0100, Klaus Ethgen wrote
> > I have set MAKEOPTS="-j3" in my make.conf.
>   I assume you have 2 cores on your cpu and you're adding 1 as per the
> ancient rule.

True.

> That may not be the best option anyways.  See
> https://blogs.gentoo.org/ago/2013/01/14/makeopts-jcore-1-is-not-the-best-optimization/
> The author of the blog post ran multiple tests, and concluded that
> setting MAKEOPTS -j to the actual number of cores is slightly faster.
> Years ago, the gcc compiler was less efficient, and adding 1 to -j did
> improve compilation speed.  That is apparently not the case today.

Interesting thoughts.

First, cpufreq-set seems to be not available on gentoo anymore. Doesn't
matter, just giving it a try.

It came out, that all build times have nearly the same sys times but the
user and real times vary. Funny, this is a two CPU machine but the build
with -j1 consumes the least user time. Just the real value gives the
same pattern than on the site.

Regards
   Klaus
- -- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-BEGIN PGP SIGNATURE-
Comment: Charset: ISO-8859-1

iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAluyBjsACgkQpnwKsYAZ
9qyOqAv+KPCXk0uftuWv7rQwzQlV9wgs9RH9OLuy9k8yXiKUTmIIjcqO7xMRJGKJ
bCQCqo0IrA+ZGnKbDYWydPTeFwM05Sa6NYHlonEcyK3tJ83GkU6J1xedhemsuCmF
eyfDn9RfQjie4C90xfCnEsov46VMcSKae1aokl2olTPPrsGcG+hjQNI6jpEtyjRu
9qzjxCdWbYho5E6PRoa4ZTvKCLSeaEiJl9fFY8Ouyy747sJPQf1lrsGsDmaf9Zxh
psvUQQGmeja1l66fvi82P19BWG3EHLw08hFJut/uKvpFHSDI+kmXixJHp7TY3avo
tmqeir1b/bq7tbBLkmpbCcOS7eYUDK0YwwENMcMQPk2l4ZC6e0xkVIlV3ZcubG2W
QF9JUSKD2bN1h4He8y/APzFFSwkzGY38nQxTTZwXoCRUZqELDHXfqPJjK8x7qE7J
5OcuPkytVcM0vbXes6Yi38MfRXMt9Re4d9uAscL12vBZet/50fUA2y9eRCP3SW0T
WHSMQ7ZT
=a+QA
-END PGP SIGNATURE-



[gentoo-user] Is this a genlop bug?

2018-10-01 Thread Peter Humphrey
Hello list,

When I run "genlop -c" is it supposed to include the whole cat/pkg name in its 
calculations, or just the pkgname? I saw this today:

$ genlop -c   
 Currently merging 8 out of 16
 * dev-lang/rust-1.29.1 
   current merge time: 13 minutes and 38 seconds.
   ETA: 1 minute and 58 seconds.
$ genlop -t rust | grep second
   merge time: 29 minutes and 26 seconds.
   merge time: 4 seconds.
   merge time: 10 seconds.
   merge time: 32 minutes and 44 seconds.
$ genlop -t dev-lang/rust | grep second
   merge time: 29 minutes and 26 seconds.
   merge time: 32 minutes and 44 seconds.

This looks like a bug to me.

-- 
Regards,
Peter.