From: Chris Marusich <cmmarusich@gmail.com>
To: guix-devel@gnu.org
Cc: fftw@fftw.org
Subject: fftwf tests running for 25+ hours - is this normal?
Date: Mon, 14 Oct 2019 20:46:01 -0700 [thread overview]
Message-ID: <87o8yi4qo6.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next reply other threads:[~2019-10-15 3:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 3:46 Chris Marusich [this message]
2019-10-15 5:52 ` fftwf tests running for 25+ hours - is this normal? Bengt Richter
2019-10-15 6:38 ` Pierre Neidhardt
2019-10-15 18:32 ` Chris Marusich
2019-10-16 5:11 ` Bengt Richter
2019-10-16 5:29 ` Bengt Richter
2019-10-17 4:06 ` Chris Marusich
2019-10-15 14:12 ` Matteo Frigo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8yi4qo6.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=fftw@fftw.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.