Notebookcheck Logo
, , , , , ,
zu verknüpfen.
, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
 

AMD A4-3330MX vs AMD A6-3400M

AMD A4-3330MX

► remove from comparison AMD A4-3330MX

Der AMD A4-3330MX (Codename Llano) ist ein Dual-Core Prozessor (bzw. APU = Accelerated Processing Unit) der Fusion Familie mit integrierter Radeon HD 6480G Grafikkarte für Notebooks. Er taktet je nach Kernlast und Temperatur mit 2.2 - 2.6 GHz (2.6 GHz bei Belastung eines Kerns) und positioniert sich im Einstiegssegment. Im Vergleich zum A4-3310MX bietet der 3330MX einen um je 100 MHz höheren Grund- sowie Turbotakt.

Der Prozessorteil basiert auf der Husky Familie 12h, welche bis auf den zusätzlichen Hardware-Divider den Rechenkernen der älteren mobilen Phenom II (Familie 10h, K10 Kerne) entspricht. Wie diese bieten die Llano CPUs keinen Level 3 Cache. Vergleichbar mit den mobilen Champlain Prozessoren Turion II und Phenom II X2 verfügt jeder Kern über 1 MB Level 2 Cache.

Die maximale Rechenleistung (dank TurboCore 2.0 mit bis zu 2.6 GHz) eines einzelnen Kerns ist daher z.B. vergleichbar mit einem AMD Turion II N550 (2.6 GHz   2 MB L2 Cache). Wenn beide Kerne ausgelastet werden, sinkt die Taktrate auf bis zu 2.2 GHz herunter. Damit sollte die Rechenleistung auf dem Niveau eines 2.3 GHz getakteten AMD Athlon II P360 sein.

Wie bei den aktuellen Core-i Prozessoren ist in der A-Serie ebenfalls eine Grafikkarte integriert. Die AMD Radeon HD 6480G bietet 240 Rechenkerne (der 400 im Chip), welche mit 444 MHz getaktet sind und auf keinen dedizierten Grafikspeicher zugreifen. Dank des integrierten UVD 3 Video Prozessors ist der A4-3330MX auch in der Lage, die meisten HD Videoformate (H.264, VC-1, MPEG4) voll zu dekodieren.

Mit 45 Watt TDP (inklusive DDR3(L)-1333 Speichercontroller und Grafikkarte) eignet sich der A4-3330MX am besten für 15"+ Notebooks.

AMD A6-3400M

► remove from comparison AMD A6-3400M

Der AMD A6-3400M (Codename Llano) ist ein Quad-Core Prozessor (bzw. APU = Accelerated Processing Unit) der Fusion Familie mit integrierter Radeon HD 6520G Grafikkarte für Notebooks. Er taktet je nach Kernlast und Temperatur mit 1.4 - 2.3 GHz (2.3 GHz bei Belastung eines Kerns) und positioniert sich im Einstiegssegment.

Der Prozessorteil basiert auf der Husky Familie 12h, welche bis auf den zusätzlichen Hardware-Divider den Rechenkernen der älteren mobilen Phenom II (Familie 10h, K10 Kerne) entspricht. Wie diese bieten die Llano CPUs keinen Level 3 Cache. Vergleichbar mit den mobilen Champlain Prozessoren Turion II und Phenom II X2 verfügt jeder Kern über 1 MB Level 2 Cache. 

Die maximale Rechenleistung (dank TurboCore 2.0 mit bis zu 2.3 GHz) eines einzelnen Kerns ist daher z.B. vergleichbar mit einem AMD Turion II P520 (2.3 GHz 2 MB L2 Cache). Wenn mehrere Kerne ausgelastet werden, sinkt die Taktrate auf bis zu 1.4 GHz herunter. Dadurch sollte die Mehrkernperformance in etwa mit einem Phenom II X4 P920 (1.6 GHz 2MB L2 Cache) bzw X3 P840 (1.9 GHz 1.5 MB L2 Cache) vergleichbar sein. Damit sollte sich die Rechenleistung auf dem Niveau eines noch auf dem Penryn Kern basierenden Pentium T4500 bewegen. Ein erster Benchmark von tweakers.net bescheinigt dem A6-3400M eine SuperPi Single-Kern Performance des Phenom II X4 N950 (36.6 s versus 36.8 s des Phenom II).

Wie bei den aktuellen Core-i Prozessoren ist in der A6 Serie ebenfalls eine Grafikkarte integriert. Die AMD Radeon HD 6520G bietet 320 Rechenkerne (der 400 im Chip), welche mit 400 MHz getaktet sind und auf keinen dedizierten Grafikspeicher zugreifen. Dank des integrierten UVD 3 Video Prozessors ist der A6-3400M auch in der Lage, die meisten HD Videoformate (H.264, VC-1, MPEG4) voll zu dekodieren.

Mit 35 Watt TDP (inklusive DDR3(L)-1333 Speichercontroller und Grafikkarte) eignet sich der A6-3400M am besten für 14-15" Notebooks.

Quellen: NGOHQ: Leaked Llano PresentationDonanimhaber: Llano Mobile Lineupc't: 12h Architekturtweakers: SuperPiAMD: geleakte GPU Benchmarks (bereits entfernt)pro-clockers: Llano GPU Spezifikationen

ModelAMD A4-3330MXAMD A6-3400M
SeriesAMD A-SeriesAMD A-Series
CodenameLlanoLlano
Serie: A-Series Llano
AMD A8-3550MX compare2 - 2.7 GHz4 / 4
AMD A8-3530MX compare1.9 - 2.6 GHz4 / 4
AMD A8-3510MX compare1.8 - 2.5 GHz4 / 4
AMD A6-3430MX compare1.7 - 2.4 GHz4 / 4
AMD A8-3520M compare1.6 - 2.5 GHz4 / 4
AMD A6-3410MX compare1.6 - 2.3 GHz4 / 4
AMD A8-3500M compare1.5 - 2.4 GHz4 / 4
AMD A6-3420M compare1.5 - 2.4 GHz4 / 4
AMD A6-3400M1.4 - 2.3 GHz4 / 4
» AMD A4-3330MX2.2 - 2.6 GHz2 / 2
AMD A4-3310MX compare2.1 - 2.5 GHz2 / 2
AMD A4-3320M compare2 - 2.6 GHz2 / 2
AMD A4-3300M compare1.9 - 2.5 GHz2 / 2
AMD A4-3305M compare1.9 - 2.5 GHz2 / 2
AMD A8-3550MX compare2 - 2.7 GHz4 / 4
AMD A8-3530MX compare1.9 - 2.6 GHz4 / 4
AMD A8-3510MX compare1.8 - 2.5 GHz4 / 4
AMD A6-3430MX compare1.7 - 2.4 GHz4 / 4
AMD A8-3520M compare1.6 - 2.5 GHz4 / 4
AMD A6-3410MX compare1.6 - 2.3 GHz4 / 4
AMD A8-3500M compare1.5 - 2.4 GHz4 / 4
AMD A6-3420M compare1.5 - 2.4 GHz4 / 4
» AMD A6-3400M1.4 - 2.3 GHz4 / 4
AMD A4-3330MX2.2 - 2.6 GHz2 / 2
AMD A4-3310MX compare2.1 - 2.5 GHz2 / 2
AMD A4-3320M compare2 - 2.6 GHz2 / 2
AMD A4-3300M compare1.9 - 2.5 GHz2 / 2
AMD A4-3305M compare1.9 - 2.5 GHz2 / 2
Clock2200 - 2600 MHz1400 - 2300 MHz
L1 Cache256 KB
L2 Cache2 MB4 MB
Cores / Threads2 / 24 / 4
TDP45 Watt35 Watt
Transistors1000 Million1000 Million
Technology32 nm32 nm
Die Size226 mm2218 mm2
Features3DNow!, MMX, SSE, SSE2, SSE3, SSE4a, DDR3 Memory Controller, Radeon HD 6480G3DNow!, MMX, SSE, SSE2, SSE3, SSE4a, Radeon HD 6480G, DDR3(L)-1333 Memory Controller
iGPUAMD Radeon HD 6480G (444 MHz)AMD Radeon HD 6520G (400 MHz)
Architecturex86x86
Announced
ManufacturerAMD A-Series A4-3330MX

Benchmarks

Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
min: 1.77     avg: 1.8     median: 1.8 (3%)     max: 1.79 Points
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
min: 1456     avg: 1497     median: 1512 (14%)     max: 1529 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 4823     avg: 4909     median: 4922 (7%)     max: 4962 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
min: 6284     avg: 6390     median: 6363 (6%)     max: 6496 Points
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
min: 1871     avg: 1930     median: 1950 (12%)     max: 1961 Points
wPrime 2.10 - wPrime 2.0 1024m *
min: 782     avg: 807     median: 792 (9%)     max: 864 s
wPrime 2.10 - wPrime 2.0 32m *
min: 24.7     avg: 26.1     median: 26 (5%)     max: 27.55 s
3DMark 06 - CPU - 3DMark 06 - CPU
min: 2120     avg: 2137     median: 2135 (5%)     max: 2152 Points
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
min: 33     avg: 37.6     median: 37 (8%)     max: 48.44 s
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
min: 73.8     avg: 90.9     median: 84 (4%)     max: 120 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
min: 1831     avg: 1922     median: 1944 (9%)     max: 1946 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
21200 MIPS (10%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
min: 17590     avg: 17730     median: 17730 (14%)     max: 17870 MFLOPS
Windows 7 Experience Index - Win7 CPU
min: 6.5     avg: 6.6     median: 6.6 (84%)     max: 6.6 Points
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
min: 4842     avg: 5050     median: 5086 (5%)     max: 5171 Points
3DMark 11 - 3DM11 Performance Physics
min: 2046     avg: 2095     median: 2092 (7%)     max: 2167 Points

Average Benchmarks AMD A6-3400M → 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

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 20. 13:00:38

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

#1 checking url part for id 2695 +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 Wed, 18 May 2022 13:12:25 +0200 +0s ... 0s

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

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

#6 linkCache_getLink no uid found +0.006s ... 0.013s

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

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

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

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

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

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

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

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

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

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

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

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

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

#20 composed specs +0s ... 0.013s

#21 did output specs +0s ... 0.013s

#22 getting avg benchmarks for device 3033 +0s ... 0.014s

#23 got single benchmarks 3033 +0s ... 0.014s

#24 getting avg benchmarks for device 2695 +0s ... 0.014s

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

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

#27 got single benchmarks 2695 +0.02s ... 0.035s

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

#29 linkCache_getLink no uid found +0s ... 0.035s

#30 linkCache_getLink no uid found +0s ... 0.035s

#31 linkCache_getLink no uid found +0.001s ... 0.035s

#32 linkCache_getLink no uid found +0s ... 0.035s

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

#34 linkCache_getLink no uid found +0s ... 0.035s

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

#36 linkCache_getLink no uid found +0s ... 0.035s

#37 linkCache_getLink no uid found +0s ... 0.035s

#38 linkCache_getLink no uid found +0s ... 0.035s

#39 linkCache_getLink no uid found +0s ... 0.035s

#40 linkCache_getLink no uid found +0s ... 0.036s

#41 linkCache_getLink no uid found +0s ... 0.036s

#42 linkCache_getLink no uid found +0s ... 0.036s

#43 linkCache_getLink no uid found +0s ... 0.036s

#44 linkCache_getLink no uid found +0s ... 0.036s

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

#46 linkCache_getLink no uid found +0s ... 0.036s

#47 linkCache_getLink no uid found +0s ... 0.036s

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

#49 linkCache_getLink no uid found +0s ... 0.036s

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

#51 linkCache_getLink no uid found +0s ... 0.036s

#52 linkCache_getLink no uid found +0s ... 0.036s

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

#54 linkCache_getLink no uid found +0s ... 0.036s

#55 linkCache_getLink no uid found +0s ... 0.036s

#56 linkCache_getLink no uid found +0s ... 0.037s

#57 linkCache_getLink no uid found +0s ... 0.037s

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

#59 linkCache_getLink no uid found +0s ... 0.037s

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

#61 linkCache_getLink no uid found +0s ... 0.037s

#62 linkCache_getLink no uid found +0s ... 0.037s

#63 linkCache_getLink no uid found +0s ... 0.037s

#64 linkCache_getLink no uid found +0s ... 0.037s

#65 linkCache_getLink no uid found +0s ... 0.037s

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

#67 linkCache_getLink no uid found +0s ... 0.037s

#68 linkCache_getLink no uid found +0s ... 0.037s

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

#70 linkCache_getLink no uid found +0s ... 0.038s

#71 linkCache_getLink no uid found +0s ... 0.038s

#72 linkCache_getLink no uid found +0s ... 0.038s

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

#74 linkCache_getLink no uid found +0s ... 0.038s

#75 linkCache_getLink no uid found +0s ... 0.038s

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

#77 linkCache_getLink no uid found +0s ... 0.038s

#78 linkCache_getLink no uid found +0s ... 0.038s

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

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

#81 linkCache_getLink no uid found +0s ... 0.038s

#82 linkCache_getLink no uid found +0s ... 0.038s

#83 linkCache_getLink no uid found +0s ... 0.038s

#84 linkCache_getLink no uid found +0s ... 0.038s

#85 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.039s

#86 linkCache_getLink no uid found +0s ... 0.039s

#87 linkCache_getLink no uid found +0s ... 0.039s

#88 linkCache_getLink no uid found +0s ... 0.039s

#89 linkCache_getLink no uid found +0s ... 0.039s

#90 linkCache_getLink no uid found +0s ... 0.039s

#91 linkCache_getLink no uid found +0s ... 0.039s

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

#93 linkCache_getLink no uid found +0s ... 0.039s

#94 linkCache_getLink no uid found +0s ... 0.039s

#95 linkCache_getLink no uid found +0s ... 0.039s

#96 linkCache_getLink no uid found +0s ... 0.039s

#97 linkCache_getLink no uid found +0s ... 0.039s

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

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

#100 linkCache_getLink no uid found +0s ... 0.04s

#101 linkCache_getLink no uid found +0s ... 0.04s

#102 linkCache_getLink no uid found +0s ... 0.04s

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

#104 linkCache_getLink no uid found +0s ... 0.04s

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

#106 linkCache_getLink no uid found +0s ... 0.04s

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

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

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

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

#111 linkCache_getLink no uid found +0s ... 0.041s

#112 linkCache_getLink no uid found +0s ... 0.041s

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

#114 linkCache_getLink no uid found +0s ... 0.041s

#115 linkCache_getLink no uid found +0s ... 0.041s

#116 linkCache_getLink no uid found +0s ... 0.041s

#117 linkCache_getLink no uid found +0s ... 0.042s

#118 linkCache_getLink no uid found +0s ... 0.042s

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

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

#121 linkCache_getLink no uid found +0s ... 0.042s

#122 linkCache_getLink no uid found +0s ... 0.042s

#123 linkCache_getLink no uid found +0s ... 0.042s

#124 min, max, avg, median took s +0s ... 0.042s

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

#126 return log +0.004s ... 0.046s

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)