If you've been following our SoC and smartphone related coverage over the past couple of years, you'll probably remember how Qualcomm let us take home an MDP8660 from MWC 2011 and thoroughly benchmark it. Qualcomm has done essentially the same thing this year, this time sending their latest and greatest MSM8960 SoC inside the aptly named MSM8960 Mobile Development Platform (MDP) just before MWC 2012. The timing is impeccable as we're fully expecting to start seeing MSM8960 based phones next week at MWC, and we've been telling you to hold off on any smartphone purchases until the 8960's arrival. Today we're finally able to give you an indication of just how fast Qualcomm's next-generation Snapdragon S4 will be.

We've already been teased MSM8960 and Krait a few times, and have talked about the architecture and what to expect from the SoC itself. The super short recap is this: Krait is the name of Qualcomm's new out of order ARMv7-A compatible CPU architecture (previous generations of Snapdragon used Scorpion) which is designed for TSMC's 28nm process. Inside MSM8960 are two Krait cores running at up to 1.5 GHz, Adreno 225 graphics, improved ISP and Qualcomm's new baseband with support for nearly every air interface out there.

The MDP we were sampled is clearly a descendant of the MDP MSM8660 we were given last year, sharing the same black utilitarian look and purpose-built design, though it's notable that the new device is markedly thinner. MDP MSM8960 is running Android 4.0.3 at 1.5 GHz, and includes 1 GB of LPDDR2, and a 4" 1024x600 display. It's an interesting note to make that both Intel and Qualcomm have somehow settled on 1024x600 for their reference designs.

We also asked Qualcomm for a copy of the old MDP8660 for comparison purposes, just to see how far we've come since the first dual core Snapdragon SoC.

Qualcomm Mobile Development Platform (MDPs)
MDP MSM8660 MDP MSM8960
SoC 1.5 GHz 45nm MSM8660 1.5 GHz 28nm MSM8960
CPU Dual Core Scorpion Dual Core Krait
GPU Adreno 220 Adreno 225
RAM 1 GB LPDDR2 1 GB LPDDR2
NAND 8 GB integrated, microSD slot 16 GB integrated, microSD slot
Cameras 13 MP Rear Facing with Autofocus and LED Flash, Front Facing (? MP) 13 MP Rear Facing with Autofocus and LED Flash, Front Facing (? MP)
Display 3.8" WVGA LCD-TFT 4.03" SWVGA (1024x600) LCD-TFT
Battery 3.3 Whr removable 5.6 Whr removable
OS Android 2.3.2 (Gingerbread) Android 4.0.3 (ICS)

We're taking a look at just CPU, GPU, and power performance today on MSM8960, as cellular baseband is disabled on the MDP just like it was when we looked at the previous MSM8660 MDP. We'll get a chance to investigate that further in the future, again right now the key areas are CPU, GPU, and power.

As we talked about in the previous MDP piece, the purpose of the MDP is just to serve as a reference design for both Qualcomm to get its Android port running on, and also for individual developers to profile and test their applications against. It's analogous to TI's OMAP Blaze platforms - you won't ever likely see one out in the wild, but it's a reference target that the silicon vendor leverages to port Android, and a piece of hardware that OEMs can use as a reference when they start customizing and building handsets.

Just like last time the MDP also comes with a software build that lets us easily enable or disable vsync on the device, restart surfaceflinger, and then run benchmark tests. There's no such analog for shipping retail devices, only development builds contain this functionality. As there are parts of each benchmark that could instantaneously peak over vsync's 60 FPS on some of the shipping platforms we're comparing to, we're providing results with vsync on and off.

In addition, last time when we ran tests on the MDP MSM8660 I noted that the governor was set to "performance" mode, which means it doesn't adaptively change CPU frequency as a function of load - it was 1.5 GHz all the time. This time the MDP MSM8960 came running with the much more typical "ondemand" governor selected, which does scale CPU frequency as a function of load, so there's less of a concern about the lack of pauses while the CPU changes performance states making results non comparable.

CPU Performance - 1.5 GHz Dual Core Krait
POST A COMMENT

86 Comments

View All Comments

  • Exophase - Wednesday, February 22, 2012 - link

    That 750mW is not for the entire core, it's for the CPU with hyperthreading disabled plus L2 cache. Intel said enabling hyperthreading adds some further draw to it, something between 10-20% as far as I can remember. Reply
  • hova2012 - Tuesday, February 21, 2012 - link

    I'm pretty sure I'm not the only one who is disappointed that the Krait dual core wasn't compared to intel's upcoming atom socs. Isn't this the generation that was supposed to bring arm up to parity with intel's chip? All in all this was a great article, sets the standard for tech reviews. Reply
  • Exophase - Wednesday, February 22, 2012 - link

    Hard to give a good comparison when you don't have direct access to Intel's reference hardware, or if you do you aren't under liberty to publish benchmarking results. Reply
  • Lucian Armasu - Tuesday, February 21, 2012 - link

    Why are the MDP versions of Qualcomm's chips significantly higher performance than the ones in the market, like the one in the HTC Rezound? Doesn't that seem strange to you?

    Could it be that Qualcomm's MDP chips are meant to run significantly faster to show good benchmarks, but then they weaken them in shipping products? Or is there something I'm missing?
    Reply
  • Death666Angel - Tuesday, February 21, 2012 - link

    How would they weaken them in shipping products?
    Do you have more comparisons between the MDP and shipping phones apart from the Rezound?
    I would look to different governor settings, different software builts and different settings as an explanation before jumping into conspiracy territory. :D
    Reply
  • Lucian Armasu - Tuesday, February 21, 2012 - link

    I was just looking at the score charts Anandtech provided. Look at these 2 for example:

    http://images.anandtech.com/graphs/graph5559/44380...

    http://images.anandtech.com/graphs/graph5559/44383...

    Why does the MDP MSM8660 have significantly higher (double) performance than the presumably "same" MSM8660 chip in HTC Rezound? Isn't the MDP MSM8660 supposed to showcase the same MSM8660 that will go into the market?

    I'd love for Brian or Anand to prove me wrong here with some kind of technical explanation, but until then I'll just assume it's Qualcomm being sneaky and trying to manipulate the public's opinion about their chips.
    Reply
  • ndk - Tuesday, February 21, 2012 - link

    The article clearly mentions that MDP 8660 was running with governor settings at "performance". I can't imagine HTC or any other company shipping their products with this setting on. Reply
  • Brian Klug - Tuesday, February 21, 2012 - link

    NDK is correct about governor being the reason, and I found that result interesting as well.

    It's clear to me at least that the governor settings on the Rezound are fairly conservative, and that even with a workload that's supposed to completely load both cores (mashing the multi-threaded test button in linpack pro), you never really get better that single threaded performance.

    -Brian
    Reply
  • infra_red_dude - Tuesday, February 21, 2012 - link

    All the overlay customization by OEM and the power management code in the device kernel does have a detrimental effect on the device's performance. Reply
  • phoenix_rizzen - Tuesday, February 21, 2012 - link

    Not to mention versions of Android. The MDP is running 4.0.3. What's the Rezound running? Reply

Log in

Don't have an account? Sign up now