unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Joshua Branson <jbranso@dismail.de>
Cc: 58357@debbugs.gnu.org
Subject: [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations'
Date: Thu, 09 Mar 2023 22:06:10 +0100	[thread overview]
Message-ID: <87r0tx4ou5.fsf@pelzflorian.de> (raw)
In-Reply-To: <871qq3bvdy.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Wed, 16 Nov 2022 01:22:49 +0100")

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> * But: Maybe the 2GB requirement should be documented after all.
>
>   IIRC someone somewhere suggested treating such high RAM usage a bug
>   and reducing module imports, for example, but not add a memory
>   requirement to the documentation.  I run a guix search and think the
>   de-facto requirement is somewhere slightly above 1GB?  But I guess I
>   test wrongly.
>
> I’m keeping this bug open because of the RAM thing.  WDYT?

Digging out this old bug, I no longer believe the RAM requirement needs
to be documented: We could document that users with little RAM should
enable swap space, but I don’t see a place where it fits. Also enabling
swap when programs crash seems like common knowledge not specific to
Guix.

Can we close?  What do you think?

Regards,
Florian




  parent reply	other threads:[~2023-03-09 21:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Yz/FHD608HeU6iIM@3900XT>
2022-10-07 14:24 ` [bug#58357] [Patch staging ] doc add a recommended system in 'Hardware Considerations' Joshua Branson via Guix-patches via
2022-10-08  9:55   ` pelzflorian (Florian Pelz)
2022-10-08 15:33   ` jbranso--- via Guix-patches via
2022-10-10 10:07     ` pelzflorian (Florian Pelz)
2022-10-14 15:12       ` Ludovic Courtès
2022-10-14 15:47         ` kiasoc5 via Guix-patches via
2022-10-15  9:47           ` pelzflorian (Florian Pelz)
2022-10-16 11:53             ` pelzflorian (Florian Pelz)
2022-10-14 17:09         ` pelzflorian (Florian Pelz)
2022-10-15 15:51           ` pelzflorian (Florian Pelz)
2022-10-17 16:35           ` Ludovic Courtès
2022-10-14 19:28         ` jbranso--- via Guix-patches via
2022-11-03 19:21         ` Ludovic Courtès
2022-11-16  0:22   ` pelzflorian (Florian Pelz)
2022-11-16 23:16     ` jbranso--- via Guix-patches via
2022-11-17 16:26       ` pelzflorian (Florian Pelz)
2022-11-19 14:06         ` Joshua Branson via Guix-patches via
2022-12-08 17:02           ` pelzflorian (Florian Pelz)
2023-03-09 21:06     ` pelzflorian (Florian Pelz) [this message]
2023-08-20 17:44       ` pelzflorian (Florian Pelz)

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=87r0tx4ou5.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=58357@debbugs.gnu.org \
    --cc=jbranso@dismail.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).