Notebookcheck Logo

Qualcomm Snapdragon S3 MSM8260 vs Qualcomm Snapdragon S1 QSD8250 vs Qualcomm Snapdragon 400 APQ8026

Qualcomm Snapdragon S3 MSM8260

► remove from comparison Qualcomm S3 MSM8260

Der Qualcomm Snapdragon S3 MSM8260 ist ein Einstiegs-SoC für Smartphones und Tablets. Er besitzt einen ARM-basierten Dual-Core-Prozessor und entstammt der ersten Generation der Snapdragon-Serie. Die CPU Kerne basieren auf der alten Scorpion Architektur (verbesserte Cortex-A8 Architektur). Weiters ist eine Adreno 220 Grafikkarte integriert.

Qualcomm Snapdragon S1 QSD8250

► remove from comparison

Der Qualcomm Snapdragon S1 QSD8250 war einer der ersten Snapdragon SoCs für Smartphones und Tablets. Er bietet einen Scorpion CPU Kern, eine Adreno 200 Grafikkarte und GSM / UMTS Funktionen.

Qualcomm Snapdragon 400 APQ8026

► remove from comparison Qualcomm 400 APQ8026

Der Qualcomm Snapdragon 400 APQ8026 ist ein preiswerter ARM-SoC für Android-Smartphones. Er integriert vier Cortex-A7-Kerne mit bis zu 1.2 GHz Taktfrequenz, eine 450 MHz schnelle Adreno 305 Grafikkarte sowie einen Single-Channel LPDDR2/3-1066 Speichercontroller.

Sowohl die Leistung des Prozessors auch die der Grafikeinheit ist nur im Einstiegssegment angesiedelt. Ähnlich hoch taktende Cortex-A7-Kerne bietet zum Beispiel auch der Mediatek MT6589, der allerdings eine etwas schwächere PowerVR-GPU integriert. Die Adreno 305 des MSM8226 besitzt für Multimedia-Zwecke und einfache Android-Spiele ausreichende Leistungsreserven, ist jedoch nicht für anspruchsvolle 3D-Grafiken und extrem hohe Auflösungen geeignet.

Neben Prozessor und Grafikkarte integriert der Chip auch Bluetooth 4.0. Desweiteren können Kameras mit einer Auflösung von bis zu 13 Megapixeln angebunden werden. Zu den unterstützten Video-Codecs zählen unter anderem H.264 und H.265 (nur Wiedergabe) bis zu einer Auflösung von 1080p.

Der APQ8026 wird in einem 28nm LP Prozess gefertigt und besitzt eine sehr niedrige Leistungsaufnahme, sodass auch ein Einsatz in kompakten Smartphones oder gar Smartwatches möglich ist.

ModelQualcomm Snapdragon S3 MSM8260Qualcomm Snapdragon S1 QSD8250Qualcomm Snapdragon 400 APQ8026
SeriesQualcomm SnapdragonQualcomm SnapdragonQualcomm Snapdragon
CodenameARMv7ARMv7ARMv7
Serie: Snapdragon ARMv7
Qualcomm Snapdragon S4 Pro APQ8064A1.5 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM89281.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ80281.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 APQ8060A1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM89601.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8260A1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 MSM89261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM82261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ80261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Plus MSM89301.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM82301.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM82271 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM86601.7 GHz2 / 2 ARMv7
» Qualcomm Snapdragon S3 MSM82601.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S1 QSD82501 GHz1 / 1 ARMv7
Qualcomm Snapdragon S4 Pro APQ8064A1.5 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM89281.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ80281.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 APQ8060A1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM89601.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8260A1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 MSM89261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM82261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ80261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Plus MSM89301.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM82301.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM82271 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM86601.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM82601.5 GHz2 / 2 ARMv7
» Qualcomm Snapdragon S1 QSD82501 GHz1 / 1 ARMv7
Qualcomm Snapdragon S4 Pro APQ8064A1.5 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM89281.6 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 APQ80281.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 APQ8060A1.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM89601.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM8260A1.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon 400 MSM89261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon 400 MSM82261.2 GHz4 / 4 ARMv7
» Qualcomm Snapdragon 400 APQ80261.2 GHz4 / 4 ARMv7
Qualcomm Snapdragon S4 Plus MSM89301.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM82301.2 GHz2 / 2 ARMv7
Qualcomm Snapdragon S4 Plus MSM82271 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM86601.7 GHz2 / 2 ARMv7
Qualcomm Snapdragon S3 MSM82601.5 GHz2 / 2 ARMv7
Qualcomm Snapdragon S1 QSD82501 GHz1 / 1 ARMv7
Clock1500 MHz1000 MHz1200 MHz
L1 Cache64 KB
L2 Cache1 MB
Cores / Threads2 / 21 / 14 / 4
Technology45 nm65 nm28 nm
FeaturesHSPA+, EDGE, GSM, GPRS, GPS, WiFi, Bluetooth, NFC, FMEmbedded 600MHz DSP (GSM, GPRS, EDGE, UMTS/WCDMA, HSDPA, HSUPA, MBMS baseband), Embedded Seventh-generation gpsOne GPS module, gpsOneXTRA AssistanceBluetooth 4.0
iGPUQualcomm Adreno 220Qualcomm Adreno 200Qualcomm Adreno 305 (450 MHz)
ArchitectureARMARMARM
Announced
ManufacturerQualcomm Snapdragon S1 QSD8250Qualcomm Snapdragon 400 APQ8026

Benchmarks

3DMark - 3DMark Ice Storm Physics
6749 Points (4%)
3DMark - 3DMark Ice Storm Extreme Physics
6667 Points (6%)
3DMark - 3DMark Ice Storm Unlimited Physics
7226 Points (6%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
1075 Points (2%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
327 Points (7%)
Geekbench 2 - 32 Bit - Geekbench Stream
385 Points (3%)
272 Points (2%)
Geekbench 2 - 32 Bit - Geekbench Memory
1034 Points (9%)
1192 Points (11%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
1230 Points (2%)
1803 Points (4%)
Geekbench 2 - 32 Bit - Geekbench Integer
912 Points (2%)
1093 Points (2%)
Geekbench 2 - 32 Bit - Geekbench Total Score
994 Points (3%)
1279 Points (3%)
Linpack Android / IOS - Linpack Multi Thread
76.5 MFLOPS (3%)
242.3 MFLOPS (8%)
Linpack Android / IOS - Linpack Single Thread
43.2 MFLOPS (4%)
85.2 MFLOPS (8%)
Mozilla Kraken 1.1 - Kraken 1.1 Total Score *
16134 ms (19%)
Sunspider - Sunspider 0.9.1 Total Score *
1888 ms (18%)
1157 ms (11%)
Sunspider - Sunspider 1.0 Total Score *
1137 ms (12%)
Octane V2 - Octane V2 Total Score
1810 Points (2%)
Vellamo 3.x - Vellamo 3.x Metal
755 Points (20%)
Vellamo 3.x - Vellamo 3.x Multicore Beta
1152 Points (26%)
Vellamo 3.x - Vellamo 3.x Browser
1546 Points (20%)
Quadrant Standard Edition 2.0 - Quadrant Standard 2.0 Total Score
8236 points (19%)
AnTuTu v3 - AnTuTu v3 CPU
3197 Points (21%)
AnTuTu v4 - AnTuTu v4 Total Score
17735 Points (41%)
AnTuTu v5 - AnTuTu v5 Total Score
17247 Points (17%)
AndEBench - AndEBench Java
308 Iter./s (9%)
AndEBench - AndEBench Native
6098 Iter./s (20%)
PassMark PerformanceTest Mobile V1 - PerformanceTest Mobile CPU Tests
6717 Points (1%)

Average Benchmarks Qualcomm Snapdragon S3 MSM8260 → NAN% n=

Average Benchmarks Qualcomm Snapdragon 400 APQ8026 → NAN% n=

- 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

v1.17
log 06. 03:09:16

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

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

#2 checking url part for id 6436 +0s ... 0s

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

#4 did not recreate cache, as it is less than 5 days old! Created at Sat, 02 Jul 2022 13:13:02 +0200 +0s ... 0s

#5 linkCache_getLink no uid found +0.004s ... 0.005s

#6 linkCache_getLink no uid found +0.003s ... 0.008s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#22 linkCache_getLink no uid found +0.003s ... 0.01s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#39 composed specs +0s ... 0.011s

#40 did output specs +0s ... 0.011s

#41 getting avg benchmarks for device 3760 +0s ... 0.011s

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

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

#44 got single benchmarks 3760 +0.006s ... 0.017s

#45 getting avg benchmarks for device 1218 +0s ... 0.017s

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

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

#48 linkCache_getLink no uid found +0.001s ... 0.019s

#49 got single benchmarks 1218 +0.006s ... 0.024s

#50 getting avg benchmarks for device 6436 +0s ... 0.025s

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

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

#53 got single benchmarks 6436 +0.01s ... 0.035s

#54 got avg benchmarks for devices +0s ... 0.035s

#55 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.036s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#77 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.043s

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

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

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

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

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

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

#84 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.046s

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

#86 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.048s

#87 min, max, avg, median took s +0s ... 0.048s

#88 return log +0s ... 0.048s

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: Redaktion,  8.09.2017 (Update: 19.05.2020)