26 ms·
So these are "cloud-native processors": many cores (80-128, etc?) that are single threaded, which allows for simultaneous connections in a cloud environment res
by emmanueloga_ 3y ago
So these are "cloud-native processors": many cores (80-128, etc?) that are single threaded, which allows for simultaneous connections in a cloud environment resulting in scalability. The processors are also smaller with more efficient power usage and can run both enterprise and cloud-native applications, making them more cost effective than other alternatives.
.- https://en.wikipedia.org/wiki/Cloud-native_processor https://en.wikipedia.org/wiki/Cloud-native_processor
- pclmulqdq 3y agoYeah, it turns out that a core the size of a large Intel atom is a lot more efficient at web workloads than a bigger CPU. Intel and AMD know this, and are responding accordingly, but Ampere seems to have beat them to the punch.
- tedunangst 3y agoSparc Niagara was only twenty years too soon.
- rbanffy 3y agoIndeed, but there is a catch - the Niagara cores had high thread counts, which creates issues with VM isolation. Single-thread designs are better for virtualization in that 1 core is one vCPU. I tested Niagara boxes a long time ago and their price/performance for web hosting wasn't competitive with Dell or IBM x86.
- gymbeaux 3y agoReminds me of how Xeon Phi Coprocessors used Atom cores
- rbanffy 3y agoThe Xeon Phi is one of Intel's missed opportunities - it could have been positioned as a virtualization workhorse, but only the last iteration got VT-x and VT-d extensions.
- gymbeaux 3y agoBut the RAM on ‘em was very low and as far as I know the cores only run C++ code, which I realize is what a lot of software is written in, including probably QEMU… can that last iteration actually run a hypervisor? I would have loved to be able to run a bare-metal OS on it and have those cores available for multithreaded Python/C#/etc.