Or Continue to Thread: iPad 4 vs 5250 (Nexus 10 Soc) …
Find Your Device:
hot_spare
2nd November 2012, 04:12 PM   |  #6  
Guest
Thanks Meter: 0
 
n/a posts
Angry
I believe we have to take the Arndale board numbers with pinch of salt. It's a dev board, and I doubt it has optimized drivers for the SoC like it's expected for N10. Samsung has this habit of optimizing the drivers with further updates.

SGS2 makes for a good case study. When it was launched in MWC2011, it's numbers were really pathetic. It was even worse than Tegra2.

Anand ran benchmark on the pre-release version of SGS2 on MWC2011, check this:

http://www.anandtech.com/show/4177/s...00-benchmarked

It was showing less than Tegra2 numbers! It was that bad initially.

Then look when Anand finally reviewed the device after few months:

http://www.anandtech.com/show/4686/s...t-redefined/17

Egypt (native resolution) numbers went up by 3.6x and Pro also got 20% higher. Now they could have been higher if not limited by vsync. GLbenchmark moved from 2.0 to 2.1 during that phase, but I am sure this would not make such a big difference in numbers.

If you again check the numbers now for SGS2, it's again another 50% improvement in performance from the time Anand did his review.

Check this SGS2 numbers now:
http://www.anandtech.com/show/5811/s...-s-iii-preview
http://www.anandtech.com/show/6022/s...usa-variants/4

This is just to show that how driver optimization can have a big affect on the performance. My point is that we have to wait for proper testing on final release of N10 device.

Also, check the fill rate properly in the Arndale board test. It's much less than what is expected. ARM says that Mali-T604 clocked at 500MHz should get a fill rate of 2 GPixels/s. It's actually showing just about 60% of what it should be delivering.

http://blogs.arm.com/multimedia/353-...l-not-a-pixel/

Samsung has clocked the GPU @ 533MHz. So, it shouldn't be getting so less.

According to Samsung, it more like 2.1 GPixels/s: http://semiaccurate.com/assets/uploa...nos_5_Mali.jpg

Fill rate is a low-level test, and there shouldn't be such a big difference from the quoted value. Let's wait and see how the final device shapes up.
The Following User Says Thank You to For This Useful Post: [ View ]