Samsung's latest and greatest Galaxy S10+ is on our test bench, so we pitted it against Apple's flagship iPhone XS Max to see which phone takes the crown in our a benchmarking showdown.
Apple's iPhone XS Max is now around six months old, but it still has impressive specs. Inside the iPhone is Apple's A12 Bionic processor and 4GB of RAM.
The Galaxy S10+ is using an eight-core Snapdragon 855 processor in the US, and is packing 8GB of RAM.
We ran a slew of different benchmarking tests with both phones, designed to test everyday performance, the limits of the GPU, browser capabilities, and more.
The tests
Starting off, we jumped into Geekbench 4 which runs a battery of tests to simulate real-world tasks. Apple's iPhone XS Max pulled well ahead in the single core with 4828 against the S10+'s 3426 but was edged out by the Galaxy S10+ in multicore where iPhone earned 10355 against the Galaxy's 10466.
For comparison, our S9+ earned 2007 and 8307 on the single and multi-core tests respectively.
We then moved on to the AnTuTu benchmarking test. The iPhone XS Max was handily beaten by the Galaxy S10+ in total score, and most of the individual tests. The S10+ earned a 362392 against the iPhone's 313461. Apple's handset did manage to win one category, beating the Galaxy in RAM usage.
Jumping into the browser, we ran the AnTuTu browser JavaScript benchmark. As we were running the test, we knew the iPhone would lose out. Many of the in-browser animations were jumpy or slow on the iPhone where they were smooth on the S10+. Final results gave the S10+ a score of 41673 and the iPhone a score of 39378.
We then turned to the Octane 2.0 test, which while retired, still gives a solid gauge of web performance, especially to compare to previous year's tests like on the S9+ and iPhone X.
Here, the iPhone won easily with a score of 37035, significantly above the 25114 we saw from the S10+.
Our last graphics test was the GFXBench benchmark. There are multiple tests to compare, but when looking at the most recently added high tier Aztec Ruins test, the iPhone earned 1403.77 frames at a 21.8 fps against the S10 which pulled 1642 frames at 26 fps. Close, but the Galaxy S10+ won again here.
Lastly, we tested wireless performance on our home network. Running on a 802.11ac network, our S10+ pulled on average 120Mbps where our iPhone earned around 100Mbps. This will vary a great deal from setup to setup, though.
A new king?
The results here are impressive — for both handsets. Apple's iPhone held its own, winning in multiple categories despite being six months old. On the other hand, the Galaxy S10+ pulled some great numbers that show significant growth over the previous S9.
Where to buy
The Samsung Galaxy S10+ can be pre-ordered from Samsung directly, as well as at Samsung authorized dealers, such as B&H Photo and Amazon.com, with prices starting at $999.
Samsung is also offering a rebate for free Galaxy Buds with S10 and S10+ preorders.
Meanwhile, the following carriers are also offering incentives on both Apple and Samsung devices:
Carrier deals:
- AT&T Wireless: Get up to $1,000 in bill credits with Galaxy S10 preorders.
- Verizon Wireless: Get up to $300 off iPhones with an eligible trade.
- Sprint: Lease an iPhone XS Max and get an iPhone XR for free.
Stay tuned to AppleInsider for further tests and comparisons between Apple and Samsung's flagship devices.
28 Comments
Not to say that the S10 didn’t make huge improvements but my XS Max geek bench scores are. 4821 and 11441. These are consistent scores on my iPhone. You should be getting better multicore scores.
Regardless. Looks like Qualcomm finally figured out how to compete with apple chips. At least until sept.
I wonder why the Qualcom's single core performance is so far behind.
The GFXbench scores are not fair the S10 out of the box is running 1080p. You should run the offscreen tests to make it fairer.
Impressive that they are both so close in performance. The S10+ does pack twice the RAM, so shows that the iPhone is more efficient. I was embarrassed by that stuttering browser test, though. Could Chrome have optimized some routines that made all the difference, and it's not really a phone-performance issue?
Even if an Android phone was besting an iPhone in (undoped) benchmark speed tests, it still wouldn't show that the iPhone was behind. I can't tell you the number of Android-based devices that people have told me were faster than any iPhone that simply couldn't open, switch, or use apps as fast, nor had the same refinement as an iOS app, not yo mention stuttering, lags, and crashing. Is it still much easier and faster to produce better iOS apps than Android apps using fewer resources?