[gentoo-user] 100% CPU load in qtwebengine

[gentoo-user] 100% CPU load in qtwebengine

[Peter Humphrey]

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

Hello list,

On this box I have this:

# grep '\-j' /etc/portage/make.conf
EMERGE_DEFAULT_OPTS="--jobs --load-average=4 [...] "
MAKEOPTS="-j4 -l4"

That seems to work well, except for a 20s period at the beginning of emerging 
qtwebengine, during which CPU load goes to 100%, according to gkrellm.

It seems that the ebuild runs a process other than make, ignoring make.conf. 
Does anyone here know what that might be, and why it disregards my 
preferences?

-- 
Regards,
Peter.

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

Re: [gentoo-user] 100% CPU load in qtwebengine

[Michael]

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

On Thursday, 23 May 2024 14:07:16 BST Peter Humphrey wrote:
> Hello list,
> 
> On this box I have this:
> 
> # grep '\-j' /etc/portage/make.conf
> EMERGE_DEFAULT_OPTS="--jobs --load-average=4 [...] "
> MAKEOPTS="-j4 -l4"
> 
> That seems to work well, except for a 20s period at the beginning of
> emerging qtwebengine, during which CPU load goes to 100%, according to
> gkrellm.
> 
> It seems that the ebuild runs a process other than make, ignoring make.conf.
> Does anyone here know what that might be, and why it disregards my
> preferences?

Does this happen while  the source archive is being decompressed?

You can check in top (press 'c' then 'Shift+v') to see what command/child 
process is eating up CPU time.  Use Page Up/Down to navigate through the long 
list.

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

Re: [gentoo-user] 100% CPU load in qtwebengine

[Peter Humphrey]

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

On Thursday, 23 May 2024 20:13:27 BST Michael wrote:
> On Thursday, 23 May 2024 14:07:16 BST Peter Humphrey wrote:
> > Hello list,
> > 
> > On this box I have this:
> > 
> > # grep '\-j' /etc/portage/make.conf
> > EMERGE_DEFAULT_OPTS="--jobs --load-average=4 [...] "
> > MAKEOPTS="-j4 -l4"
> > 
> > That seems to work well, except for a 20s period at the beginning of
> > emerging qtwebengine, during which CPU load goes to 100%, according to
> > gkrellm.
> > 
> > It seems that the ebuild runs a process other than make, ignoring
> > make.conf. Does anyone here know what that might be, and why it
> > disregards my preferences?
> 
> Does this happen while  the source archive is being decompressed?

It could be; the .tar.xz file is 288MB - but I didn't think bzip2 was 
multithreaded*. I tried to check by rerunning the emerge, but it found a 
Gentoo binary and went to fetch that.

*  And app-alternatives/bzip2 has installed bzip2.

-- 
Regards,
Peter.

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

Re: [gentoo-user] 100% CPU load in qtwebengine

[Michael]

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

On Friday, 24 May 2024 11:52:55 BST Peter Humphrey wrote:
> On Thursday, 23 May 2024 20:13:27 BST Michael wrote:
> > On Thursday, 23 May 2024 14:07:16 BST Peter Humphrey wrote:
> > > Hello list,
> > > 
> > > On this box I have this:
> > > 
> > > # grep '\-j' /etc/portage/make.conf
> > > EMERGE_DEFAULT_OPTS="--jobs --load-average=4 [...] "
> > > MAKEOPTS="-j4 -l4"
> > > 
> > > That seems to work well, except for a 20s period at the beginning of
> > > emerging qtwebengine, during which CPU load goes to 100%, according to
> > > gkrellm.
> > > 
> > > It seems that the ebuild runs a process other than make, ignoring
> > > make.conf. Does anyone here know what that might be, and why it
> > > disregards my preferences?
> > 
> > Does this happen while  the source archive is being decompressed?
> 
> It could be; the .tar.xz file is 288MB - but I didn't think bzip2 was
> multithreaded*. I tried to check by rerunning the emerge, but it found a
> Gentoo binary and went to fetch that.
> 
> *  And app-alternatives/bzip2 has installed bzip2.

The archive is compressed with xz, which in later versions can run in a 
multithreaded fashion.  I don't know if emerge calls upon it to operate with 
multiple threads (e.g. xz --threads 0 foo.xz).

PS. The bzip2 is single threaded and a slow compressor to boot, but pbzip2 is 
multithreaded.

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