Notebookcheck Logo

Qualcomm Adreno 619L vs Qualcomm Adreno 680

Qualcomm Adreno 619L

► remove from comparison

Die Qualcomm Adreno 619L ist eine im Qualcomm Snapdragon 690 verbaute Grafikeinheit für Smartphones und Tablets (hauptsächlich Android basiert). Sie ist in der unteren Mittelklasse positioniert. 

Die Adreno 600 Serie unterstützt laut Wikipedia Vulkan 1.0, OpenGL ES 3.2, OpenCL 2.0 Full und DirectX 11_1. Der Chip sollte daher ein abgespeckter Adreno 630 (weniger Shader?) sein.

Qualcomm Adreno 680

► remove from comparison

Die Qualcomm Adreno 680 ist eine im Qualcomm Snapdragon 8cx ARM-SoC integrierte Grafikeinheit für Windows-Notebooks und Tablets. Der Chip soll ab Mitte/Ende 2019 erhältlich sein. Architekturell ist die GPU ähnlich zum Adreno 640. Laut Qualcomm 2x schneller als die alte Adreno 630 im Snapdragon 850 für Windows Laptops bei 60% verbesserter Effizienz.

Die Leistung soll verleichbar mit einer Intel UHD Graphics 620 sein, jedoch nur bei nativ für ARM64 kompilierten Spielen und Programmen. Im Emulator laufen nur 32-Bit-Applikationen (keine 64-Bit für AMD/Intel kompilierte) und mit einem deutlichen Geschwindigkeitsnachteil.

Qualcomm Adreno 619LQualcomm Adreno 680
Adreno 600 Serie
Adreno 660 compare
Adreno 650 compare @ 0.25 - 0.67 GHz
Adreno 690 compare
Adreno 685 compare
Adreno 680
Adreno 642 compare
Adreno 642L compare
Adreno 640 compare
Adreno 630 compare
Adreno 620 compare
Adreno 619 compare
Adreno 619L
Adreno 618 compare
Adreno 616 compare
Adreno 612 compare
Adreno 610 compare
Adreno 660 compare
Adreno 650 compare @ 0.25 - 0.67 GHz
Adreno 690 compare
Adreno 685 compare
Adreno 680
Adreno 642 compare
Adreno 642L compare
Adreno 640 compare
Adreno 630 compare
Adreno 620 compare
Adreno 619 compare
Adreno 619L
Adreno 618 compare
Adreno 616 compare
Adreno 612 compare
Adreno 610 compare
ArchitekturAdreno 600
Shared Memoryjaja
APIDirectX 12.1, OpenGL ES 3.2, VulkanDirectX 12
Herstellungsprozess8 nm7 nm
FeaturesOpenGL ES 3.2, OpenCL 2.0, Direct3D 12 (FL 12_1)
Erscheinungsdatum15.12.2015 06.12.2018
Stromverbrauch7 Watt
CPU in Adreno 619LGPU Base SpeedGPU Boost / Turbo
Qualcomm Snapdragon 690 5G8 x 1700 MHz? MHz? MHz
CPU in Adreno 680GPU Base SpeedGPU Boost / Turbo
Qualcomm Snapdragon 8cx Gen 2 5G8 x 3150 MHz, 7 W? MHz? MHz
Qualcomm Snapdragon 8cx8 x 2840 MHz, 7 W? MHz? MHz
min. - max.? MHz? MHz

Benchmarks

3DMark - 3DMark Ice Storm Unlimited Graphics
44899 Points (6%)
3DMark - 3DMark Sling Shot (ES 3.0) Unlimited
min: 3122     avg: 3225     median: 3224.5 (19%)     max: 3327 Points
3DMark - 3DMark Sling Shot (ES 3.0) Unlimited Graphics
min: 3307     avg: 3311     median: 3311 (8%)     max: 3315 Points
3DMark - 3DMark Sling Shot Extreme (ES 3.1) Unlimited
min: 2308     avg: 2328     median: 2328 (19%)     max: 2348 Points
3DMark - 3DMark Sling Shot Extreme (ES 3.1) Unlimited Graphics
min: 2120     avg: 2154     median: 2153.5 (8%)     max: 2187 Points
3DMark - 3DMark Wild Life Unlimited
min: 809     avg: 818     median: 817.5 (1%)     max: 826 Points
3DMark - 3DMark Wild Life Extreme Unlimited
247 Points (1%)
3DMark 11 - 3DM11 Performance Score
min: 1650     avg: 1847     median: 1847 (4%)     max: 2044 Points
3DMark 11 - 3DM11 Performance GPU
min: 1593     avg: 1936     median: 1935.5 (3%)     max: 2278 Points
Cinebench R10 Cinebench R10 Shading (32bit) + Qualcomm Adreno 680
Cinebench R10 - Cinebench R10 Shading (32bit)
353 Points (0%)
GFXBench (DX / GLBenchmark) 2.7
GFXBench 2.7 T-Rex HD Onscreen C24Z16 + Qualcomm Adreno 619L
GFXBench (DX / GLBenchmark) 2.7 - GFXBench 2.7 T-Rex HD Onscreen C24Z16
min: 54     avg: 56     median: 56 (2%)     max: 58 fps
GFXBench 2.7 T-Rex HD Onscreen C24Z16 + Qualcomm Adreno 680
58.9 fps (2%)
GFXBench T-Rex HD Offscreen C24Z16 + Qualcomm Adreno 619L
GFXBench (DX / GLBenchmark) 2.7 - GFXBench T-Rex HD Offscreen C24Z16
min: 72     avg: 72.5     median: 72.5 (1%)     max: 73 fps
GFXBench T-Rex HD Offscreen C24Z16 + Qualcomm Adreno 680
140.2 fps (1%)
GFXBench 3.0 - GFXBench 3.0 Manhattan
min: 30     avg: 31.5     median: 31.5 (9%)     max: 33 fps
GFXBench 3.0 - GFXBench 3.0 Manhattan Offscreen
min: 36     avg: 36.5     median: 36.5 (3%)     max: 37 fps
GFXBench - GFXBench 5.0 Aztec Ruins High Tier Onscreen
min: 8     avg: 8.4     median: 8.4 (5%)     max: 8.7 fps
GFXBench - GFXBench 5.0 Aztec Ruins High Tier Offscreen
5.8 fps (2%)
GFXBench - GFXBench 5.0 Aztec Ruins Normal Tier Onscreen
min: 13     avg: 13.5     median: 13.5 (7%)     max: 14 fps
GFXBench - GFXBench 5.0 Aztec Ruins Normal Tier Offscreen
min: 15     avg: 15.5     median: 15.5 (2%)     max: 16 fps
GFXBench - GFXBench Car Chase Onscreen
min: 12     avg: 12.5     median: 12.5 (0%)     max: 13 fps
GFXBench - GFXBench Car Chase Offscreen
min: 14     avg: 14.5     median: 14.5 (0%)     max: 15 fps
Antutu v9 - AnTuTu v9 GPU
76440 Points (12%)
Basemark GPU 1.2 - Basemark GPU 1.2 Vulkan Official Medium Offscreen 1080
min: 22.78     avg: 22.8     median: 22.8 (2%)     max: 22.85 fps
ComputeMark v2.1 - ComputeMark v2.1 Result
1890 Points (4%)
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile 2D Graphics Tests
30131 Points (30%)
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile 3D Graphics Tests
17916 Points (31%)
Power Consumption - Furmark Stress Test Power Consumption - external Monitor *
12.6 Watt (2%)
012345678910111213Tooltip
Power Consumption - GFXBench Aztec Ruins Normal Tier Offscreen Power Consumption 150cd *
2.4 Watt (3%)
00.20.30.50.60.80.91.11.21.41.51.71.822.12.32.42.62.72.9Tooltip

Average Benchmarks Qualcomm Adreno 619L → 100% n=2

Average Benchmarks Qualcomm Adreno 680 → 149% n=2

- Bereich der Benchmarkergebnisse für diese Grafikkarte
- Durchschnittliche Benchmarkergebnisse für diese Grafikkarte
* Smaller numbers mean a higher performance
1 This benchmark is not used for the average calculation

Spiele-Benchmarks

Die folgenden Benchmarks basieren auf unseren Spieletests mit Testnotebooks. Die Performance dieser Grafikkarte bei den gelisteten Spielen ist abhängig von der verwendeten CPU, Speicherausstattung, Treiber und auch Betriebssystem. Dadurch müssen die untenstehenden Werte nicht repräsentativ sein. Detaillierte Informationen über das verwendete System sehen Sie nach einem Klick auf den fps-Wert.

League of Legends: Wild Rift

League of Legends: Wild Rift

2020
ultra
100%
Adreno 619L:
60 fps  fps
PUBG Mobile

PUBG Mobile

2018
low
100%
Adreno 619L:
39 fps 40 fps ~ 40 fps
med.
100%
Adreno 619L:
40 fps 40 fps ~ 40 fps
high
100%
Adreno 619L:
30 fps 30 fps ~ 30 fps
Dead Trigger 2

Dead Trigger 2

2013
high
100%
Adreno 619L:
60 fps  fps
Asphalt 9: Legends

Asphalt 9: Legends

2013
high
100%
Adreno 619L:
29 fps  fps
Real Racing 3

Real Racing 3

2013
high
100%
Adreno 619L:
60 fps  fps

Average Gaming Qualcomm Adreno 619L → 100%

Average Gaming 30-70 fps → 100%

Eine Liste mit weiteren Spielen und allen Grafikkarten finden Sie auf unserer Seite: Welches Spiel ist mit welcher Grafikkarte spielbar?

Add one or more devices and compare

In the following list you can select (and also search for) devices that should be added to the comparison. You can select more than one device.

restrict list:

show all (including archived), 2022, 2021
v1.18
log 27. 09:46:19

#0 checking url part for id 10573 +0s ... 0s

#1 checking url part for id 9846 +0s ... 0s

#2 not redirecting to Ajax server +0s ... 0s

#3 did not recreate cache, as it is less than 5 days old! Created at Thu, 22 Sep 2022 17:27:05 +0200 +0.001s ... 0.001s

#4 linkCache_getLink no uid found +0.072s ... 0.072s

#5 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.072s

#6 linkCache_getLink using $NBC_LINKCACHE +0.004s ... 0.076s

#7 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#8 linkCache_getLink no uid found +0s ... 0.076s

#9 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#10 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#11 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#12 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#13 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#14 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#15 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#16 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#17 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#18 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#19 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#20 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.076s

#21 composed specs +0s ... 0.076s

#22 did output specs +0s ... 0.076s

#23 start showIntegratedCPUs +0s ... 0.076s

#24 getting avg benchmarks for device 10573 +0.03s ... 0.106s

#25 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.107s

#26 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.107s

#27 got single benchmarks 10573 +0.009s ... 0.116s

#28 getting avg benchmarks for device 9846 +0s ... 0.116s

#29 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.117s

#30 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.117s

#31 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.119s

#32 got single benchmarks 9846 +0.007s ... 0.125s

#33 got avg benchmarks for devices +0s ... 0.125s

#34 linkCache_getLink using $NBC_LINKCACHE +0.004s ... 0.129s

#35 linkCache_getLink using $NBC_LINKCACHE +0.004s ... 0.133s

#36 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.133s

#37 linkCache_getLink using $NBC_LINKCACHE +0.004s ... 0.137s

#38 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.137s

#39 linkCache_getLink using $NBC_LINKCACHE +0.004s ... 0.14s

#40 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.14s

#41 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.141s

#42 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.141s

#43 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.141s

#44 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.142s

#45 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.142s

#46 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.142s

#47 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.143s

#48 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.143s

#49 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.143s

#50 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.143s

#51 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.143s

#52 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.144s

#53 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.144s

#54 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.144s

#55 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.144s

#56 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.144s

#57 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.145s

#58 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.145s

#59 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.145s

#60 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.145s

#61 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.145s

#62 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.145s

#63 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.146s

#64 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.146s

#65 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.146s

#66 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.146s

#67 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.146s

#68 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.146s

#69 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.147s

#70 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.148s

#71 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.148s

#72 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.148s

#73 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.149s

#74 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.15s

#75 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.151s

#76 linkCache_getLink using $NBC_LINKCACHE +0.009s ... 0.16s

#77 min, max, avg, median took s +0.007s ... 0.167s

#78 before gaming benchmark output +0s ... 0.167s

#79 Got 10 rows for game benchmarks. +0.007s ... 0.174s

#80 composed SQL query for gamebenchmarks +0s ... 0.174s

#81 got data and put it in $dataArray +0.001s ... 0.176s

#82 linkCache_getLink using $NBC_LINKCACHE +0.003s ... 0.178s

#83 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.18s

#84 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.18s

#85 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.18s

#86 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.18s

#87 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.18s

#88 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.18s

#89 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.182s

#90 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.184s

#91 linkCache_getLink using $NBC_LINKCACHE +0.002s ... 0.185s

#92 benchmarks composed for output. +0s ... 0.185s

#93 calculated avg scores. +0s ... 0.185s

#94 linkCache_getLink using $NBC_LINKCACHE +0.08s ... 0.265s

#95 return log +0.002s ... 0.268s

Teilen Sie diesen Artikel um uns zu unterstützen. Jeder Link hilft!
.170
> Notebook Test, Laptop Test und News > Benchmarks / Technik > Benchmarks / Technik > Grafikkarten Vergleich - Head 2 Head
Autor: Sebastian Jentsch,  8.09.2017 (Update: 19.05.2020)