Notebookcheck Logo

Qualcomm Snapdragon 400 8930AB vs Qualcomm Snapdragon S4 Pro MSM8960T

Qualcomm Snapdragon 400 8930AB

► remove from comparison Qualcomm 400 8930AB

Der Qualcomm Snapdragon 400 8930AB ist ein hoch getakteter ARM Dual-Core SoC für Android Smartphones. Er integriert zwei Krait 300 Kerne mit bis zu 1.7 GHz Taktfrequenz (MSM8930 hatte noch Krait 200 mit bis zu 1.2 GHz) und eine Adreno 305 Grafikkarte. Er wird im 28nm LP Verfahren gefertigt und bietet einen Single-channel-LPDDR2 Speicherkontroller (533 MHz).

Qualcomm Snapdragon S4 Pro MSM8960T

► remove from comparison Qualcomm MSM8960T

Der Qualcomm MSM8960T (Modellreihe Snapdragon S4 Pro) ist ein schneller ARM-SoC, der vorrangig in Smartphones eingesetzt wird. Er besitzt einen Krait-basierten Dual-Core-Prozessor sowie eine Adreno-320-Grafikeinheit. Weiterhin integriert sind ein LPDDR2-Speichercontroller (Dual-Channel, max. 500 MHz) sowie verschiedene Funkstandards inklusive LTE. Gefertigt wird der Chip von TSMC in einem 28-Nanometer-LP-Prozess.

Im Gegensatz zu älteren Qualcomm-SoCs, welche noch auf langsameren Scorpion-Kernen basierten, kommt im MSM8960T die moderne Krait-Architektur zum Einsatz. Diese ist deutlich schneller als die Cortex-A5-, Cortex-A7- und Cortex-A9-Architektur von ARM und liegt nur knapp hinter dem High-End-Design Cortex-A15. Beiden Kernen steht ein jeweils 32 KB großer L1-Cache sowie ein gemeinsamer L2-Cache mit 1 MB Kapazität zur Verfügung. Eine hohe Taktrate von bis zu 1,7 GHz sorgt in Verbindung mit der hohen Pro-MHz-Leistung dafür, dass die Performance noch über dem Niveau eines Quad-Core Cortex-A9 wie beispielsweise Nvidias Tegra 3 liegt. Auch die NEON-Befehlssatzerweiterung für bis zu 128 Bit breite Operanden wird unterstützt.

Die Adreno-320-Grafikeinheit kommt auch im Snapdragon 600 zum Einsatz und zählt Mitte 2013 zu den schnellsten Mobile-GPUs überhaupt. Der typischerweise mit 400 MHz taktende Chip besitzt genügend Reserven, um auch hochauflösende FullHD-Displays und aufwändige Spiele zu bewältigen.

Da der MSM8960T nur über zwei CPU-Kerne verfügt, sollte die Leistungsaufnahme etwas unterhalb von Quad-Core-SoCs wie dem Snapdragon 600 liegen. Der Chip kann deshalb auch in kleineren Smartphones mit schwächerem Akku eingesetzt werden können.

ModelQualcomm Snapdragon 400 8930ABQualcomm Snapdragon S4 Pro MSM8960T
SeriesQualcomm SnapdragonQualcomm Snapdragon
CodenameARMv7ARMv7
Serie: Snapdragon ARMv7
Qualcomm Snapdragon S4 Pro APQ8064A compare1.5 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM8928 compare1.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ8028 compare1.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Pro MSM8960T1.7 GHz2 / 2 ARMv7
» Qualcomm Snapdragon 400 8930AB1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus APQ8060A compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8960 compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8260A compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 MSM8926 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM8226 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ8026 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Plus MSM8930 compare1.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8230 compare1.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8227 compare1 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM8660 compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM8260 compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S1 QSD8250 compare1 GHz1 / 1 ARMv7
Qualcomm Snapdragon S4 Pro APQ8064A compare1.5 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM8928 compare1.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ8028 compare1.6 GHz4 / 4 ARMv7
» Qualcomm Snapdragon S4 Pro MSM8960T1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 8930AB1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus APQ8060A compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8960 compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8260A compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 MSM8926 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM8226 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ8026 compare1.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Plus MSM8930 compare1.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8230 compare1.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8227 compare1 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM8660 compare1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM8260 compare1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S1 QSD8250 compare1 GHz1 / 1 ARMv7
Clock1700 MHz1700 MHz
L1 Cache64 KB64 KB
L2 Cache1 MB1 MB
Cores / Threads2 / 22 / 2
Technology28 nm28 nm
FeaturesHSPA+, EDGE, GSM, GPRS, GPS, WiFi, Bluetooth, NFC, FMLTE, HSPA+, EDGE, GSM, GPRS, GPS, WiFi, Bluetooth, NFC, FM
iGPUQualcomm Adreno 305Qualcomm Adreno 320 (400 MHz)
ArchitectureARMARM
Announced

Benchmarks

3DMark - 3DMark Ice Storm Physics
min: 5181     avg: 6302     median: 6860 (4%)     max: 6864 Points
7305 Points (5%)
3DMark - 3DMark Ice Storm Extreme Physics
min: 5397     avg: 6193     median: 6192.5 (5%)     max: 6988 Points
min: 7074     avg: 7129     median: 7129 (6%)     max: 7184 Points
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
min: 963     avg: 1098     median: 1098 (2%)     max: 1233 Points
Geekbench 3 - Geekbench 3 32 Bit Single-Core
min: 531     avg: 584     median: 583.5 (11%)     max: 636 Points
Geekbench 2 - 32 Bit - Geekbench Stream
min: 593     avg: 680     median: 716 (6%)     max: 731 Points
min: 632     avg: 668     median: 668 (5%)     max: 704 Points
Geekbench 2 - 32 Bit - Geekbench Memory
min: 1527     avg: 1894     median: 2034 (18%)     max: 2121 Points
min: 2453     avg: 2630     median: 2630 (24%)     max: 2807 Points
Geekbench 2 - 32 Bit - Geekbench Floating Point
min: 244     avg: 1983     median: 2853 (6%)     max: 2853 Points
min: 2057     avg: 2521     median: 2520.5 (5%)     max: 2984 Points
Geekbench 2 - 32 Bit - Geekbench Integer
min: 898     avg: 1113     median: 1211 (2%)     max: 1229 Points
min: 871     avg: 1068     median: 1068 (2%)     max: 1265 Points
Geekbench 2 - 32 Bit - Geekbench Total Score
min: 1394     avg: 1740     median: 1907 (5%)     max: 1919 Points
min: 1578     avg: 1848     median: 1848 (5%)     max: 2118 Points
Linpack Android / IOS - Linpack Multi Thread
min: 241.6     avg: 296     median: 298.5 (10%)     max: 347.8 MFLOPS
min: 225.8     avg: 246.4     median: 246.4 (8%)     max: 266.9 MFLOPS
Linpack Android / IOS - Linpack Single Thread
min: 153.8     avg: 172.7     median: 171.1 (17%)     max: 193.2 MFLOPS
min: 166     avg: 169.5     median: 169.5 (17%)     max: 172.9 MFLOPS
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
34416 ms (40%)
min: 10213     avg: 13835     median: 13834.5 (16%)     max: 17456 ms
Sunspider - Sunspider 1.0 Total Score *
min: 701     avg: 1047     median: 1117.5 (12%)     max: 1252 ms
min: 1159     avg: 1422     median: 1421.5 (16%)     max: 1684 ms
Sunspider - Sunspider 0.9.1 Total Score *
min: 723     avg: 955     median: 954.5 (9%)     max: 1186 ms
min: 1202     avg: 1329     median: 1250 (12%)     max: 1534 ms
Octane V2 - Octane V2 Total Score
0 Points (0%)
min: 1466     avg: 2018     median: 2018 (2%)     max: 2570 Points
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
6958 points (16%)
7510 points (17%)
AnTuTu v3 - AnTuTu v3 CPU
min: 4032     avg: 5115     median: 5644 (37%)     max: 5669 Points
5727 Points (37%)
AnTuTu v4 - AnTuTu v4 Total Score
17699 Points (41%)
AndEBench - AndEBench Java
min: 186     avg: 266     median: 266 (8%)     max: 346 Iter./s
min: 327     avg: 350     median: 350 (11%)     max: 373 Iter./s
AndEBench - AndEBench Native
min: 4389     avg: 4822     median: 4821.5 (16%)     max: 5254 Iter./s
min: 6665     avg: 6716     median: 6715.5 (22%)     max: 6766 Iter./s
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
min: 4329     avg: 6192     median: 7051 (1%)     max: 7195 Points
7065 Points (1%)

Average Benchmarks Qualcomm Snapdragon 400 8930AB → 100% n=17

Average Benchmarks Qualcomm Snapdragon S4 Pro MSM8960T → 107% n=17

- 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

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.17
log 10. 23:24:33

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

#1 checking url part for id 4455 +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 Sat, 06 Aug 2022 13:13:32 +0200 +0s ... 0s

#4 linkCache_getLink no uid found +0.003s ... 0.004s

#5 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.005s

#6 linkCache_getLink no uid found +0.005s ... 0.01s

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

#8 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

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

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

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

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

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

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

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

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

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

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

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

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

#21 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#22 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.01s

#23 composed specs +0s ... 0.01s

#24 did output specs +0s ... 0.01s

#25 getting avg benchmarks for device 4413 +0s ... 0.011s

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

#27 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.011s

#28 got single benchmarks 4413 +0.008s ... 0.019s

#29 getting avg benchmarks for device 4455 +0s ... 0.02s

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

#31 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.02s

#32 got single benchmarks 4455 +0.007s ... 0.028s

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

#34 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.029s

#35 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.029s

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

#37 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.03s

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

#39 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.03s

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

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

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

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

#44 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.031s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#69 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

#70 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

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

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

#73 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

#74 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.034s

#75 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.035s

#76 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.035s

#77 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#78 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#79 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#80 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#81 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#82 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

#83 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.036s

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

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

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

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

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

#89 No cached benchmark found, getting uncached values +0s ... 0.037s

#90 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#91 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.037s

#92 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#93 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#94 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.038s

#95 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#96 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.038s

#97 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#98 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#99 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#100 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.039s

#101 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#102 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#103 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#104 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#105 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#106 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#107 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#108 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#109 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.04s

#110 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#111 min, max, avg, median took s +0s ... 0.041s

#112 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.041s

#113 return log +0.004s ... 0.045s

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