unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: help-guix <help-guix@gnu.org>
Subject: Installer, recommended store size and hardware detection
Date: Wed, 06 Feb 2019 15:13:22 +0100	[thread overview]
Message-ID: <874l9hgg3h.fsf@ambrevar.xyz> (raw)

[-- Attachment #1: Type: text/plain, Size: 1939 bytes --]

Hi Guix!

During the Guix days we talked about the graphical installer and more
specifically about the recommended partition size to host the store.



Question for everyone:

    How much do you allocate to the store?



I don't think that a rule like "10% of the disk" is really what we
need.  The store "recommended size" does not grow linearly in my
understanding (but I could be missing a point).

I've tried with 25GB: it's way too painful.
Alex Kost once told me that he used 50GB and needn't `guix gc` for about
a year.

Too small a partition for the store can lead to a painful Guix
experience.  We don't want to frustrate newcomers.

Frustration typically occurs when the partition is full and the
user must run `guix gc`.  Running `guix gc` can lead to packages being
re-downloaded, etc.  This is even more painful on slow connections.

Of course, we all make different uses of Guix and the rate at which the
store gets filled may vary a lot from user to user.  It seems hard to
"recommend" something universal.  Let me try anyways:

  "How much space to we need so that the store does not get filled
  before a year with a default desktop.scm (with GNOME?), running weekly
  updates (i.e. about 52 times)."

This will take some time to measure ;)

I'm not sure we need to partition at all: is it a problem to use the
full disk?  If the user really wants to keep the store separate, we
could document a recommended minimum of 50GB for instance.



On a similar note, what do you think about adding hardware detection to
the installation process and help create a config.scm with the right
values for a specific machine?

Lewo from the Nix community told me they have hardware detection in
their config generation script:

  https://github.com/NixOS/nixpkgs/blob/c01eeda8e96c0fa63eb23df3df51403cc0589672/nixos/modules/installer/tools/nixos-generate-config.pl

What do you people think?

--
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

             reply	other threads:[~2019-02-06 14:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-06 14:13 Pierre Neidhardt [this message]
2019-02-06 14:47 ` Installer, recommended store size and hardware detection Giovanni Biscuolo
2019-02-09  8:39 ` Chris Marusich
2019-02-09 10:52 ` Jan Nieuwenhuizen
2019-02-12 16:41 ` Ludovic Courtès
2019-02-12 17:19   ` Pierre Neidhardt

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=874l9hgg3h.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --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).