Search the Community

Source: http://www.anandtech.com/show/11201/qualcomm-snapdragon-835-performance-preview/6 It seems that recently Qualcomm invited many reviewers to its San Diego HQ to test phones built around its Snapdragon 835 SoC. These are development phones made by Qualcomm for hardware and software testing, so don't get too excited. The new Snapdragon 835 is an octa core big.LITTLE CPU based on Samsung's new 10 nm LPE lithography, with the power cluster containing 4 Kryo 280 cores at 2.45 ghz and the efficiency core containing 4 Kryo 280 cores at 1.90 ghz. These cores aren't completely new designs, as evidenced by the shared "Kryo" name, but they have some improvements that should bring about higher IPC. It also has a new GPU, the Adreno 540, which should bring a pretty substantial performance improvement compared to the Adreno 530 from the Snapdragon 820 and 821. Anandtech was able to perform quite a few tests. Naturally, I'm not gonna put everything here, but I'll put a few of the benchmarks in order to give you a good idea of how the 835 performs. First up is Geekbench 4's single threaded integer performance. Geekbench 4 - Integer Performance Single Threaded Snapdragon 835 Snapdragon 821 (% Advantage) Snapdragon 810 (% Advantage) AES 905.40 MB/s 559.10 MB/s (61.9%) 714.47 MB/s (26.7%) LZMA 3.13 MB/s 2.20 MB/s (42.3%) 1.92 MB/s (63.0%) JPEG 16.80 Mpixels/s 21.60 Mpixels/s (-22.2%) 12.27 Mpixels/s (36.9%) Canny 23.60 Mpixels/s 30.27 Mpixels/s (-22.0%) 23.63 Mpixels/s (-0.1%) Lua 1.84 MB/s 1.47 MB/s (25.2%) 1.20 MB/s (53.3%) Dijkstra 1.73 MTE/s 1.39 MTE/s (24.5%) 0.91 MTE/s (90.1%) SQLite 53.00 Krows/s 36.67 Krows/s (44.5%) 33.30 Krows/s (59.2%) HTML5 Parse 8.67 MB/s 7.61 MB/s (13.9%) 6.38 MB/s (35.9%) HTML5 DOM 2.26 Melems/s 0.37 Melems/s (510.8%) 1.26 Melems/s (79.4%) Histogram Equalization 52.90 Mpixels/s 51.17 Mpixels/s (3.4%) 53.60 Mpixels/s (-1.3%) PDF Rendering 50.90 Mpixels/s 52.97 Mpixels/s (-3.9%) 43.70 Mpixels/s (16.5%) LLVM 196.80 functions/s 113.53 functions/s (73.3%) 108.87 functions/s (80.8%) Camera 5.71 images/s 7.19 images/s (-20.6%) 4.69 images/s (21.7%) It's quite apparent integer performance was something Qualcomm focused on for Kryo 280. While the improvement over Snapdragon 820 varies from test to test, it's quite apparent Qualcomm definitely has improved. Kryo's integer performance was relatively weak compared to other SoCs, so it's nice to see that Qualcomm has caught up with the rest of the market here. Moving on, we have Geekbench 4's Floating Point Performance. Geekbench 4 - Floating Point Performance Single Threaded Snapdragon 835 Snapdragon 821 (% Advantage) Snapdragon 810 (% Advantage) SGEMM 11.5 GFLOPS 12.2 GFLOPS (-5.7%) 11.0 GFLOPS (4.2%) SFFT 2.9 GFLOPS 3.2 GFLOPS (-9.7%) 2.3 GFLOPS (25.2%) N-Body Physics 879.6 Kpairs/s 1156.7 Kpairs/s (-24.0%) 580.2 Kpairs/s (51.6%) Rigid Body Physics 6181.7 FPS 7171.3 FPS (-13.8%) 4183.4 FPS (47.8%) Ray Tracing 232.6 Kpixels/s 298.7 Kpixels/s (-22.0%) 130.1 Kpixels/s (78.7%) HDR 7.8 Mpixels/s 10.8 Mpixels/s (-27.6%) 6.4 Mpixels/s (21.9%) Gaussian Blur 23.4 Mpixels/s 48.5 Mpixels/s (-51.8%) 21.9 Mpixels/s (6.7%) Speech Recognition 13.9 Words/s 10.9 Words/s (27.5%) 8.1 Words/s (71.4%) Face Detection 513.8 Ksubs/s 685.0 Ksubs/s (-25.0%) 404.4 Ksubs/s (27.0%) Strangely enough, floating point performance seems to have regressed relative to Kryo. This shouldn't be too bad, since Kryo had very strong Floating Point performance, but it still is definitely a strange thing to see. I'll skip the PCMark and Java Script tests, but the 835 is essentially near if not at the top in PCMark and is consistently number 1 or 2 out of the non-Apple SoCs in the JavaScript tests. Now for the GPU tests. I won't bore you guys with all the test. Here's one that's relatively representative of the other tests: As you can see, the new Adreno 540 GPU is now probably the most powerful smartphone GPU, beating out last year's Adreno 530 as well as the PowerVR GPU used in the iPhone 7 and 7 Plus. Now, onto something a bit more interesting... Power consumption! Qualcomm Power Testing - Device Level w/Fixed Workload Power Consumption SD820 Reference Phone 4.60W SD835 Reference Phone 3.56W The Snapdragon 810 really failed hard at power consumption. More insight was recently provided in Anandtech's Kirin 960 review, which you can find here. It showed, the 810 consuming around double the power of other SoCs at the same number of cores utilized (It was consuming 8 watts of power at 3 cores utilized). Snapdragon 820 was a huge jump from this, and it seems Qualcomm has further improved power efficiency with the 835. This is definitely a good step forward. The Snapdragon 835 is looking like a great evolutionary upgrade to the 820. I look forward to seeing the next generation of smartphones utilizing this SoC.

With Intel 10 nm desktop CPUs reportedly arriving early next year (https://wccftech.com/intel-10nm-desktop-cpus-arriving-early-2020/), what is your take on how their performance will stack up against the latest and greatest from AMD? The SKUs will probably not be high-end/enthusiast yet, but still, how do you think the team blue's parts will perform against the same grade/similarly priced AMD counterparts? (Ice Lake mobile has about 18 % IPC improvement over the previous gen.) I think that as soon as intel has something to offer in all the importanat price brackets, they will retake the lead firmly. I'm inclined to that opinion because they already have the lead in gaming, clock speeds and some productivity instances. As soon as they figure out how to pack more cores on a chip efficiently, that will be it.

source: http://www.kitguru.net/components/anton-shilov/intel-delays-ramp-of-10nm-mass-production-due-to-poor-yields-report/ ---- update July 16th: Intel confirms 10nm delays as it enters 3rd generation of 14nm products source: http://arstechnica.com/gadgets/2015/07/intel-confirms-tick-tock-shattering-kaby-lake-processor-as-moores-law-falters/ AnandTech - Intel second quarter earnings --- if Intel delays this 10nm process node they might have a problem, depending on what Samsung can actually produce; this wasn't exactly unexpected