Analyzing Intel Core M Performance: How 5Y10 can beat 5Y71 & the OEMs' Dilemma
by Brett Howse & Ian Cutress on April 8, 2015 8:00 AM EST3DMark Ice Storm Unlimited Results
Ice Storm Unlimited is quite a bit different than the last two benchmarks. The test is built for smartphones and tablets, so is far less demanding than the other GPU benchmarks. There are two GPU tests, and a physics test, and as you will see in the graphs, when those workloads are occurring is very obvious. The overall benchmark is quite short though, which allows the devices that have more thermal issues, but higher overall turbo frequencies, to keep the frequencies up much more. It is basically the equivalent of a CPU burst workload, except mostly run on the GPU.
The Core i5 does not even flinch at this workload, even leveraging its turbo when needed. The Venue 11 Pro is the most interesting graph because it so clearly defines when the actual work is happening. Because the duration is so short, it is able to turbo quite high, and the GPU frequencies are not throttled too much. The ASUS does have to throttle the CPU to keep the GPU frequency up on this test. The Yoga 3 Pro shows quite a strong result in this very short test.
Looking at the average CPU speeds, the Yoga 3 Pro jumps way out in front. The Venue 11 Pro is quite far behind, but as you can see in the graphs, when the work was required, it did have thermal headroom available to turbo.
On the GPU front, the Yoga 3 Pro is almost at the same average as the Core i5 in this test, as both have the same base and turbo frequencies. The Venue 11 is only a bit behind, and the ASUS falls to third due to the 100 MHz frequency deficit that the 5Y10 has on the GPU compared to the 5Y71 processor.
On the SoC temperature side, none of the devices struggle with temperature on such a short test.
On such a short test, the Core M devices all do very well, and the fastest Core M model in the Yoga 3 Pro tops this GPU test. It is quite a bit in front of the rest of the devices, showing that with active cooling, it can still get a lot of work done in a short amount of time. Remember that the Core i5 Dell Latitude is the only device with single-channel memory, which hurts it most in the GPU tests and explains why it is below the Core M devices despite much higher average frequencies for both the CPU and GPU.
Facebook
Twitter
RSS
110 Comments
View All Comments
seapeople - Thursday, April 9, 2015 - link
Won't an over-aggressive turbo actually decrease performance? Processors are generally less power efficient at higher clock speeds, i.e., running at 3GHz is twice as fast as 1.5GHz but generally uses more than 2x the power, and thus more than 2x the heat.In this case, therefore, a processor that races to 3GHz will quickly (and less efficiently) use up its thermal headroom and have to throttle back moreso than a processor that stayed at 2GHz.
It's like a footrace - if the race is 100m long, you're going to finish fastest if you go all out. However, if the race is a mile long, then the guy who starts off sprinting is going to be sputtering along a quarter of the way into the race as the joggers pass him up.
MrSpadge - Friday, April 10, 2015 - link
You are right that with agressive Turbo the chip is running in a less power efficient state initially and will have to throttle a bit earlier than a slower, steadily running chip. but if we're talking about low performance under sustained loads, this doesn't matter: it affects the first few seconds, or 10's of seconds at most, whereas in the following minutes both systems are running at the same power efficient throttled speed, which is basically determined by the system cooling. It's not like the sprinter who's completely exhausted and can't recover.retrospooty - Wednesday, April 8, 2015 - link
I dont think its really all that complicated... If you are looking for raw performance, Core M isnt for you. It is really for low power devices that do basic stuff like browsing, email etc. For that purpose, its one hell of a CPU. That performance level at 4.5 watts is a hefty accomplishment IMOYuLeven - Wednesday, April 8, 2015 - link
I do development on a Core M machine. Instead of carrying 4 pounds of computing power on my back, I let a cloud based development box do the heavy lifting. The plume light Core M notebook is used basically to write the code and give orders to the Dev box. IMHO opinion a far better setup than having scoliosis for the sake of running code locally.mkozakewich - Wednesday, April 8, 2015 - link
It's not for web browsing. That's what Atom is for. A Core-M device is good for all regular core tasks except sustained graphics tasks. I wouldn't get one to game, but it'll be great for anything else.retrospooty - Thursday, April 9, 2015 - link
That is pretty much exactly what am saying. Basic use, core M is fine. Not for high performance requirements.nathanddrews - Wednesday, April 8, 2015 - link
They have taken the exact opposite approach to their SSD design, where they try very hard to offer constant and consistent performance.xthetenth - Wednesday, April 8, 2015 - link
Both make sense from the perspective of increasing perceived speed. With storage, it hanging and being slow is the biggest way it can impact the feel of the device, while processors that trade finishing short tasks much faster for a tiny decrease in how fast they complete long tasks do a lot to achieve a responsive feel.xthetenth - Wednesday, April 8, 2015 - link
Device buyers don't buy devices to get a higher average frequency, they buy things to do what they want without the device holding them up. Look at the benchmarks where the ASUS holds higher average frequencies but the Yoga's higher maximum frequency means it completes tasks faster, and it performs better in the benchmark. That sort of responsiveness is what turbo is for. The time to complete long tasks isn't going to be materially changed but the time to complete short tasks is going to be reduced significantly if the processor can use a quick burst like turbo allows.I'm also pretty sure that most users consider not getting burned by their device a good thing that should continue, incidentally.
StormyParis - Wednesday, April 8, 2015 - link
That's not a real use case though. Real use case is load a page (low CPU), render page (high CPU) read page (low CPU). I don't care how fast my CPU is idling while I'm reading the page, I do care how fast the page renders. It'd be different if I were running simulations.. that's what desktop CPUs are for.