From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tobias Geerinckx-Rice Subject: Re: Cuirass Ghzminutes enhancement idea Date: Fri, 21 Jun 2019 20:26:31 +0200 Message-ID: <87d0j6u754.fsf@nckx> References: Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:40279) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1heOFG-0004nu-8y for guix-devel@gnu.org; Fri, 21 Jun 2019 14:26:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1heOFF-0002A0-38 for guix-devel@gnu.org; Fri, 21 Jun 2019 14:26:42 -0400 Received: from tobias.gr ([2001:470:7405::1]:39586) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1heOFE-000280-GZ for guix-devel@gnu.org; Fri, 21 Jun 2019 14:26:41 -0400 In-reply-to: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org, swedebugia --=-=-= Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Swedebugia, Guix, I was about to answer on IRC when I saw this thread :-) swedebugia wrote: > Maybe we could have an additional time measurement: > Ghzminutes. E.g. if the build took 60 minutes on a 3 Ghz machine=20 > it > took 20 Ghzminutes. > The build node would have to communicate the total=20 > Ghz > used for the build. E.g. if 2-core 3 Ghz=3D 2*3 Ghz=3D 6 Ghz. https://www.tobias.gr/marx.png Instead (and I'm probably not the first to suggest this), store=20 the time taken to build each store item in the database and spit=20 out some misleading number based on that. Prefer local build=20 data; fall back to build farm (new nar field?) data if a similar=20 package has never been built locally. In both cases, make innumerable ridiculous assumptions: that=20 system load isn't constantly fluctuating; that store items with=20 identical names aren't completely different configurations of the=20 same package; that -c and -M are remotely similar; that it's not=20 this week in Belgium where CPUs are being heat-throttled by the=20 weather alone; that the build isn't bound by a test suite that=20 takes a day to run on spinning rust (hi ceph); =E2=80=A6 It might even give a rough idea of build time. Kind regards, T G-R PS: reminds me of=20 http://linuxfromscratch.org/lfs/view/stable/chapter04/aboutsbus.html --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQT12iAyS4c9C3o4dnINsP+IT1VteQUCXQ0hVwAKCRANsP+IT1Vt eXkQAP906np39HJesTGueN0zNhGW/a4rSfaF13C8K6IGXcoZ7gEApXHwiwj4VzOg dHgJmlAh0IRqDpZa80gaFUw2qtvcAAE= =+ypi -----END PGP SIGNATURE----- --=-=-=--