intrinsic Open-Source Projects
Performance-portable, length-agnostic SIMD with runtime dispatchProject mention: ARM vs. RISC-V Vector Extensions | news.ycombinator.com | 2021-05-06
> If your goal is to understand how hardware SIMD works, you're probably better off sticking to C code with intrinsics
Agreed, and we're also using intrinsics in time-critical places. I am confident we will be able to hide both SVE and RVV behind the same C++ interface (https://github.com/google/highway) - works for RVV, just started SVE.
Microbenchmark to achieve peak performance on x86_64 CPUs and NVIDIA GPUsProject mention: lscpu + neofetch = cpufetch | news.ycombinator.com | 2021-04-07
Dr-Noob here. Created an account just to comment on this post. I appreciate all of your comments.
For the ones who think that cpufetch uses lscpu (especially the one who wrote the title of this post), please see https://www.reddit.com/r/linux/comments/milnza/cpufetch_simp...
About the peak performance, nezirus, the purpose is to have a quick look of how powerful a CPU is supposed to be. Peak performance does not measure the real performance of a CPU but it is a rough estimate of it. The peak performance is one of the distinguishing marks of cpufetch and is one of my favorite fields of cpufetch. Concerning the fight between Gold 6238 and EPYC 7702P, is not the other way around. If you are able to use the full power of the CPU, Gold is much more powerful. However, in a real program, this is not always true. For more information about the peak performance, see https://github.com/Dr-Noob/peakperf. There you will understand how peak performance is calculated and how it works.
Thank you very much for your "text screenshots", I really like to see my program on all this variety of hardware!
Scout APM - Leading-edge performance monitoring starting at $39/month. Scout APM uses tracing logic that ties bottlenecks to source code so you know the exact line of code causing performance issues and can get back to building a great product faster.