News for hackers. Stuff that matters.
Re:Go as an alternative to Node.js for very fast servers by thrownaway2424 on Wednesday August 14, 2013 @01:53PM (#6213099)
No, not even close. Each thread on a Haswell CPU, just as an example, has 8 execution ports. Each Haswell core has ten execution units. The CPU can retire way more than one instruction per cycle.
Re:Go as an alternative to Node.js for very fast servers by chad_oliver on Wednesday August 14, 2013 @04:50PM (#6214152)
You are absolutely correct, but you could also afford to be a bit more polite. Sentences like "In other words, you have no idea what the difference is" might be true but they're also a bit rude.
Re:Go as an alternative to Node.js for very fast servers by corresation on Thursday August 15, 2013 @08:06AM (#6217282)
They aren't absolutely correct at all, and aaron was actually close to the money. Thrownaway is fundamentally misrepresenting (or misunderstanding) how threads -- in an operating system sense, and what we are talking to here -- relate to microcode and execution units in a core.
Re:Go as an alternative to Node.js for very fast servers by AsymetricCom on Wednesday August 14, 2013 @02:09PM (#6213189)
In theory
Re:Go as an alternative to Node.js for very fast servers by oofabz on Wednesday August 14, 2013 @02:51PM (#6213456)
It's not just theory, you typically get about 3 instructions per cycle in practice.