4 ms·
Tools like that are a core part of the design process. You write that software along with the choice of parametrization of the design. It's not an off the she
by ajross 7y ago
Tools like that are a core part of the design process. You write that software along with the choice of parametrization of the design. It's not an off the shelf thing. But yes, that's how it works.
It's also important to note that decisions like this are hugely workload-specific. There's no single best processor for all applications. In extreme examples: almost every transistor on a vector SIMD unit is wasted when trying to optimize for a client Javascript benchmark; streaming symmetric encryption gets no benefit from L3 cache (which is like half the chip these days!); etc...
- mmrezaie 7y agoDo people like Jim Keller are the experts in finding the right balance? Is that why he and his team are so important?
- zazagura 7y agoMaybe the time has come for applications specific CPU variations? One optimized for node.js tasks, one for databases, ...
- tempguy9999 7y ago> one for databases as a DB guy, there's no 'one task' for DBs . The only thing I can think that is nearly characteristic of DBs I've worked on is that they're IO bound. That's possibly true of most things except Floating point and graphics.
- snaky 7y agoWhile that's true, you can achieve impressive results offloading particular parts of particular DBMS code to the specialized CPUs, https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/perf/src/tpc/db2z_ibmziip.html https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0...
- pjc50 7y agoARM got a Javascript oriented instruction: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0801g/hko1477562192868.html http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.... At least two different tasks, audio and graphics, have special application specific processors. Networking and crypto are also often offloaded.
- snaky 7y agoMainframes used to explore this long ago, leveraging different microcode for different workloads keeping the hardware of processing unit the same, https://en.wikipedia.org/wiki/ZIIP https://en.wikipedia.org/wiki/ZIIP On the other side of the computing spectrum, there were a couple of papers in 2010s about offloading most common mobile tasks (like CSS layouting) to the specialized mobile CPU subsystems. Maybe this should have been implemented if Google made their own mobile CPU.