From: Vincent Legoll <vincent.legoll@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: guix pull parallelism
Date: Fri, 12 Aug 2016 16:31:58 +0200 [thread overview]
Message-ID: <CAEwRq=q1y3C+_nTPBvCFjMpbto48tvr2eq2jKJWTKq1TmFZSNw@mail.gmail.com> (raw)
Hello,
it does look like some parts of "guix pull" are parallelized
as I was seeing guix-daemon's child guile take 200% CPU during :
loading... 23.5% of 511 filesrandom seed for tests: 1471011793
loading... 99.8% of 511 files
compiling... 99.6% of 511 files
So far so good, nice to use those cores that would stay idle.
But...
$ grep -c ^processor /proc/cpuinfo
3
So why is that not a ~300% is there only parallelism for 2 threads,
or is it an unintended side effect and there is no parallelism ?
If it had been ~100% or ~300% I would not have asked, but that
200% looks wrong one (missed a core) way or the other (no
parallelism)...
Thanks for feeding my curiosity...
--
Vincent Legoll
next reply other threads:[~2016-08-12 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 14:31 Vincent Legoll [this message]
2016-08-13 11:11 ` guix pull parallelism Vincent Legoll
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAEwRq=q1y3C+_nTPBvCFjMpbto48tvr2eq2jKJWTKq1TmFZSNw@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=help-guix@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).