From: Tobias Geerinckx-Rice <me@tobias.gr>
To: guix-devel@gnu.org, swedebugia <swedebugia@riseup.net>
Subject: Re: Cuirass Ghzminutes enhancement idea
Date: Fri, 21 Jun 2019 20:26:31 +0200 [thread overview]
Message-ID: <87d0j6u754.fsf@nckx> (raw)
In-Reply-To: <f5bc3206-9145-ccda-f2c5-1240a0ab395d@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]
Swedebugia, Guix,
I was about to answer on IRC when I saw this thread :-)
swedebugia wrote:
> <swedebugia> Maybe we could have an additional time measurement:
> Ghzminutes. E.g. if the build took 60 minutes on a 3 Ghz machine
> it
> took 20 Ghzminutes.
> <swedebugia> The build node would have to communicate the total
> Ghz
> used for the build. E.g. if 2-core 3 Ghz= 2*3 Ghz= 6 Ghz.
https://www.tobias.gr/marx.png
Instead (and I'm probably not the first to suggest this), store
the time taken to build each store item in the database and spit
out some misleading number based on that. Prefer local build
data; fall back to build farm (new nar field?) data if a similar
package has never been built locally.
In both cases, make innumerable ridiculous assumptions: that
system load isn't constantly fluctuating; that store items with
identical names aren't completely different configurations of the
same package; that -c and -M are remotely similar; that it's not
this week in Belgium where CPUs are being heat-throttled by the
weather alone; that the build isn't bound by a test suite that
takes a day to run on spinning rust (hi ceph); …
It might even give a rough idea of build time.
Kind regards,
T G-R
PS: reminds me of
http://linuxfromscratch.org/lfs/view/stable/chapter04/aboutsbus.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-06-21 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 15:43 Cuirass Ghzminutes enhancement idea swedebugia
2019-06-21 16:01 ` Andreas Enge
2019-06-21 16:17 ` swedebugia
2019-06-21 17:46 ` ng0
2019-06-21 18:26 ` Tobias Geerinckx-Rice [this message]
2019-06-21 18:30 ` Tobias Geerinckx-Rice
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=87d0j6u754.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=swedebugia@riseup.net \
/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).