The iPhone 6s on paper has a fairly mediocre technical specification with a dual-core processor and 2GB of LPDDR4 RAM. However, the closed ecosystem and software optimization provides surprisingly top-tier performance using lower-end internal hardware. WCCFTech’s benchmark results emphasizes this and the iPhone 6s destroys the competition in Geekbench’s single threaded test.
The iPhone 6s scored a very impressive 2446 which thrashes the Galaxy Note 5’s recorded figure of 1467. However, the top-end Android phones regain the top spot in multi-core workloads due to an Octa-core configuration. Although, the Galaxy Note 5’s score of 4787 isn’t a massive leap from the iPhone 6s multi-core score of 4390.
In AnTuTu, the iPhone 6S attained a score of 58602 which falls significantly behind the Galaxy Note 5’s figure of 69,702. Although, I would have expected the gap to be much larger given the dual core setup.
While the top-end Android phones have a very impressive technical specification, it seems the lack of optimization on Android results in smaller gains than expected. It would be interesting to see the performance numbers from an Octa-core, 4GB RAM Apple device. This doesn’t seem likely for some time though and it’s all down to personal taste. The iPhone 6s is extremely expensive when you factor in the specification, but this doesn’t seem to hold the phone back and does very well in major benchmarks.
Thank you WCCFTech for providing us with this information.
Electronic Arts (EA) announced today that its games were played for over 11 billion hours…
Steam's annual end-of-year recap, Steam Replay, provides fascinating insights into gamer habits by comparing individual…
GSC GameWorld released a major title update for STALKER 2 this seeking, bringing the game…
Without any formal announcement, Intel appears to have revealed its new Core 200H series processors…
Ubisoft is not having the best of times, but despite recent flops, the company still…
If you haven’t started playing STALKER 2: Heart of Chornobyl yet, now might be the…