From: Csepp <raingloom@riseup.net>
To: kiasoc5 <kiasoc5@disroot.org>
Cc: Nicolas Graves <ngraves@ngraves.fr>, guix-devel@gnu.org
Subject: Re: Guix / Nix Benchmarks
Date: Tue, 20 Jun 2023 07:24:34 +0200 [thread overview]
Message-ID: <87zg4ur9fo.fsf@riseup.net> (raw)
In-Reply-To: <b530ba8b-2b3e-9a8a-e230-5fb0e4e6df3d@disroot.org>
kiasoc5 <kiasoc5@disroot.org> writes:
> On 6/19/23 08:54, Nicolas Graves via Development of GNU Guix and the
> GNU System distribution. wrote:
>> One of the criticism that can be read online about Guix (compared to
>> Nix) is its speed. I have never tried Nix and probably won't in a near
>> future, but I was wondering if some work has been made to compare them
>> on basic tasks (package installation, removal...) (the reason why I ask
>> is to be able to give an honest answer to someone hesitating between
>> both).
>>
>
> At least package installation is faster with Nix. One reason is that
> Hydra (their "substitute server") has faster download speeds compared
> to CI/Bordeaux, likely due to multiple geographical locations/mirrors.
Conversely, Nix itself is likely to be slower than Guile. I remember
search being so memory intensive with Nix that it got OOM killed even
with 4 GB of RAM, although they may have fixed that since.
next prev parent reply other threads:[~2023-06-20 5:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 12:54 Guix / Nix Benchmarks Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-06-19 18:55 ` kiasoc5
2023-06-20 5:24 ` Csepp [this message]
2023-06-20 9:14 ` Efraim Flashner
2023-06-20 10:45 ` W. T. Meyer
2023-06-20 14:48 ` Nicolas Graves via Development of GNU Guix and the GNU System distribution.
2023-07-02 20:30 ` Ludovic Courtès
2023-07-02 21:42 ` Ricardo Wurmus
2023-07-02 22:02 ` Wilko Meyer
2023-07-03 6:17 ` Ricardo Wurmus
2023-08-19 12:11 ` Simon Tournier
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=87zg4ur9fo.fsf@riseup.net \
--to=raingloom@riseup.net \
--cc=guix-devel@gnu.org \
--cc=kiasoc5@disroot.org \
--cc=ngraves@ngraves.fr \
/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).