Skip to content

March 18, 2017

Galaxy S8 benchmarks show Exynos 8895 outpacing the Snapdragon 835

by John_A

Samsung’s Exynos version of its Galaxy S8 appears to outperform Qualcomm’s in GeekBench.

Adding to the pile of Samsung Galaxy S8 rumors that are stacking up as high as the Leaning Tower of Pisa is this GeekBench discovery. Uploaded earlier this week, the GeekBench score shows Samsung taking the cake. It has the top two spots on the chart, with its Exynos 8895 processor leading the pack, and the Galaxy S8+ with the Snapdragon 835 ranking in at a close second.

galaxy-s8-s8-plus-renders-6.jpg?itok=3im

The Exynos 8895 is the successor to the Exynos 8890, which was featured on the international variant of the Galaxy S7 Edge. Like its predecessor, the Exynos 8895 will be exclusive to the Galaxy S8 sold in international markets. The U.S. will get the Snapdragon 835 version, which is what’s sitting pretty in second place.

But all in all, benchmarks are still just numbers, and just because they exist within certain benchmarking suites, those numbers aren’t the final say on whether one processor is best for a mobile device over another.

For everyone obsessing over which CPU is better for the Galaxy S8. pic.twitter.com/28TTXdIDhW

— Jerry Hildenbrand (@gbhil) March 17, 2017

Samsung Galaxy S8 and S8 Plus

  • Latest Galaxy S8 rumors!
  • Galaxy S8 announcement coming March 29 in NYC
  • Galaxy S8 release date set for April 28
  • Join our Galaxy S8 forums

Advertisements
Read more from News

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Note: HTML is allowed. Your email address will never be published.

Subscribe to comments

%d bloggers like this: