wow... seems like the ARM guys are up in ARMS about this benchmark... the tenor of their alarm disguised as s(k)epeticism (yes we spell it with a K here) is hinting at their allegiance in this fight.
I really don't care, except made in the USA is always good for me.
The benchmark used and methodology does really matter a lot. If you load your car with heavy stuff, do you expect to achieve the same top speed or petrol consumption?
Note that current drain is not relevant, what you really want to measure is task energy (which requires voltage and time to complete a task).
Also it's not news that Intel can make a phone CPU with reasonable battery life, eg. Lava XOLO and Razr I early 2012. The Z2580 in K900 is simply the dual core variant.
Regardless of questions about whether these were the best benchmarks for mobile, or whether the source was Java or whatever, the point remains that it looks like Intel has made some real progress on reducing current drain while providing a level of performance suitable for a smartphone. Better, equal or just slightly worse than competing architectures is less critical right now (unless you're the Intel sales guy) than the fact that they appear to finally have a processor worthy of running on a smartphone's modest battery capacity. We will all get a much clearer picture once they are designed into a few more phones with wider deployment.
Agree. The benchmark setup and detailed results should be published. It is very easy to chose data that makes once processor look better than the other.
The other question is which intel parts are they using? Are these a select few parts screened from hundreds for their favorable power characteristics? There is usually silicon variation and it is possible to find a few parts that work well but these numbers will be difficult to reproduce in volume production.
Looks to me like this is Intel marketing at work.
...and these numbers matter why? The reason Apple and Samsung don't publish benchmarks like this is because they don't matter. Unless you plan to run SETI@home on your mobile, these numbers mean next to nothing.
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.