Our Windows performance analysis takes place on Intel's Bay Trail Form Factor Reference Design. The 10-inch tablet features a 2560 x 1440 display, 2GB of LPDDR3-1067 memory and a 64GB eMMC solution. The platform was running Windows 8.1 (32-bit).

Intel left me to install and run anything I wanted to during a period of a few hours at their campus in Santa Clara. I got a feel for the speed and snappiness of Bay Trail during my benchmark setup/installation process. While I don't believe Clover Trail was really usable in Windows 8's desktop mode (it was just too slow), the same is definitely not true for Bay Trail. With the exception of a few benchmark installs or loads that simply took forever, my Bay Trail experience was really quite good under Windows. Bay Trail is obviously not as fast as Haswell when it comes to general usage, but it's definitely worthy of a discussion. Whether or not it actually is good enough for an entry level machine will depend on how OEMs choose to configure their Bay Trail systems. I'll hold off on a final verdict here until we have some time with final Bay Trail devices and not just FFRDs.

Intel already teased the Atom Z3770's multithreaded Cinebench performance, but what about single threaded performance? Remember that single threaded performance is often a signfiicant contributor to things like application responsiveness.

Cinebench R11.5 - Single-Threaded Benchmark

The single threaded performance numbers are just barely ahead of AMD's Jaguar based Kabini SoC. The big difference however is power. I had Intel measure SoC power at the board level while running a single threaded Cinebench 11.5 run on the Atom Z3770 and saw a range of 800mW - 1.2W. AMD on the other hand lists the A4-5000's SoC/APU idle power as 770mW. I don't have equivalent data for AMD, but with the A4-5000 idling at 770mW, it's safe to say that SoC level power consumption is lower on Bay Trail. The A10-4600M/Trinity comparison is interesting as it really helps put Bay Trail's performance in perspective as well.

Cinebench R11.5 - Multi-Threaded Benchmark

Multithreaded performance puts Bay Trail and AMD's Kabini at similar performance levels. Once again, looking at SoC power however the Atom Z3770 pulls around 2.5W in this test. Looking at the increase in platform power for the A4-5000 here, I'm assuming that the equivalent data for AMD would put Kabini in the 6W range. Multithreaded performance comes very close to the Pentium 2020M, but that's really overstating the strength of Bay Trail here as the Atom Z3770 has twice as many cores as the Pentium 2020M.

Single threaded integer performance is likely more useful to know, especially given Bay Trail's target market. For a rough idea of what to expect there, we turn to 7-Zip's built in benchmark. The dataset footprint is large enough to require main memory accesses, making this benchmark a little more interesting than it otherwise would've been. I unfortunately don't have access to all the CPUs here, so the 2C/4T 1.9GHz Core i7 3517U turns into a 2C/4T 1.7GHz Core i5 3317U as it's the only comparison data I had handy:

7-Zip Single-Threaded Benchmark

While Silvermont's single threaded FP performance seemed identical to Jaguar, its single threaded integer performance is much higher in the 7-Zip benchmark. Here the Atom Z3770 is 25% faster than the A4-5000. Looking further up the list however, there's still a healthy gap between thermally constrained Ivy Bridge Ultrabook class parts and the best Bay Trail has to offer. In this case Surface Pro's silicon is 70% faster than Bay Trail. Depending on your perspective that's either a huge difference or remarkably small given how wide the previous Atom to Core gap was.

7-Zip also features a multithreaded benchmark. Here we're looking at the same workload, but now split across all available cores/threads:

7-Zip Multi-Threaded Benchmark

In multithreaded integer workloads, the Z3770 gets dangerously close to Ivy Bridge levels of performance. Again, we're overstating Bay Trail's performance here as the Z3770 has four cores while the Core i5-3317U only has two (but with Hyper Threading presenting another 2 virtual cores). I don't believe most tablet workloads are heavily threaded integer workloads, however the world is hardly single threaded anymore. The reality is that a quad-core Bay Trail should perform somewhere between 40% - 80% of a dual-core Ivy Bridge.

For what its worth, Bay Trail SoC power during the multithreaded 7-Zip benchmark was between 1.9W - 2.5W. At this point there's no question in my mind that Silvermont and Bay Trail are truly tablet-class power consumers.

Our next tests are browser based benchmarks that, once again, hope to characterize Bay Trail's performance in a manner that's more representative of lighter client workloads:

Mozilla Kraken Benchmark (Chrome)

The Silvermont vs. Jaguar comparison shows a 29% advantage for Intel. Looking back at Clover Trail vs. Bay Trail, the performance improvement is staggering. Intel improved performance by over 3x at this point. The 17W Ivy Bridge vs. Bay Trail comparison continues to be interesting. Here the Core i5-3317U completes the Kraken test in half the time of the Atom Z3770.

SunSpider 0.9.1 Benchmark (Chrome)

The Silvermont/Jaguar gap in SunSpider shrinks a bit in SunSpider. Bay Trail is still over 2x faster than Clover Trail, and Ivy Bridge remains over 2x the speed of Bay Trail.

For our final light CPU workload test we have PCMark 7. This is an interesting benchmark as it takes into account the storage subsystem a bit. Keep in mind here that the Bay Trail system is using eMMC based storage, while all of the others are using a standard SSD (Samsung SSD 830):

PCMark 7 (2013)

As we saw earlier, Bay Trail can make up for its single threaded performance by doing quite well in multithreaded tests. PCMark 7 attempts to present a mixed workload view of Bay Trail's performance and the result is relatively similar to AMD's Jaguar based A4-5000 Kabini APU. AMD's Trinity ends up being just under 30% faster than Bay Trail, while 17W Ivy Bridge is 60% faster. Overall platform performance is definitely not bad at all as long as the OEM does a good job specing the device. In this case the Samsung eMMC solution in the Bay Trail tablet reference design was surprisingly decent.

GPU Performance

Arguably the more interesting CPU and GPU tests will come in the Android section but I borrowed some Android data from our Kabini review and ran through 3DMark, GFXBench 2.7 and some lighter Steam games:

3DMark - Ice Storm

Bay Trail's overall 3DMark Ice Storm score (720p) is about on par with Brazos rather than being a competitor for Kabini. Bay Trail's HD Graphics core is based on Ivy Bridge and it's a cut down implementation at that.

3DMark - Physics

3DMark's Physics test is basically a multithreaded CPU benchmark, which allows the Z3770 to pull ahead of the A4-5000.

3DMark - Graphics

If we isolate graphics alone however, the Z3770 once again falls behind Brazos.

GFXBench 2.7's T-Rex HD test seems to agree with what 3DMark tells us:

GL/DXBenchmark 2.7 - T-Rex HD (Offscreen)

Obviously under Windows we have more opportunities to benchmark actual game performance. I turned to the lighter (1366 x 768, low quality) game benchmarks I ran for our HD 5000 comparison. I had to exclude Super Street Fighter IV as a driver problem kept it from running on the Bay Trail FFRD.

In a couple of cases Bay Trail delivers roughly half the GPU performance of a 2011 11-inch MacBook Air, but in a much lower power package. Minecraft saw a bigger gap at 1/3 the performance. None of these games are really playable, but that doesn't mean others aren't. I was able to play Team Fortress 2 on Intel's Bay Trail FFRD (with a Bluetooth keyboard and mouse of course) at reasonable frame rates. The system would chunk occasionally but for the most part it was relatively quick. Obviously Bay Trail's graphics are better suited for lighter tablet games.

Minecraft

Borderlands 2

GRID 2

 

Introduction Android Performance
Comments Locked

190 Comments

View All Comments

  • PEJUman - Wednesday, September 11, 2013 - link

    NVM, some googling answers my question. Cool.. I learn something today.
  • Kidster3001 - Thursday, September 12, 2013 - link

    All of Android runs in a VM. Every Android device in the world. Apps can call native routines via JNI and some apps do contain native *.so libraries (for multiple ISA's) but in the end, Android is a VM. Your UI, your system apps, everything runs through Dalvik.

    The difference between Atom devices and ARM devices is that Intel has included a binary translator to convert the ARM *.so to x86 code on-the-fly. If there are no x86 .so included in the app then the x86 device will use the ARM-v7a library via the translator.

    It is very easy for app developers to compile their libraries natively if they choose. Most apps have NO native libraries in them, they're all Java. When compiling a native app, just tell the system which ISAs to compile for. Of those apps which do have native components most compile for ARM, ARM-v7a and MIPS. Flicking another switch to also compile for x86 is not that difficult.
  • monstercameron - Friday, September 13, 2013 - link

    kabini android, nope those are most likely the windows results.
  • lmcd - Wednesday, September 11, 2013 - link

    Yeah, I imagine or at least hope Kabini + HPL process is on the queue. That would make Intel work a bit harder.
  • Nagorak - Wednesday, September 11, 2013 - link

    It wouldn't be anywhere close. AMD doesn't have Intel's process advantage. If AMD could get power down by just cutting GPU performance then they probably would have done so. In a tablet power consumption is pretty damn important.

    In fact, more so than these load tests, idle power consumption is probably the key, and that wasn't fully tested at this point.
  • andrewaggb - Wednesday, September 11, 2013 - link

    I kinda expected more. It should make for a decent windows 8 tablet, but given that the new iphone has 2x cpu/gpu I think it's pretty safe to say the next ipad will destroy this thing graphically.

    Intel needs to become a graphics leader now.... not in 2-5 years.
  • kyuu - Wednesday, September 11, 2013 - link

    Obviously the proper comparison here would be with Temash, since that's AMD's tablet SoC. Kabini isn't meant to compete with Bay Trail in power consumption, so it's pretty far from a surprise that it draws more power.

    I'm guessing the results would be pretty much the same: Bay Trail beats Temash slightly in CPU benches, but still gets soundly thrashed in GPU benches.

    Also, don't the current Kabini SKUs lack AMD's equivalent of turbo boosting? I thought I saw that on the Kabini review article...
  • silverblue - Wednesday, September 11, 2013 - link

    The comparison with Kabini is an interesting one. Kabini supports more instruction sets (Bay Trail is Westmere-level which means it lacks AVX) but it has a single memory channel and lacks any form of turbo. Amusingly though, Kabini is practically on-par here in terms of single threading (per clock) but is being hampered a little in multi-threading if 7-Zip is any indication (memory bandwidth?).

    Add in turbo to Kabini and the Bay Trail advantage in single-threading disappears, but power usage is obviously higher. AMD have their work cut out here; Beema (and HSA) can't come soon enough.

    I think AMD's yearly cadence will help here - Beema has HSA plus GCN2.0 at the very least on a more mature 28nm process - however AMD will still be on 28nm when Intel goes 14nm. Still, if HSA is the be-all-and-end-all that we've been told it is, they have hope.

    The 4600M is embarrassed in CineBench; clock either SoC at 2GHz and they'll equal it for far less power. CineBench is very Intel-friendly, though the same trick in 7-Zip's multi-threaded test would result in the same outcome. Proof indeed that Kaveri is needed.
  • zeo - Wednesday, September 11, 2013 - link

    Kabini has Turbo, only the two dual core Temash models drops it... and Bay Trail has its alternative to Turbo Boost that's called Burst technology...

    And HSA requires industry support... they need to make it a standard, which is why they started up the HSA Foundation, but until that happens then it's only a novelty like Nvidia's CUDA, and right now it's mainly just ARM backing them there so far...
  • silverblue - Thursday, September 12, 2013 - link

    The only Jaguar-based chip (outside of consoles) with any turbo functionality (note I'm typing "turbo" in lower case as I'm referring to the basic technology and not a specific implementation) is, at this time, the A6-1450, which is a Temash chip. In addition, without the turbo dock, it cannot actually achieve its turbo frequencies.

    As regards HSA, here's something quoted from the AMD website:

    "The founding members of HSA are: AMD, ARM, Imagination Technologies, MediaTek, Texas Instruments, Samsung Electronics and Qualcomm®."

    Consider that ARM is what generally binds most of these together, and their huge dominance of the smartphone and tablet market, and you can easily see that HSA isn't just another "novelty like Nvidia's CUDA".

    http://developer.amd.com/resources/heterogeneous-c...

Log in

Don't have an account? Sign up now