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 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.