From: Vincent Legoll <vincent.legoll@gmail.com>
To: help-guix <help-guix@gnu.org>
Subject: Re: guix pull parallelism
Date: Sat, 13 Aug 2016 13:11:12 +0200 [thread overview]
Message-ID: <CAEwRq=r-La0=z7jhzygc2D5HrNRuTsHZLT2_BWRQo82XKqE+Rg@mail.gmail.com> (raw)
In-Reply-To: <CAEwRq=q1y3C+_nTPBvCFjMpbto48tvr2eq2jKJWTKq1TmFZSNw@mail.gmail.com>
Hello
> 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)...
OK I looked more into this, and now I'm seeing parts that are 1 CPU,
but the bulk is between 250% and 280%, so I think it's OK for a 3 CPU
VM. Disregard my previous observations.
--
Vincent Legoll
prev parent reply other threads:[~2016-08-13 11:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 14:31 guix pull parallelism Vincent Legoll
2016-08-13 11:11 ` Vincent Legoll [this message]
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=r-La0=z7jhzygc2D5HrNRuTsHZLT2_BWRQo82XKqE+Rg@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).