The benchmark shows what it was trying to show, the contributuon of the processor on power draw. An attempt to isolate the processor makes complete sense. Battery life of the various phones would be meaningless as there are so many other parts of the phone that play into this.
This is not a phone benchmark per se but a processor benchmark (plus likely power conversion and memory subsystem).
Ah, now you say, 'if time is equal'. That is the one, solitary case, where the statement is true.
But why would time be equal? Especially on different architectures, with different instruction sets and different processes. Also compilers and a whole lot other issues.
Under many circumstances the chip that dissipates the most power during the task could have the lesser energy consumption completing a task.
It ain't for no reason that batteries are specified in energy capacity, not power.
Performance aside, I am disappointed in the lack of professionalism in some of the comments. This is a professional site, please treat as such.
On the comments wrt power and energy, if you have the same performance at half the power then the total task energy will be half as well.
Intel and Microsoft are teaming up on the energy issue, at least starting with Haswell. I presume Atom will follow the same recipe going forward, if not already.
The real question is whether Windows 8 is compelling enough to take significant market share in tablet and phone.
One can argue about benchmarks all day long, but with new Haswell in Macbook Air the battery life goes from 7 to 12 hrs. Thus it is reasonable to assume that with the new Bay Trail on 22nm tri-gate Intel will have a competitive advantage over ARM.
Blog Doing Math in FPGAs Tom Burke 8 comments For a recent project, I explored doing "real" (that is, non-integer) math on a Spartan 3 FPGA. FPGAs, by their nature, do integer math. That is, there's no floating-point ...