Maybe the time has come for applications specific CPU variations?
One optimized for node.js tasks, one for databases, ...
One optimized for node.js tasks, one for databases, ...
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.
At least two different tasks, audio and graphics, have special application specific processors. Networking and crypto are also often offloaded.
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.