Now that also battery lifetime and long term performance tests have floated in for the A8X, there doesn't seem any noticable throttling on it and it seems to last a tad over 4 hours in T-Rex.
No throttling in Gfx-Bench T-Rex. But T-Rex is also a pretty favorable Bench for Gpus with FP16 units as it's only using FP16 if i ain't wrong.
All devices eventually throttle; the point is rather where and by how much for each case. Other than that I'd love to know where the hell they've substantiated that the A8X contains a G6650.German Notebookcheck made it throttle, when first using "Relative Benchmark" and then Cpu/Gpu Benches.
http://www.notebookcheck.com/Test-Apple-iPad-Air-2-A1567-128-GB-LTE-Tablet.129027.0.html
CPU throttled 30% by using it afterwards in Geekbench and GPU 15% in 3dmark. But i don't really know whether Relative Benchmark is showing realistic Powernumbers or just numbers like Furmark, which won't happen normally. But at least with this Bench it's also getting pretty hot (43°C) and uses quite a bit of power.
CPU throttled 30% by using it afterwards in Geekbench and GPU 15% in 3dmark. But i don't really know whether Relative Benchmark is showing realistic Powernumbers or just numbers like Furmark, which won't happen normally. But at least with this Bench it's also getting pretty hot (43°C) and uses quite a bit of power.
No throttling in Gfx-Bench T-Rex. But T-Rex is also a pretty favorable Bench for Gpus with FP16 units as it's only using FP16 if i ain't wrong.
No one's released a die shot yet either. They are probably working with Chipworks on that to have some physical evidence for their A8X analysis.Surprised that Anandtech hasn't reviewed the air2 yet, seems a bit slower than in anand's days.
No one's released a die shot yet either. They are probably working with Chipworks on that to have some physical evidence for their A8X analysis.
Perhaps on top of browser tuning, Octane is benefitting more than the other tests from the better memory performance?The jump in performance on Google's Octane V2 benchmark for the Air 2 vs iP6 is surprising. As Octane is primarily a javascript benchmark, I assumed it was mostly single-core bound, does Octane benefit from the Air 2's 3rd core? The Air 2 was launched with iOS 8.1, whereas the iPhone was tested on an earlier version of iOS 8, which could be the difference.
A8X is a 6850. Helps account for a good part of those extra 1B transistors.
http://www.anandtech.com/show/8716/apple-a8xs-gpu-gxa6850-even-better-than-i-thought
There you go Since they just copied and duplicated the GPU part of the A8 die shot, the labeling is most likely not accurate.For that die shot mock up: why would the block named "shared digital logic" in the middle of each quad core double with an 8 cluster config?
Actually it is. If you were to look at the die shot, there's a strip of shared logic running right down the middle of the GPU, clearly different from the 8 USCs. I have to assume the various backends and frontends (ROPs, geometry, etc) were scaled up as well as the number of USCs.There you go Since they just copied and duplicated the GPU part of the A8 die shot, the labeling is most likely not accurate.
Thanks for clearing that upActually it is. If you were to look at the die shot, there's a strip of shared logic running right down the middle of the GPU, clearly different from the 8 USCs. I have to assume the various backends and frontends (ROPs, geometry, etc) were scaled up as well as the number of USCs.