5 ms·
Can't find the numbers right now, but I'm pretty sure clock for clock, hummingbird is significantly better than snapdragon. The GPU also matters a lot. One rea
by icegreentea 16y ago
Can't find the numbers right now, but I'm pretty sure clock for clock, hummingbird is significantly better than snapdragon.
The GPU also matters a lot. One reason why the iPhone feels so awesome despite the somewhat slower CPU is that it's GPU blows 80% of android GPUs out of the water. Once again, I'm pretty sure the GPU performance (if its anything like the Galaxy S) utterly destroys the Nexus One.
- mdasen 16y agoThe Galaxy S (which uses the 1GHz Hummingbird processor) benchmarks faster on the Quadrant test (which does test 3D performance) than the Nexus One with Android 2.1, but slower than devices like the Droid X. It's likely that the new Nexus S would be faster than the Nexus One, but not as fast as many other devices that have been out for a while. So, it is an upgrade, but it's below what has already come out from other manufacturers - in contrast with the Nexus One which was an enviable top of the line device when it came out. EDIT: In fact, the Nexus S looks pretty identical to the Galaxy S sans the Samsung software.
- ergo98 16y agoSupposedly there is some sort of issue with the Quadrant test in particular on the Galaxy S. With the fix (the "lag fix") the Galaxy S tops the field. The Galaxy S is a fantastic device. It is essentially a higher clocked version of the iPhone 4.
- flyosity 16y agoHas the Android UI been rewritten to use the GPU? One of the main reasons why scrolling/panning always feels smoother on the iPhone is that the user interface rendering uses the GPU whereas Android does not. If the Nexus S has a fantastic GPU and the UI doesn't use it, that kinda sucks. http://code.google.com/p/android/issues/detail?id=6914 http://code.google.com/p/android/issues/detail?id=6914
- ergo98 16y agoNo. Honeycomb will likely be the first to use GPU UI rendering. The N1 w/2.2 is extremely fluid, with minor stuttering that is attributable to garbage collection (the thing is endlessly pausing to do GC). 2.3 includes a highly optimized concurrent garbage collection so that should strongly improve. However honestly I think it's one of those things that matters a lot if you're, to put it impolitely, dicking around, but becomes irrelevant when you're using it as a tool day to day. Similar to how everyone using a Kindle for the first time hits back and forward a bunch of times and complains about page flip times, whereas to actual readers it just doesn't matter.