unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: "Félix Baylac Jacqué" <felix@alternativebit.fr>, guix-devel@gnu.org
Subject: Re: How long does it take to run the full rustc bootstrap chain?
Date: Mon, 31 Oct 2022 20:02:50 +0100	[thread overview]
Message-ID: <20221031185630.GA3567@LionPure> (raw)
In-Reply-To: <87mt9hjpwp.fsf@gmail.com>

Hi again, thanks for your reply...

On +2022-10-27 10:35:02 -0400, Maxim Cournoyer wrote:
> Hi,
> 

(Oops, pasting back alternative I thought would be faster)
> > So above combo command line now gives me
> > --8<---------------cut here---------------start------------->8---
> > SIZE MODEL                          TYPE  TRAN   VENDOR   NAME
> > 465.8G Samsung SSD 970 EVO Plus 500GB disk  nvme            nvme0n1
> > 
> > 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981
> > $ 
> > --8<---------------cut here---------------end--------------->8---

[...]

--8<---------------cut here---------------start------------->8---
> $ lsblk -o size,model,type,tran,vendor,name|grep -Ei 'ssd|model';echo;lspci |grep -i nvme
>   SIZE MODEL                      TYPE  TRAN   VENDOR   NAME
> 465.8G Samsung SSD 860 EVO 500GB  disk  sata   ATA      sda
> 931.5G Samsung SSD 840 EVO 1TB    disk  sata   ATA      sdc
> --8<---------------cut here---------------end--------------->8---
> 
> 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.
>

Hm, just TRAN sata, no nvme, so it's going to be slow, but
what is the effect on what you timed?

Is there an easy way to get a measure of how many GB went
through those SATA channels during what you timed? That
would give an idea of what faster phusical disk memory
access would do for you. If many people are waiting longer
that they like, maybe they would chip in to fund an upgrade,
to feed that 12(24)-core "beast" :-)

I'd bet it is waiting a lot, if not more than computing :)
--
Regards,
Bengt Richter




  parent reply	other threads:[~2022-10-31 19:03 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       ` Has guix system ever run a hardware survey? Joshua Branson
2022-10-31 19:02       ` Bengt Richter [this message]
2022-11-01 12:49         ` How long does it take to run the full rustc bootstrap chain? 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

  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=20221031185630.GA3567@LionPure \
    --to=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 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).