Up to 4GB RAM may be a limitation to support multiple VMs with sophisticated service. The power saving may come down to how many VMs that can be supported on a ARM based server vs that can be supported by a x86 based server.
here are a few more publicly announced Cortex-A licenses: Broadcom , NEC Electronics, NVIDIA, STM, Toshiba, Mindspeed Technologies, Freescale, Matsushita, Samsung, PMC-Sierra, Ziilabs.
Why are there no solutions like Tilera's 36 or 64 core products. Are ARM's per core licensing costs too high ? 32 bit address limitations ? There are a lot of multi-core non ARM product our there, Cavium Networks (MIPS), Netlogic (MIPS), Freescale (PPC), Azul (Java VM), Plurality ...
2 or even 4GB of RAM is sufficiant for many, many server tasks. I think a system based on that SoC is on par with the Pentium III Tualatin quad-processor systems build in 2001-2002. These system also had just 2 or 4 GB of RAM. But nevertheless served well.
Definitely interesting, but it seems problematic that you have four cores that can address only a total of 4GB of memory, e.g. 1GB per core. Might be limiting for a lot of server apps. In practice it might be worse, with the system only able to handle 2-3GB (that's been my experience with 32-bit, non-PAE Linux).
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.