From: Chris Marusich <cmmarusich@gmail.com>
To: Marco van Hulten <marco@hulten.org>
Cc: help-guix@gnu.org
Subject: Re: upgrading systems with <= 2 GiB RAM
Date: Mon, 11 Nov 2019 20:32:24 -0800 [thread overview]
Message-ID: <87sgmt1zqf.fsf@gmail.com> (raw)
In-Reply-To: <20191031155420.78fab93a@gfi063209.klientdrift.uib.no> (Marco van Hulten's message of "Thu, 31 Oct 2019 15:54:20 +0100")
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
Marco van Hulten <marco@hulten.org> writes:
> Hello—
>
> I have an oldish amd64 system with 2 GiB of memory, but it is fast
> enough to use as a media center. Guix was last updated early this
> year. Upgrading it now takes many days. It keeps on swapping (using
> quite consistently 2 of 4 GiB of swap available).
>
> Do you think the swapping is the reason that it takes so long?
>
> Would it be a general strong advice to use more than 2 GiB, or is it
> likely useful to give details like which program is compiling (as in a
> proper bug report)?
>
> —Marco
If you wind up compiling things, it will likely fail on larger builds.
For example, my old machine which has 2 GB of RAM fails when trying to
compile IceCat. I suppose the only possible solution is to always use
pre-built binaries, either by using substitutes or by building first on
a machine with more memory, and then copying the results over via "guix
copy" or "guix archive".
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2019-11-12 4:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 14:54 upgrading systems with <= 2 GiB RAM Marco van Hulten
2019-10-31 22:49 ` Marius Bakke
2019-11-03 14:14 ` Marco van Hulten
2019-11-03 15:48 ` Marius Bakke
2019-11-12 4:32 ` Chris Marusich [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=87sgmt1zqf.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=help-guix@gnu.org \
--cc=marco@hulten.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).