Does the "Relative performance" in the plot refer to computational performance/speed alone?
If so this analysis kinda sidestep the issue of power consumption. It was not the processor's computational speed that was in question. It was that Intel CPU had more or less the same performance at HALF the current drain/power.
Scaling of the benchmark LEVELS is key here in my opinion.
What are the quantitative measures used to give qualitative performance "scores?"
For gaming people, only super fast will do at any power cost.
For most other people, battery life dominates in the high end phone market in my opinion, as long calls are common, hectic days on road, but a dead phone is very very costly, so multi-day battery life in heavy use scenario is very important.
Other "performance" metrics are unclear to non-techies so perhaps someone can make them clearer in terms like "time to open email" or texting delays, whatever.
The RAM scores seem highly unusual. Is there some kind of "cheating" going on with Antutu? I agree with Jim -- using one benchmark to brag about a chip capabilities is certainly wrong. But not only is the Antutu score "out of the norm", but the subtest scores seem very strange. Doesn't even look like the results of a real benchmark compared to the scaling of other benchmarks!
I couldn't agree more about the performance/watt metric. Noe one would be shocked if you said a top of the line Xeon (or POWER8) beat an ARM chip in performance. The race is completely about performance/watt.
As the editor has remarked performance benchmarks are thwart with issues. Many of them are constructed to take advantage of the architecture of a specific core for the sole purpose of making that vendor's silicon look really fast, when in reality it's just really good marketing spin.
Also, what OS was running on each platform to carry out these tests, since a highly optimised OS can make these benchmark tests show amazing performance on a slow processor vs. poor results on a badly ported OS running on a considerably faster processor.
This is further compounded if the OS isn't utilising the multi-core architecture very effectively. Many OS utilise two CPU cores really well, two not so much and the others are hardly used at all, making you wonder why some OS vendors were ported in the first place to many of the multi-core processors.
In terms of Power consumption, that is nearly always governed by the quality of the silicon process. As you go down in silicon geometry the leakage current from the gates increases significantly, which needs to be properly controlled in the manufacturing process.
Intel uses a low leakage 32nm process for the Atom and the Samsung is made on a standard 28nm process. Therefore, the Power consumption remark is somewhat flawed, since its not related to an ARM vs Intel CPU issue, but the choice of manufacturing process.
Well, long calls affecting battery life is much more a function of the RF chipset efficiency and software control of transmit levels, etc. I don't see how it would fit into a comparison of digital SoCs.
Note how often the word "current" is used. The ABI article is clearly more about the current draw than about raw performance. So, while I agree that they could have done a better job by averaging multiple benchmarks, I think the point of the article is that Intel seems to have finally conquored what analysts have considered its "Achilles' heel": power consumption. The intel part performs competatively compared to other SOCs on the market and it does so with impressive power numbers.
As to another commenters point about power being tightly correlated with process and that Intel has an advantageous process -- I agree. But in the end its the current products on the market "at the present time" that matter -- not how the company achieved its success. If the purpose is a strict architecture comparison, then yeah, take the process out of the mix. However, the "ARM vs Intel" babble out there isn't really geeky comparisons to architecture specfically. Its just terminology used to compare "Intel based" SOCs and "ARM based" SOCs that are currently available.
The AnTuTu blog posted a complaint about Chinese manufacturers who diddled the benchmarks to make RAM performance appear to be double what it actually was. (See http://www.antutulabs.com/node/100) The fact that the manufacturers could diddle the benchmarks like that makes the value of the benchmarks questionable.)
I didn't quite laugh when I read the article, but it was tempting, I've been watching the electronics market place for decades, and benchmarks are simply a tool in the marketing battle. Vendors will post the benchmark scores that favor thier products, and ignore or attempt to denigrate the rest. They will further emphasize the individual parts of a benchmark suite where they excel, and ignore the less favorable ones. (And it's not like flat-out cheating is unheard of.) Most folks take benchmarks with sacks of salt, and the ones that get attention at all are run by independent third-party testing groups who aren't tied to any of the vendors.
The two applicable questions are "Has Intel become competitive with ARM in power draw at the same performance level?", and "Will any vendors give Intel design wins in upcoming products based on these benchmarks?"
My personal suspicion is that the answers are No and No.
Everything I've seen about the mobile device market indicates battery life is the biggest factor users will be concerned about, and Intel is still playing catchup with ARM in that area. Since device manufacturers pretty much have to provide battery life estimates under normal usage conditions as part of their marketing, they'll look long and hard at the battery life using an ARM processor vs an Atom processor, and if the ARM processor uses significantly less power, it's likely to get the nod even if the Atom processor has somewhat better performance.
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.