From: Marco van Hulten <marco@hulten.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: successful installation, but problems updating
Date: Thu, 09 Nov 2017 20:27:37 +0100 [thread overview]
Message-ID: <20171109202737.19fd288b@jasniac.instanton> (raw)
In-Reply-To: <877euzio7k.fsf@gnu.org>
Ludo'-
Op 09 nov 14:19 schreef Ludovic Courtès:
> How many CPUs and how much RAM does this machine have? Does it help in
> any way to run “guix pull --cores=2”, thereby limiting CPU usage to two
> cores?
I have two processors, so I tried to run it on one, and it worked:
```
root@watson ~# time guix pull --cores=1
Starting download of /tmp/guix-file.kQQ8AM
From https://git.savannah.gnu.org/cgit/guix.git/snapshot/master.tar.gz...
….tar.gz 2.8MiB/s 00:05 | 13.8MiB transferred
unpacking '/gnu/store/v1zs6bfaam79wp9pf1ja9k8ys4f3dm2s-guix-latest.tar.gz'...
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
The following derivation will be built:
/gnu/store/5admrckcwdqgqix1d7hfj23fczk2k7ss-guix-latest.drv
substitute: updating list of substitutes from 'https://mirror.hydra.gnu.org'... 100.0%
copying and compiling to '/gnu/store/pmk3b4sqqnizkhmrxx7cdyj4as0ym6r4-guix-latest' with Guile 2.2.2...
loading... 26.1% of 647 filesrandom seed for tests: 1510251772
compiling... 100.0% of 647 files
Some deprecated features have been used. Set the environment
variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
program to get more information. Set it to "no" to suppress
this message.
updated GNU Guix successfully deployed under `/root/.config/guix/latest'
real 37m0.478s
user 0m2.963s
sys 0m0.508s
```
Right now I'm updating packages, and things are looking up.
Do you have any idea what went wrong when using both cores?
I am conflating cores and processors right now. I think these are
equal for this system, but I'm not sure. I have an Intel Core2 Duo.
/proc/cpuinfo shows two processes. Furthermore, I presume that
`--cores N` actually means that guix spawns N processes.
-Marco
next prev parent reply other threads:[~2017-11-09 19:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-06 8:16 successful installation, but problems updating Marco van Hulten
2017-11-06 9:43 ` Carlo Zancanaro
2017-11-06 20:06 ` Marco van Hulten
2017-11-07 9:20 ` Ludovic Courtès
2017-11-07 10:58 ` Marco van Hulten
2017-11-08 1:37 ` Marco van Hulten
2017-11-09 7:45 ` Marco van Hulten
2017-11-09 13:19 ` Ludovic Courtès
2017-11-09 19:27 ` Marco van Hulten [this message]
2017-11-09 20:46 ` Marco van Hulten
2017-11-09 20:53 ` Mathieu Othacehe
2017-11-10 7:26 ` Marco van Hulten
2017-11-10 16:35 ` Leo Famulari
2017-11-11 22:23 ` Marco van Hulten
2017-11-12 1:26 ` Leo Famulari
2017-11-06 10:18 ` Thomas Sigurdsen
2017-11-10 5:58 ` Chris Marusich
2017-11-10 7:23 ` Carlo Zancanaro
2017-11-10 16:28 ` Leo Famulari
2017-11-10 23:30 ` Chris Marusich
2017-11-11 15:29 ` myglc2
2017-11-11 17:05 ` Chris Marusich
2017-11-11 18:06 ` myglc2
2017-11-12 1:29 ` Leo Famulari
2017-11-12 3:36 ` myglc2
2017-11-12 4:45 ` Leo Famulari
2017-11-12 11:10 ` Chris Marusich
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=20171109202737.19fd288b@jasniac.instanton \
--to=marco@hulten.org \
--cc=help-guix@gnu.org \
--cc=ludo@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).