From: zimoun <zimon.toutoune@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>,
Jacob Hrbek <kreyren@rixotstudio.cz>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Proposal: Build timers
Date: Tue, 23 Nov 2021 17:23:27 +0100 [thread overview]
Message-ID: <86o86avo1s.fsf@gmail.com> (raw)
In-Reply-To: <41445168-F908-4316-8AC4-55AFB3F43FB0@lepiller.eu>
Hi,
On Tue, 23 Nov 2021 at 07:05, Julien Lepiller <julien@lepiller.eu> wrote:
> LFS has a notion of a Standard Build Unit (SBU), that is the build
> time of a particular package on your machine. Each package build time
> is estimated in SBU. However, they do not take threads into account,
> because the relation is not exactly proportional (some parts are
> linear, there is some overhead, …). SBUs change quite often with
> versions, so I don't think averaging on different versions/derivations
> would make a lot of sense… But I suppose this info could help
> determine how long it should take to build the same derivation or a
> similar one.
Thanks for the SBU pointer. This webpage [1] provides some details.
But I do not find the mentioned table. I would see more numbers about
averages and standard derivation.
Moreover, I am confused, here [2] GCC@11.2.00 requires 26+56 SBU. And
there [3] it says 164 SBU. Why is it so different?
I am not convinced such SBUs makes sense for x86_64 because for instance
my laptop (4 cores+SSD) is different from my desktop (4 cores+HDD) and
really different from my workstation (64 cores+mix). From my
understanding, this SBU makes sense in the LFS context because machines
are, from my opinion, not so much heterogeneous.
However, other architectures are generally more homogeneous machines.
And because substitutes are less available, maybe such unit could be
worth as a rough indicator.
1: <https://www.linuxfromscratch.org/~bdubbs/about.html>
2: <https://www.linuxfromscratch.org/blfs/view/svn/general/gcc.html>
3: <https://www.linuxfromscratch.org/lfs/view/stable/chapter08/gcc.html>
Cheers,
simon
next prev parent reply other threads:[~2021-11-23 16:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 22:02 Proposal: Build timers Jacob Hrbek
2021-11-23 1:06 ` zimoun
2021-11-23 6:21 ` Jacob Hrbek
2021-11-23 11:56 ` zimoun
2021-11-23 14:39 ` Jacob Hrbek
2021-11-24 11:35 ` zimoun
2021-11-25 4:00 ` Jacob Hrbek
2021-11-23 12:05 ` Julien Lepiller
2021-11-23 16:23 ` zimoun [this message]
2021-11-23 20:09 ` Liliana Marie Prikler
2021-11-23 21:31 ` Jacob Hrbek
2021-11-23 21:35 ` Jacob Hrbek
2021-11-23 23:50 ` Julien Lepiller
2021-11-24 11:31 ` zimoun
2021-11-24 20:23 ` Vagrant Cascadian
2021-11-24 21:50 ` zimoun
2021-11-25 4:03 ` Jacob Hrbek
2021-11-25 5:21 ` Liliana Marie Prikler
2021-11-25 10:23 ` zimoun
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=86o86avo1s.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
--cc=kreyren@rixotstudio.cz \
/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).