From: swedebugia <swedebugia@riseup.net>
To: Laura Lazzati <laura.lazzati.15@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: Question about Guix documentation
Date: Thu, 13 Dec 2018 09:29:00 +0100 [thread overview]
Message-ID: <014db2c0-b976-ef3e-da74-77aea3522e86@riseup.net> (raw)
In-Reply-To: <CAPNLzUOG5-yQakvG=oN-shjozLCZLHfjbkcefHtJYbPi4z=5bg@mail.gmail.com>
On 2018-12-03 00:39, Laura Lazzati wrote:
>> 1GB of RAM? That is a *lot* :)
>> I have 2 GB on my 2 day-to-day laptops. 1 with GNOME3 GuixSD and 1 with
>> Parabola+MATE. Both work fine and I rarely have to wait for other
>> programs than the really heavy ones (Libreoffice comes to mind).
> Oh no! my retroPC is fancy :O and I did not know :) I was going to add
> that I did almost up to 4th year of university with it but felt
> ashamed. I guess you know where the name MATE comes from ;), it is at
> the end of the site. I will check the processor. because I don't
> remember how many cores it has.
Actually what makes a bigger difference than CPU speed/number of cores
is the hdd/ssd speed. Because of the heavy store/hardlinking/profile
generation hooks etc. Guix is quite disk I/O intensive.
So installing ssd in your old laptop would probably speed things up.
They are cheep these days and you can get away with buying a small one
for little money 32Gb is enough if you trim generations and run guix gc
regularly).
--
Cheers
Swedebugia
next prev parent reply other threads:[~2018-12-13 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 13:36 Question about Guix documentation Laura Lazzati
2018-12-01 17:17 ` Giovanni Biscuolo
2018-12-02 15:05 ` Laura Lazzati
2018-12-02 21:36 ` swedebugia
2018-12-02 23:39 ` Laura Lazzati
2018-12-13 8:29 ` swedebugia [this message]
2018-12-13 13:45 ` Laura Lazzati
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=014db2c0-b976-ef3e-da74-77aea3522e86@riseup.net \
--to=swedebugia@riseup.net \
--cc=guix-devel@gnu.org \
--cc=laura.lazzati.15@gmail.com \
--cc=ricardo.wurmus@mdc-berlin.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).