On +2019-10-14 20:46:01 -0700, Chris Marusich wrote: > Hi, > > I've been trying to reconfigure my system on my x200 laptop. It's been > a day or two, and I've found that my computer has spent the last 25 > hours running fftwf tests. I know my laptop is rather weak (2 cores, 8 > GB of memory, an SSD) compared to most desktops today, but still, 25 > hours seems pretty long. > > Guix is running > > make check -j 2 > > which ultimately calls > > perl -w ./check.pl -r -c=30 -v --nthreads=2 > /tmp/guix-build-fftwf-3.3.8.drv-0/fftw-3.3.8/tests/bench > > which calls > > /tmp/guix-build-fftwf-3.3.8.drv-0/fftw-3.3.8/tests/.libs/bench -o > nthreads=2 --verbose=1 --verify //obcd34320 [... a lot of arguments ...] > > Despite the fact that "-j 2" was provided to make, only 1 CPU is pegged > at 100% utilization. I suppose I'll just wait and see what happens, but > 25 hours feels very long. It seems on ci.guix.gnu.org, the build times > are generally less than 1 hour: > > https://ci.guix.gnu.org/search?query=fftwf > > Is this normal, or should I kill the build and try again? What kind of > system is ci.guix.gnu.org building on (how many cores, how much memory)? > > -- > Chris
Hi Chris, Have you checked sensors for overheating that might induce CPU clock throttling? That happened to me when I did guix pull; guix upgrade; and it got to doing racket, which started out fast, but got really slow -- though it did finally crawl across the finish line, and cooled off. I guess it would show up in dmesg or journalctl -xe but I didn't look, sorry. HTH -- Regards, Bengt Richter
