Quote from: Sambit Saha on October 24, 2024, 21:15:38The 8 Elite consumes 0.3 W more than the A18 Pro while being around 5% slower the single-core test.
In Geekerwan's multi-core test, the A18 Pro consumes 27% lower power, but is only around 12% slower.
Quote from: Disrupt on October 24, 2024, 15:23:15You know that your product has been successful, when you've managed to trigger a certain group of fruit company fanboys and gotten them to the point, where they foam at the mouth. And that's over an soc that delivers upwards of 20% more multicore performance, while consuming 3/10's of a watt more power and having two extra CPU cores to work with. The years of Apple's complete dominance over phone soc performance are almost over, it's time to make room for more competitors. 6.6W vs 6.9W is literally a difference of less than 6%, ain't that gonna put a dent on your battery life. /s
If anything, everyone expected QCom's S8Elite to be way more power hungry, considering the fact that it has more cores to feed power to. But that's not the case is it? Nope. If anything, this showcases that the Nuvia design influence has culminated in the S8Elite being an efficiency monster this time around.
3/10's of 1W means 0.3, the difference between 6.6 and 6.9, or less than 5 percent basically. Nothing to write home about, when it comes to power/watt or efficiency. And that percentage also applies to the difference between the single core performance of both chips, it's approximately 5 percent, maybe a little bit over that.
But it's still a far cry from prior gens, where we saw much greater efficiency with Apple chips while delivering 30 percent greater single core performance. And this test had the Apple chip running on an optimised Apple compiler, while the other two were running on GB's generic compiler...and the S8Elite still surpassed the A18 pro's multicore performance, while falling behind by about 6% in single core performance. This time around they're more evenly matched, even though it's apples vs oranges, due to one running on its own compiler and the other running on a generic one.