Sometimes I wish we could get to a timeline where the FPU format standards have something like Crockford’s DEC64 end up winning or evolving into the prevailing standard. Simpler & consistent math ought not to be this hard.
Not just single core perf though. Very efficient idle TDP, efficient all core boost, efficient all core TDP, and efficient mid-high performance tier accelerator (GPU, NPU) TDP.
And the benchmarks seem to understate this. That i9-9001THIKK doesn't matter when it thermal throttles a few seconds into a task. Are they testing these laptops inside freezers or something?
The person in the forum thread claimed to be repairing CM5s and CM4s. Unusual but it seems like an otherwise hyper reactive response by the RPi Foundation. Something you wouldn’t batt an eye at if it were Apple instead.
Sadly, I think things like distcc or ccache have mostly gone out of mode. Vertically scaling (multi core, multi thread, multi TB RAM build machines) and simple artifact caching have won for now. Artifact caching with dependency tracking in the midst of job scheduling was solved “good enough” by OS based mechanisms. Having used and managed the basics of a build farm, removing the need for networking, build farm management and build job coordination is a huge burden relief when your source tree doesn’t require it.
Part of the motivation to use processes is because their structure helps to keep the job generic, uni
I was not impressed by author’s surprise that original emulation ran at 1/10th speed. For the past 50 years, that’s usually the target for calling (“unaccelerated”) emulation good enough. Especially for architectures that are current or in development or otherwise require some sort of instruction translation.
The last 30 years we’ve seen innovations like dynamic recompilation, fat binaries, JIT VMs, and profile guided optimization. So that has created an expectation of sub-order of magnitude run time performance. It’s a fanciful time we live in.
Hey, author here. That's fair, I didn't have the background. I knew interpreters would be slow, I just didn't expect it to still be ~10x after all the optimizations. After reading about it more though, that does seem to be the norm
https://www.crockford.com/dec64.html