Google Nexus S Processor Overclocked To 1.2GHz

dkd903 writes "Though Google's Nexus S is powered by a single core Hummingbird processor, it looks like the one core would be enough to put LG's dual-core processor powered Optimus to shame. An XDA Forums user morfic has overclocked the processor on Nexus S up to 1.2GHz in a new kernel based on the Bionix NS1 mod."

Really??

[mejogid]

Given that the LG Optimus 2x - also known as the Star - benchmarks pretty impressively, I doubt a Nexus S overclock will put it to shame. In the quadrant benchmark the Nexus S has been noted as obtaining a score of 1474 [nexusoneforum.net], whilst the Star scores 1759 [mobilecrunch.com].

Assuming linear scaling from 1ghz, the Nexus S would obtain 1769 with android 2.3 whilst the star manages the previously stated 1759 with android 2.2 which has received fewer performance optimisations. Whilst this is only one benchmark, the more graphically focussed ones favour the Star's tegra (nVidia) processor to an even greater extent.

Therefore far from putting the new dual core Optimus to shame, I would argue that an overclocked Nexus S can just about keep level with it whilst using a faster OS version on benchmarks that favour it. Hardly putting the Star to shame...

Re:So...

[jsse]

Funny as it seems, but overclocking could sometime save battery life as it could alter the default voltage usage of a particular frequency. At least, this is the case of Nokia N900 with Titan's Kernel Power, where we could choose 'starving' profile for overclocking with less voltage than default. Say it can run at almost half as much voltage at 600Mhz than normal. (fyi. N900 can be overclocked to 1.15GHz max. with Kernel Power)

Re:And?

[Ethanol-fueled]

Meh.

To use a car analogy, overclocking is like adding a fart-pipe to a stock Honda Civic and then bragging to everybody about your extra 25 horsepower of noisy but totally otherwise unnoticable performance gain.

Overclocking != Dual Core

[Lord Byron II]

Not matter how fast a single core goes, there is still a cost associated with having to perform a bunch of context switches and you have to share all of the cache. There are benefits to having a real dual core implementation.