Javascript Performance

Although smartphones are clearly headed for a life beyond simple messaging, web browsing and phone duties, we are still lacking the tools to measure performance in areas other than a component of web page rendering. Measuring javascript performance is one component of the entire web page rendering process but it's the most mature in terms of something we can benchmark.

Sunspider is quite possibly the most well known of these javascript tests:

SunSpider Javascript Benchmark 0.9.1 - Stock Browser

We expected Snapdragon S4 to do very well here based on our preview numbers and it did not disappoint. Although it's not quite as fast as Intel's Medfield, it's clearly the fastest smartphone SoC in this test otherwise. It's worth noting that HTC is able to deliver performance that's within 5% of Qualcomm's Snapdragon S4 MDP, a significant improvement over where things were last year.

The Sunspider test makes good use of 1 - 2 cores but there are times when it'll stress all four on a Tegra 3. For the most part however, NVIDIA's extra cores go unused in this benchmark. Krait and HTC's ICS browser definitely offer a significant advantage over the performance of the ICS launch vehicle, Samsung's Galaxy Nexus. This is honestly the hardware that Google should have used as the basis for its Nexus platform, it's too bad that it wasn't available at the end of last year.

BrowserMark is another js benchmark in our suite:


Here the international and AT&T One Xes trade spots as Tegra 3's extra cores are able to give it the slight edge in performance. Once again we're talking about the fastest smartphones in our test suite.

Low Level FP Performance

Linpack isn't a great indication of smartphone performance, but it is a good test of the floating point capabilities of the CPUs in these SoCs. ARM has steadily been improving FP performance for the past few generations but we're going to see a big jump to Krait/A15. As most client smartphone workloads are integer based and those that are FP heavy end up relying on the GPU, an advantage here doesn't tell us much today (particularly because Linpack isn't running native code but rather atop Dalvik) other than how speedy the FPUs are:

Linpack - Single-threaded

Improved single threaded FP and memory performance is something we get with Krait, and it's demonstrated quite well by the AT&T One X. While you're unlikely to see this magnitude of an advantage in most real world smartphone workloads, this is an architectural advantage of Qualcomm's Krait that's worth mentioning. However these days most FP intensive workloads on smartphones are handled by the GPU, making this performance advantage mostly academic at this point.

Linpack, like many scientific workloads, scales up to multiple cores quite nicely. If we spawn as many threads as there are logical cores (2 for Intel and Qualcomm, but 4 for NVIDIA's Tegra 3) we can see how these SoCs fare in a multithreaded world:

Linpack - Multi-threaded

BaseMark OS

Rightware's BaseMark OS is a general purpose benchmark designed to better simulate overall Android performance. It includes a heavily threaded benchmark, file IO tests, and compression/decompression tasks that all contribute to its overall score. We only have results from the HTC One S/AT&T One X (Snapdragon S4), One X (Tegra 3), Galaxy Nexus (OMAP 4) and the Lava phone (Medfield) here:

BaseMark OS Performance

As expected, the AT&T One X does very well in this general purpose, OS-level benchmark. The device significantly outperforms Samsung's Galaxy Nexus, which isn't a surprise given how dated the hardware was at the time of launch. Again the magnitude of advantage is likely exaggerated by this benchmark, but there's no changing the fact that HTC makes the fastest Android smartphones on the planet for now.

Note that the performance difference between the two One X models is likely exaggerated by BaseMark OS as well. In our regular use we found the two to be fairly similar in performance, with the slight edge going to the AT&T One X but not by a huge margin. You'd be hard pressed to tell these two apart.


Vellamo is a Qualcomm developed benchmark that focuses primarily on browser performance, both in rendering and UI speed. The results are heavily influenced by the browser used on the device being tested. As a whole Vellamo isn't always indicative of whether or not you're going to get a smooth browsing experience, but it's another datapoint that captures more than just javascript performance. The Qualcomm-developed nature of the benchmark is always cause for concern, but even if you exclude the Snapdragon results the benchmark can be useful:

Vellamo Overall Score

Qualcomm's SoCs have always done very well in this Qualcomm-built benchmark, but the results still echo what we've seen in practice. The AT&T One X definitely feels like the fastest Android phone we've used, especially compared to much of what was available last year. The gap between the international and AT&T One X versions is, once again, debatable. The Qualcomm performance advantage is at times perceivable, but I wouldn't consider it to be significant at all.

Flash Rendering Performance

These days nearly all high-end smartphones (I refuse to call them superphones) can render Flash smoothly. The HTC One X is no exception. We're basically at vsync here and will have to move to either more stressful flash content to test or just accept that flash is already performant enough.

CraftyMindFlash Rendering Performance

GPU Performance - GLBenchmark 2.1

As we wait for actual 3D gaming benchmarks to make their way into Android (and hopefully crossplatform) games, we must rely on synthetic tests designed to simulate 3D game performance as best as possible. We start with GLBenchmark, one of the better Android GPU tests on the market today. There are two benchmarks, Egypt and Pro, and each is run in two modes: native screen resolution and offscreen (vsync disabled) at 720p. The latter is more useful for apples to apples comparisons as everything is rendering the same number of pixels, whereas performance in the onscreen tests is determined by the screen resolution of the device along with the performance of its GPU.

GLBenchmark 2.1 - Egypt

Part of the deal in getting Krait to market as quickly as possible required that Qualcomm pair the CPU with an older GPU, in this case the Adreno 225 instead of the newer Adreno 3xx offerings due out later this year. As a result, the AT&T One X can take a back seat to the international One X in GPU performance. When not limited by v-sync, the Tegra 3 based international One X is about 12% faster than the Qualcomm S4 based AT&T One X. For most gaming however, you'll be hard pressed to notice a performance difference.

GLBenchmark 2.1 - Egypt - Offscreen (720p)

GLBenchmark 2.1 - Pro

The Pro offscreen results actually flip flop a bit with the AT&T One X leading the international version. Once again, limited by v-sync (onscreen results) the two are basically identical performers.

GLBenchmark 2.1 - Pro - Offscreen (720p)

Basemark ES 2.0 V1

Rightware's Basemark ES 2.0 V1 is an aging GPU test that tends to favor Qualcomm's Adreno GPUs above almost all others:

RightWare Basemark ES 2.0 V1 - Taiji

RightWare Basemark ES 2.0 V1 - Hoverjet

We're not surprised to see the AT&T One X do so well here as it appears Qualcomm has done quite a bit of optimization work for this particular benchmark. I wouldn't put too much faith in these numbers other than to show you an example of just what can happen with a good amount of optimization on behalf of a hardware vendor.

Battery Life Camera - Stills and Video


View All Comments

  • metafor - Wednesday, May 02, 2012 - link

    His point is that blacks on an LCD require far more power than on an AMOLED. Since a black pixel on an AMOLED = no power used.

    I'm curious as to how the power consumption of a fully white AMOLED screen of equal pixel density and screen size compares to that of an LCD -- at equal brightness of course. This actually shouldn't be very difficult to test and really would be nice in one of these reviews.

    Take the Galaxy Nexus or the upcoming GS3 and the One X, turn off everything (airplane mode, kill all background processes) and disable auto-lock/auto-dim. Turn the screen to various levels of brightness while displaying a pure white screen (several apps will do this).

    Then see how long the phone takes to go from 100% battery to 0%. Extrapolate based on how large the battery is in WH rating.

    Then compare the two.
  • Lucian Armasu - Saturday, May 12, 2012 - link

    Which is why I find it very weird that Samsung didn't go with a more stock ICS dark look for their Galaxy S3. ICS feels like it was made for AMOLED displays, and yet Samsung refuses to use it. Shame. Reply
  • ilkhan - Tuesday, May 01, 2012 - link

    I stopped reading at this line:
    "however the device does not work with T-Mobile WCDMA and the One XL page lists the correct air interface support."
    The rest of it was totally irrelevant after that.
    Pity. That screen has been getting tons of praise.
    Maybe the OneX2 will include a proper GPU and TMo support.
  • ilkhan - Tuesday, May 01, 2012 - link

    (no edits?)
    It was already borderline without a replaceable battery and without an mSD slot. The frequency support just closes the book for sure.

    Which really is a pity. The android phones first got started by word of mouth "expandable storage, easy to hack, total control, function over form", the antithesis of apple. Now they are racing to embrace all the bullshit that apple did 5 years ago. We don't need 7mm thick phones. Gimme the extra 2 extra mm of thickness if it means I get an mSD slot and replaceable larger battery, I'll be happier that way.
  • metafor - Tuesday, May 01, 2012 - link

    Having come from a Sensation to a One S, I gotta say, I love the 7mm thin factor over almost everything else (the weight too). With dropbox and Google music, most of my needs for large storage has been eliminated. Reply
  • ImSpartacus - Tuesday, May 01, 2012 - link

    Just wait. When the market goes far enough in one direction, it opens up a niche market in the other direction.

    You might end up having to use a developer device or something like that, but you'll get your wish.
  • Zoomer - Wednesday, May 02, 2012 - link

    I would like my 4 hardware buttons too. microSIM I suppose is acceptable, though the use of a special tool for access is not.

    Physical Buttons
    Swappable batteries would be a plus, if only for easier debugging / full off.
  • Zoomer - Wednesday, May 02, 2012 - link

    Oh almost forgot, HTC branding on the top of the glass. HTC's the manufacturer, NOT AT&T. AT&T is just pipe. ;) Reply
  • kmmatney - Wednesday, May 02, 2012 - link

    You can always get an external USB battery to use an an extra battery (and it can charge other things to). Reply
  • sprockkets - Tuesday, May 01, 2012 - link

    That's why they make the One S. Shame that has to be the case, but you might like the metal case better. I wish I could open it like the sensation though. Reply

Log in

Don't have an account? Sign up now