The Nexus 4 is based around a 1.5 GHz Qualcomm Snapdragon S4 Pro SoC, the quad core Krait APQ8064 with Adreno 320 GPU, which is still built on a 28nm process. The combination of APQ8064 for AP and MDM9x15 for baseband is Qualcomm's Fusion 3 platform, and the Nexus 4 and Optimus G are the first phones to market based on that platform. This is a relatively unique opportunity for Nexus, which until recently wasn't really first to market with the latest and greatest silicon. 

A while ago we posted our Nexus 4 and Nexus 10 performance preview. At that point we still had a lot of testing to perform, and many people noted that the Nexus 4 performance was far behind the LG Optimus G despite it being based on the same platform. Later, some people noticed that I had uploaded another set of results from GLBenchmark 2.5 to the online result browser with much better performance. The difference wasn't some over the air software update but rather that I was running some of the tests with the Nexus 4 in a ziplock bag inside the freezer to mitigate any condensation problems, and simultaneously nail down any possible thermal throttling. 

I've re-run everything and can confirm obviously that there was thermal throttling going on affecting some of the results, and have included the new results wherever there was a deviation from previous. For those wondering why the LG Optimus G wasn't affected in spite of it having the same platform, the reason is because the results from the Optimus G were run in parts due to some instability affecting its ability to run a complete set of tests without crashing. The Nexus 4 has newer drivers that don't crash during a full GLBenchmark 2.5 run but as a result run the device long enough for thermal throttling to kick in. 

GLBenchmark 2.5 - Fill Test

GLBenchmark 2.5 - Fill Test (Offscreen 1080p)

GLBenchmark 2.5 - Triangle Texture Test

GLBenchmark 2.5 - Triangle Texture Test (Offscreen 1080p)

GLBenchmark 2.5 - Triangle Texture Test - Fragment Lit

GLBenchmark 2.5 - Triangle Texture Test - Fragment Lit (Offscreen 1080p)

GLBenchmark 2.5 - Triangle Texture Test - Vertex Lit

GLBenchmark 2.5 - Triangle Texture Test - Vertex Lit (Offscreen 1080p)

GLBenchmark 2.5 - Egypt HD

GLBenchmark 2.5 - Egypt HD (Offscreen 1080p)

GLBenchmark 2.5 - Egypt Classic

GLBenchmark 2.5 - Egypt Classic (Offscreen 1080p)

The result of the tests in the freezer results that are much closer to what we'd expect based on the APQ8064 MDP/T runs and the Optimus G numbers I saw in Korea. 

When it comes to the CPU side of things there were results also affected by thermal throttling. I spaced some of those runs out (unintentionally) enough that performance didn't change, but for other things it did affect performance. I can't tell what GPU clocks end up being when the SoC decides to throttle, but it is possible to nail down what CPU performance state APQ8064 settles down into when there's throttling going on by looking at the state tables. 

 
Left - 1.134 GHz during throttling (running tests), Right - All the performance states

I can see the Nexus 4 not use any of the performance states above 1134 MHz when it's getting hot, as shown in the images above. I've tweeted a link to the pastebin for thermald.conf which I believe configures the thermal cutoffs and will be interesting to kernel hackers trying to play with these values. 

SunSpider Javascript Benchmark 0.9.1 - Stock Browser

BrowserMark

Google Octane Benchmark v1

Mozilla Kraken Benchmark

Vellamo Benchmark - 2.0

Vellamo Benchmark - 2.0

Sequential Read (256KB) Performance

Sequential Write (256KB) Performance

Random Read (4KB) Performance

Random Write (4KB) Performance

Our CPU performance side is unfortunately still dominated by JavaScript performance tests. The story there is that the Nexus 4 ships with Chrome (and originally shipped with a newer build of Chrome than what was on the market - we were running that updated version all along) and thus the mainline version of the V8 JavaScript engine. OEMs perform their own optimizations to the V8 library, and try to upstream whatever they can into the main project, but in the case of Chrome for Android that means V8 sans secret OEM sauce. 

Battery Life and Charging Android 4.2 - New Flavor of Jellybean
POST A COMMENT

188 Comments

View All Comments

  • mmrezaie - Wednesday, November 14, 2012 - link

    I don't think so!

    I have been following anandtech from very start. Now I am seeing some disturbing stuff in this site. For example comparing some of the battery life tests I see that there is inconsistency between reports that Anand published and ones that I see in arstechnica, or tomshardware, or even Gigaom. They seem to be on a very special setting that favors apple more often. I have an iphone, ipad, and also galaxy nexus. comparing them I don't think there is that much difference.

    I leave it to the reader but what I think a site like this that puts lots of effort, should not be biased (or seen so). It hearts the reputation. You have some type of reviews that no one else offer. please don't ruin it!
    Reply
  • Klug4Pres - Tuesday, November 13, 2012 - link

    Intro paras repeat.

    p.s. Thanks for the review, Brian.

    Comment Man
    Reply
  • Brian Klug - Tuesday, November 13, 2012 - link

    Oops, fixed! I don't know how that happened...

    -Brian
    Reply
  • Klug4Pres - Tuesday, November 13, 2012 - link

    "fourth incantation"

    "bound to elicit", although illicit could be good also.
    Reply
  • Brian Klug - Tuesday, November 13, 2012 - link

    Fixed! Reply
  • Arbie - Tuesday, November 13, 2012 - link


    They didn't program it in Forth, and it isn't an incantation (!).
    Reply
  • Klug4Pres - Tuesday, November 13, 2012 - link

    Only the 13 MP system (which is an option)

    I suggest "(which is an option for the Optimus G)"
    Reply
  • VivekGowri - Tuesday, November 13, 2012 - link

    You have the best username I've seen in the comments, I'm not even going to lie. Reply
  • Klug4Pres - Thursday, November 15, 2012 - link

    Thanks, Vivek!

    I love the podcasts you guys have been making, and Brian's comments are just very informative and hilarious at the same time, hence the username.
    Reply
  • boozed - Tuesday, November 13, 2012 - link

    Surely there should be a "send corrections" button right next to the "print this article" button? Reply

Log in

Don't have an account? Sign up now