Just noticed that even though my MAKEOPTS is set to -j4, portage was using all 16 threads to build mariadb 10.5.10.
ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-mtune=native -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CXXFLAGS="-mtune=native -O2 -pipe" FCFLAGS="-mtune=native -O2 -pipe" FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs config-protect-if-modified distlocks ebuild-locks fixlafiles ipc-sandbox merge-sync multilib-strict network-sandbox news parallel-fetch pid-sandbox preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch userpriv usersandbox usersync xattr" FFLAGS="-mtune=native -O2 -pipe" LDFLAGS="-Wl,-O1 -Wl,--as-needed" MAKEOPTS="-j4" ================================================================= Package Settings ================================================================= dev-db/mariadb-10.5.10::gentoo was built with the following: USE="backup extraengine pam server -bindist -columnstore -cracklib -debug -galera -innodb-lz4 -innodb-lzo -innodb-snappy -jdbc -jemalloc -kerberos -latin1 (-mroonga) -numa -odbc -oqgraph -perl -profiling -rocksdb -s3 (-selinux) -sphinx -s st-mariabackup -sst-rsync -static -systemd -systemtap -tcmalloc -test -xml -yassl" ABI_X86="(64)" CFLAGS="-mtune=native -O2 -pipe -fno-strict-aliasing" CXXFLAGS="-mtune=native -O2 -pipe -felide-constructors -fno-strict-aliasing" FEATURES="ebuild-locks strict pid-sandbox binpkg-logs distlocks merge-sync ipc-sandbox binpkg-docompress userfetch binpkg-dostrip qa-unresolved-soname-deps config-protect-if-modified unknown-features-warn network-sandbox unmerge-logs pres erve-libs protect-owned usersync sfperms fixlafiles assume-digests news sandbox parallel-fetch xattr unmerge-orphans usersandbox multilib-strict userpriv"
Created attachment 716472 [details] mariadb-htop.png How do you verify? I cannot reproduce, see attached screenshot where I am running `MAKEOPTS=-j1 ebuild mariadb-10.5.10.ebuild clean install`.
I've also checked with htop, but right now I cannot reproduce either :( Not sure if the server wasn't exhausted from other VM or why that happened. Thanks for giving it a shot, sorry for the noise.