all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Joshua Branson <jbranso@dismail.de>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: bokr@bokr.com, "Félix Baylac Jacqué" <felix@alternativebit.fr>,
	guix-devel@gnu.org
Subject: Has guix system ever run a hardware survey?
Date: Fri, 28 Oct 2022 08:00:50 -0400	[thread overview]
Message-ID: <87tu3oximl.fsf_-_@dismail.de> (raw)
In-Reply-To: <87mt9hjpwp.fsf@gmail.com> (Maxim Cournoyer's message of "Thu, 27 Oct 2022 10:35:02 -0400")

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

> Hi,
>
> bokr@bokr.com writes:
>
> [...]
>
>>
>> I opted for the best SSD available for my purism librem13v4 at the time,
>> and was really happy with seems like 10x faster than the SATA SSD in my older
>> but still i7 x86_64 previous laptop. Prob really 4-5x faster.
>>
>
> Building Rust is mostly CPU dependent; I think fast single thread
> performance is key as not that much happen in parallel, IIRC.  The 3900X
> is a 12 cores (24 logical) beast.
>

This makes me wonder what sort of data we'd get if we asked guix system
users what sort of machine they use guix system on.

I've got an os-booted Thinkpad T400.  My core 2 duo seems pretty slow
compared to what ya'll have.  :)


  reply	other threads:[~2022-10-28 12:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-15  7:33 How long does it take to run the full rustc bootstrap chain? Félix Baylac Jacqué
2022-10-19 19:52 ` Efraim Flashner
2022-10-20  9:59 ` Ludovic Courtès
2022-10-20 20:11   ` Efraim Flashner
2022-10-22  8:57     ` Félix Baylac Jacqué
2022-10-22 13:48 ` Maxim Cournoyer
2022-10-26 19:37   ` bokr
2022-10-27 14:35     ` Maxim Cournoyer
2022-10-28 12:00       ` Joshua Branson [this message]
2022-10-31 19:02       ` Bengt Richter
2022-11-01 12:49         ` Maxim Cournoyer
2022-11-06  9:08     ` Efraim Flashner

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tu3oximl.fsf_-_@dismail.de \
    --to=jbranso@dismail.de \
    --cc=bokr@bokr.com \
    --cc=felix@alternativebit.fr \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.