In what has become an annual tradition for Qualcomm, the company has once again opened the doors of their San Diego headquarters to the press to take a preview look at the next generation of their flagship mobile platform. These events have been going on for several years now, and have become an integral part of how Qualcomm approaches the public with their wares; preview events not only let them set expectations, but to get the word out to technically-minded audiences in a vendor-neutral manner. Rather than being one part in the next flagship smartphone, preview day means that everything can be about Qualcomm and the platforms that they have created.

Late last year Qualcomm announced the Snapdragon 845 platform, the successor to 2017’s Snapdragon 835. Implementing a number of important architectural improvements over its predecessor, the Snapdragon 845 gets to follow-up on what ended up being a rather well-received platform in the Snapdragon 835, and to see if Qualcomm can maintain their momentum. Qualcomm used their December event to release a good bit of info on the 845 in advance, so we’ve already had a chance to see what Qualcomm is planning architecturally. And now with the preview event we finally get to see how all of this comes together with a look at the platform as a whole.

Whenever discussing the state of affairs of Qualcomm’s flagship SoCs, I always struggle not to tie it to the Snapdragon 810 in some fashion. Which not to beat Qualcomm over the head for past mistakes – in that case a poorly thought out response to Apple – but rather because it serves as a such a great point of reference for discussing the company’s SoC development as a whole. 810 was arguably the company’s low point, so everything since then has been part of a rather remarkable upward trajectory for the flagship Snapdragon. Even though Qualcomm has been leading the pack in high performance SoCs for several years now, last year’s Snapdragon 835 in particular really felt like Qualcomm was in that position for all-around technical capabilities and not merely because of size, momentum, and the realities of LTE licensing.

All of this means that there’s a lot riding on the Snapdragon 845, just in a different and less obvious way than before. Qualcomm has redeemed themselves from the 810 and it’s not a question of whether they can put together a great SoC, but instead it’s a question of how they will follow up upon a great SoC like the 835.

Qualcomm Snapdragon 845 vs 835
SoC Snapdragon 845 Snapdragon 835
CPU 4x Kryo 385 Gold (A75 derivative)
@ 2.8GHz 4x256KB L2

4x Kryo 385 Silver (A55 derivative)
@ 1.77GHz 4x128KB L2

2MB L3 in DSU
4x Kryo 280 Gold (A73 derivative)
@ 2.45GHz 2MB L2

4x Kryo 280 Silver (A53 derivative)
@ 1.90GHz 1MB L2
GPU Adreno 630 Adreno 540 @ 670/710MHz
Memory 4x 16-bit CH @ 1866MHz

3MB system cache
4x 16-bit CH @ 1866MHz
ISP/Camera Dual 14-bit Spectra 280 ISP
1x 32MP or 2x 16MP
Dual 14-bit Spectra 180 ISP
1x 32MP or 2x 16MP
2160p60 10-bit H.265
2160p30 (2160p60 decode),
1080p120 H.264 & H.265
Integrated Modem Snapdragon X20 LTE
(Category 18/13)

DL = 1200Mbps
5x20MHz CA, 256-QAM

UL = 150Mbps
2x20MHz CA, 64-QAM
Snapdragon X16 LTE
(Category 16/13)

DL = 1000Mbps
3x20MHz CA, 256-QAM

UL = 150Mbps
2x20MHz CA, 64-QAM
Mfc. Process 10nm LPP 10nm LPE

The answer to that comes in the form of the Snapdragon 845, an interesting SoC that is a “tock” design if there ever was one. Qualcomm doesn’t get the advantage of an entirely new manufacturing node – the 845 is being made on Samsung’s second-generation 10LPP process, a refined version of 10LPE used for the 835 – so Qualcomm’s improvements are rooted almost entirely in architecture rather than a mix of architecture and manufacturing. Which is to say that it’s a bit of an uphill challenge for the company, but the flip side of that argument is that it’s going to be a chance for Qualcomm’s architectural engineers to take attention front and center.

What the Snapdragon 845 entails then, as we originally learned late last year, is a series of upgrades and overhauls across all the various subsystems of the SoC. Arguably the biggest news here is that Qualcomm’s latest-generation Kyro 385-series CPU cores are derived from ARM’s Cortex-A75 and A55 designs, and that the resulting SoC is the first to employ ARM's DynamiQ CPU cluster organization. DynamIQ enables the various different CPU cores within an SoC to be hosted within the same cluster and cache hierarchy, as opposed to having separate discrete clusters with no shared cache between them, allowing for finer-grained and more efficient approaches to when and how various clusters are powered up. Meanwhile on the GPU side, the notoriously tight-lipped GPU group over at Qualcomm has confirmed that the Snapdragon 845 implements the first Adreno 600 series GPU, which in turn is the first new GPU architecture from Qualcomm in a couple of years and promises some significant performance improvements.

Outside of the core processor architecture, the changes in the rest of the SoC are perhaps not quite as dramatic, but still important to the platform as a whole. This includes, of course, Qualcomm’s latest and greatest LTE modem, the Snapdragon X20, upgrading Qualcomm’s LTE capabilities category 18. Both the camera ISP and Hexagon DSP have also been upgraded as well with the introduction of the Spectra 280 and Hexagon 685, which Qualcomm will be leveraging for camera image quality improvements and their stake in the modern mobile AI race respectively. Finally, the SoC also includes the latest version of the company’s Aqstic audio codec, which although audio has not traditionally been heavily promoted by the company, will be an increasingly important part of differentiating itself from other high-performance mobile SoCs.

Getting down to the heart of matters then, this year’s flagship Snapdragon platform preview is a lot like last year’s. We’re once again taking a look at a Qualcomm Reference Design (QRD), which is a fully functional smartphones in a slightly oversized, utilitarian chassis used for hardware testing and software development. The Snapdragon 835 QRD was a 5.5-inch equivalent phone, and for the 845 QRD Qualcomm has stuck with much the same. The device itself is unremarkable, featuring a 1440p LCD and 6GB of LPDDR4X memory, but it’s otherwise typical of the class of Snapdragon 845 devices we expect to see starting a bit later this year.

Similarly, while this is still a preview, final device performance shouldn’t be too much different from what we see with Qualcomm’s QRD. Vendors do make customizations to both hardware and software, so how a device’s cooling system is built or how aggressive the power management is configured will have an impact on final performance. But as far as stock performance goes, the QRD is about as neural as it gets, if not a slightly idealized case for the platform as it allows Qualcomm to optimally configure the phone themselves.

CPU & Memory Subsystem
Comments Locked


View All Comments

  • jjj - Monday, February 12, 2018 - link

    In high end phones perf doesn't quite matter anymore but A75 looks interesting.
    You seems to not like it and it's very suspicious that you have GPU power numbers but not CPU - that's the most important info we needed here, the only risk to see a big negative change.The one thing you had to look at and you don't..
    Anyway, since you avoid looking at what matters (and that really stinks), excluding power numbers, why wouldn't you like A75? It's a tiny core that gets quite awesome perf numbers, can't wait for server SoCs at 4GHz or more. 1 or almost 1 per MHz in GB integer for such a small core is awesome. If power is not terrible, sounds like a fantastic core. FP is a bit behind but maybe that's ok nowadays.
  • Andrei Frumusanu - Monday, February 12, 2018 - link

    I'm not sure you read the article before writing your criticism, we explicitly talked about CPU power at the end:

    > And while we weren’t able to test for system power efficiency improvements for this preview, we weren’t left empty-handed and were able to quickly do a CPU power virus on the QRD845. The results there have turned out promising, with 1W per-core and slightly under 4W for four-core power usage, which are very much in line with the Snapdragon 835.

    I also explicitly state that it's disappointing that it didn't reach many of ARM's performance targets, in some tests it merely falls back to a clock frequency advantage.
  • jjj - Monday, February 12, 2018 - link

    My bad, only looked at the benchmarks, for the most part. Thanks for pointing out the power numbers. and if I may suggest, that info, even if limited, should be in the CPU section and visible.

    In GB, I am quite happy with it. To quote GB's knowledge base "Geekbench 4 uses a Microsoft Surface Book with an Intel Core i7-6600U processor as the baseline with a score of 4,000 points.".
    The clocks there peak at 3.4GHz so that means 1.1764 per MHz. Granted, not sure how much of that stands with the latest versions of the benchmark , might have changed since v.4.0. Anyway, you got Intel at 18% higher in integer and 59% in FP, clock for clock but with a many times larger core- we'll see how power compares at 4GHz or above.
    I'm impressed by perf density, not necessarily absolute perf and i also remind myself that very high ST perf is only needed in some niches. They do need some further gains with future gens but they are on the right track and it's starting to be exciting.

    Any chance you guys could do a A75 vs Coffee Lake, Ryzen and Atom and not focus on only SPEC?
  • ZolaIII - Monday, February 12, 2018 - link

    Geek bench is highly unoptimized for X86 (probably not good optimized for ARM either) so for any real comparation you would have to compile it from the source with optimal flags...
  • name99 - Monday, February 12, 2018 - link

    Of course it is ("highly unoptimized for X86")...
    And you learned this how, exactly?
    Hell, why don't you throw in the obligatory "John Poole is on the Apple payroll" while you're about it?
  • ZolaIII - Monday, February 12, 2018 - link

    As it is! & it's Open Source but people like you don't even know what that is. So you fatch the code, add optimisation flags and compile it for a given target instead using generic one built for degeneric.
  • Wilco1 - Monday, February 12, 2018 - link

    Geekbench isn't open source. Neither is it unoptimized for x86, the same compiler and the same options are used across multiple OSes and ISAs.
  • Pdimri - Monday, February 12, 2018 - link

    What are the chances Google coming up its own SOC in next Pixel device to compete with A11 chip. Snapdragon chipset is lagging behind on year to year basis and this gap is going to widen even more.
  • Andrei Frumusanu - Monday, February 12, 2018 - link

    Zero in my opinion.
  • Speedfriend - Monday, February 12, 2018 - link

    Andrei - is that zero that they do they own chip or zero that it is competitive with Apple's?

Log in

Don't have an account? Sign up now