3 ms·
The node size numbers have been made up for decades. Even if process shrinks bottom out two or three node shrinks from now there will still be improvements in p
by dodobirdlord 6y ago
The node size numbers have been made up for decades. Even if process shrinks bottom out two or three node shrinks from now there will still be improvements in process, materials, thermals, and packaging to allow things like greater z-axis stacking. And there's a ton of room for targeted improvement in things like vector instructions.
That's not to say that there isn't an enormous amount of improvement available in software. Projects like simdjson prove that there's a 2x or more improvement available for many high-performance use cases by migrating to vector instructions.
https://github.com/simdjson/simdjson https://github.com/simdjson/simdjson
- csharptwdec19 6y agoYou don't even have to reach for SIMD to get better performance. Just stop letting crappy software get written. I'm currently agonizing over an application that has an 80-120ms response time for 5 hops (including db writes). Yet I know many people who code in my language would find that number amazing for the work being done in those hops. No SIMD. Nothing too crazy. Just well thought out processing flow and proper separation of the stupid.