From: Jacob Hrbek <kreyren@rixotstudio.cz>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Proposal: Build timers
Date: Tue, 23 Nov 2021 21:35:24 +0000 [thread overview]
Message-ID: <iXwDISuadhYpp4IHgBQOfDA-KvCYuy6JjO_RiZLFYcr_TCpbG_xyIG_kqoDUonhREuWylYUFjodAR5y642RK39m2gcG9F4EPpKOPO3uam08=@rixotstudio.cz> (raw)
In-Reply-To: <a5bba60c43c1ad95930c04ea3d3fb823ba1bc21e.camel@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1615 bytes --]
Skimming through the research that lily provided our builds are reproducible so the changes in cpu cycles requirements should be same with any post-build implementation disabled, but i recognize that different CPUs might use different configuration that influences the calculation and it will be a complicated task to account for all variables that influence the build across systems so instead of accurate measurements we should work with a sane tolerance for accuracy.
-- Jacob "Kreyren" Hrbek
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, November 23rd, 2021 at 8:09 PM, Liliana Marie Prikler <liliana.prikler@gmail.com> wrote:
> Am Montag, den 22.11.2021, 22:02 +0000 schrieb Jacob Hrbek:
>
> > See the proposal in https://git.dotya.ml/guix.next/GUIX.next/issues/5
> >
> > -- Jacob "Kreyren" Hrbek
> >
> > Sent with ProtonMail Secure Email.
>
> Your Pokémon analogy is extremely flawed. The same CPU at a different
>
> clockrate does not perform the same task in the same amount of cycles
>
> [1, 2].
>
> [1] Kotla, Ramakrishna & Devgan, Anirudh & Ghiasi, Soraya & Keller, Tom
>
> & Rawson, Freeman. (2004). Characterizing the impact of different
>
> memory-intensity levels. 3 - 10. 10.1109/WWC.2004.1437388.
>
> [2] Snowdon, David & Sueur, Etienne & Petters, Stefan & Heiser, Gernot.
>
> (2009). Koala a platform for OS-level power management. Proceedings of
>
> the 4th ACM European Conference on Computer Systems, EuroSys'09. 289-
>
> 302. 10.1145/1519065.1519097.
[-- Attachment #1.2: publickey - kreyren@rixotstudio.cz - 0x1677DB82.asc --]
[-- Type: application/pgp-keys, Size: 737 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
next prev parent reply other threads:[~2021-11-23 21:35 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
2021-11-23 20:09 ` Liliana Marie Prikler
2021-11-23 21:31 ` Jacob Hrbek
2021-11-23 21:35 ` Jacob Hrbek [this message]
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='iXwDISuadhYpp4IHgBQOfDA-KvCYuy6JjO_RiZLFYcr_TCpbG_xyIG_kqoDUonhREuWylYUFjodAR5y642RK39m2gcG9F4EPpKOPO3uam08=@rixotstudio.cz' \
--to=kreyren@rixotstudio.cz \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@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).