This numa optimization (at the CHIPLET level) reminds me of coders going above and beyond trying to do the compiler's job. Which is very cool for live streams and tech blogs and tech videos on youtube but it's a pain for actual programmers. So, just like the compiler is supposed to handle the lower level optimizations, so should the software handle the modern architectures properly and spare the sysadmin / storage admin from doing this manual bolt tighening. He's the driver, not the mechanic. I mean it's super cool, don't get me wrong, but it's the coding team's concern (whoever that is)
Complex Performance Tuning can scare a systems admin into opting for a closed source solution but even those end up having crazy bugs that are only known by insiders
@@amosgiture not really scared scared, but more like weighing the pros/cons and how much he's being paid cause that sort of decision comes down to tco and negotiated discounts / support packages at the management level. If the company relies 100% on it's own it department and does not buy support and it also has very competent sysadmins, the only reason those closed source solutions are interesting most of the time is just because they say so in a very fancy way and catch the executive's (non technical) eye and there's no code to prove the contrary. So unless we're talking dedicated solutions that include hardware and sla-s, open source is just as if not even more solid than commercial. Back on point, this low level tuning is a pain until you get it and afterwards you just automate away. But still, it is at the fundamental level *not* the sysadmin's job. Just like optimizing branch prediction is not a ts frontend dev's job, tuning for inter-chiplet numa is not the sysadmin's.
![Lp. Сердце Вселенной #60 РОЖДЕНИЕ ЛОЛОЛОШКИ [Финал] • Майнкрафт](http://i.ytimg.com/vi/YoR0pAV9FVQ/mqdefault.jpg)
This numa optimization (at the CHIPLET level) reminds me of coders going above and beyond trying to do the compiler's job. Which is very cool for live streams and tech blogs and tech videos on youtube but it's a pain for actual programmers.
So, just like the compiler is supposed to handle the lower level optimizations, so should the software handle the modern architectures properly and spare the sysadmin / storage admin from doing this manual bolt tighening. He's the driver, not the mechanic.
I mean it's super cool, don't get me wrong, but it's the coding team's concern (whoever that is)
Complex Performance Tuning can scare a systems admin into opting for a closed source solution but even those end up having crazy bugs that are only known by insiders
@@amosgiture not really scared scared, but more like weighing the pros/cons and how much he's being paid cause that sort of decision comes down to tco and negotiated discounts / support packages at the management level. If the company relies 100% on it's own it department and does not buy support and it also has very competent sysadmins, the only reason those closed source solutions are interesting most of the time is just because they say so in a very fancy way and catch the executive's (non technical) eye and there's no code to prove the contrary. So unless we're talking dedicated solutions that include hardware and sla-s, open source is just as if not even more solid than commercial.
Back on point, this low level tuning is a pain until you get it and afterwards you just automate away. But still, it is at the fundamental level *not* the sysadmin's job. Just like optimizing branch prediction is not a ts frontend dev's job, tuning for inter-chiplet numa is not the sysadmin's.