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

AMD E-350 vs AMD E-240

AMD E-350

► remove from comparison

Der AMD E-350 (Codename Zacate) ist ein Dual-Core Prozessor mit integrierter Grafikkarte und Speichercontroller (Single Channel DDR3-1066) für kleine Notebooks und Netbooks. Er ist gedacht als direkte Konkurrenz zu den Intel Atom Prozessoren (z.B. Atom N550).

Die beiden Bobcat Kerne bieten jeweils 512 KB Level 2 Cache und im Gegensatz zu derzeitigen Atom Cores "out-of-order" Ausführung. Dadurch ist die CPU bei gleicher Taktfrequenz schneller als ein Pinetrail Atom (z.B. als der etwas langsamer getaktete Atom N550 Dual Core). Die Leistung reicht jedoch nicht an gleichgetaktete Penryn Celerons oder Danube Athlons heran. Im Schnitt ist der E-350 z.B. etwas langsamer als ein Celeron SU2300 mit 1.2 GHz bzw. Athlon II Neo K325 mit 1.3 GHz. 

Eine Besonderheit ist die integrierte Radeon HD 6310 Grafikkarte, welche dank 80 Shader und UVD3 Video Prozessor deutlich leistungsstärker ist als die Intel GMA 3150 in Atom Prozessoren. Die (Mobility) Radeon HD 6310 sollte in etwas das Niveau einer ION Grafik erreichen.

Der Stromverbrauch liegt mit einer TDP von 18 Watt deutlich über Atom und auf dem Niveau von Sandy Bridge ULV-Prozessoren (17 Watt). Die verbaute Grafikkarte im E350 ist jedoch auch deutlich leistungsfähiger. Erste Strommessungen einer Brazos Prototypen Plattform zeigen Stromverbrauchswerte von 11-29 Watt und dadurch im Bereich eines MacBook Air 11" unter Windows 7 (welches jedoch deutlich leistungsfähiger ist).

AMD E-240

► remove from comparison

Der AMD E-240 (Codename Zacate) ist ein Einzelkern-Prozessor mit integrierter Grafikkarte und Speicherkontroller (Single Channel DDR3-1066) für kleine Notebooks und Netbooks. Er ist gedacht als direkte Konkurrenz zu den Intel Atom Prozessoren (z.B. Atom N475).

Der E-240 basiert auf den E-350 Doppelkernprozessor, jedoch mit nur einem aktivierten Kern. Dieser Bobcat Kern bietet 512KB Level 2 Cache und im Gegensatz zu derzeitigen Atom Cores "out-of-order" Ausführung. Dadurch ist die CPU bei gleicher MHz und Taktfrequenz schneller als ein Pinetrail Atom (z.B. als der Atom N455). Die Leistung reicht jedoch nicht an gleichgetaktete Penryn Celerons Einzelkern oder AMD V-Series Prozessoren.  

Eine Besonderheit ist die integrierte Radeon HD 6310 Grafikkarte, welche dank 80 Shader und UVD3 Video Prozessor deutlich leistungsstärker ist als die Intel GMA 3150 in Atom Prozessoren. Die (Mobility) Radeon HD6310 sollte in etwas das Niveau einer ION Grafik erreichen.

Der Stromverbrauch ist mit einem TDP von 18 Watt deutlich über Atom und Arrandale ULV Prozessoren eingeordnet. Die verbaute Grafikkarte im E240 ist jedoch auch deutlich leistungsfähiger.

ModelAMD E-350AMD E-240
SeriesAMD E-SeriesAMD E-Series
CodenameZacateZacate
Serie: E-Series Zacate
AMD E2-2000 compare1.75 GHz2 / 2
AMD E2-1800 compare1.7 GHz2 / 2
AMD E-450 compare1.65 GHz2 / 2
» AMD E-3501.6 GHz2 / 2
AMD E1-1500 compare1.48 GHz2 / 2
AMD E1-1200 compare1.4 GHz2 / 2
AMD E-300 compare1.3 GHz2 / 2
AMD E-2401.5 GHz1 / 1
AMD E2-2000 compare1.75 GHz2 / 2
AMD E2-1800 compare1.7 GHz2 / 2
AMD E-450 compare1.65 GHz2 / 2
AMD E-3501.6 GHz2 / 2
AMD E1-1500 compare1.48 GHz2 / 2
AMD E1-1200 compare1.4 GHz2 / 2
AMD E-300 compare1.3 GHz2 / 2
» AMD E-2401.5 GHz1 / 1
Clock1600 MHz1500 MHz
L1 Cache128 KB64 KB
L2 Cache1 MB512 KB
Cores / Threads2 / 21 / 1
TDP18 Watt18 Watt
Technology40 nm40 nm
Die Size75 mm275 mm2
SocketFT1 BGA 413-BallFT1 BGA 413-Ball
FeaturesMMX(+), SSE(1,2,3,3S,4A), AMD-VMMX(+), SSE(1,2,3,3S,4A), AMD-V
iGPUAMD Radeon HD 6310
Architecturex86x86
Announced

Benchmarks

Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
min: 0.59     avg: 0.6     median: 0.6 (1%)     max: 0.62 Points
0.3 Points (0%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
min: 1029     avg: 1048     median: 1048.5 (9%)     max: 1064 Points
min: 891     avg: 938     median: 937.5 (8%)     max: 984 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
100%
1 E-350 +
min: 1887     avg: 1997     median: 2005 (3%)     max: 2080 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
100%
1 E-350 +
min: 2034     avg: 2182     median: 2195.5 (2%)     max: 2250 Points
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
min: 1122     avg: 1140     median: 1140 (7%)     max: 1158 Points
min: 988     avg: 1016     median: 1015.5 (6%)     max: 1043 Points
wPrime 2.10 - wPrime 2.0 1024m *
min: 2054     avg: 2130     median: 2093 (25%)     max: 2257 s
4472 s (53%)
wPrime 2.10 - wPrime 2.0 32m *
min: 64     avg: 68.7     median: 68.8 (14%)     max: 72.1 s
137.4 s (28%)
3DMark 06 - CPU - 3DMark 06 - CPU
min: 985     avg: 1016     median: 1021 (2%)     max: 1033 Points
min: 497     avg: 501     median: 500.5 (1%)     max: 504 Points
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
min: 49     avg: 51.2     median: 50 (11%)     max: 61 s
57.5 s (12%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
min: 109     avg: 111.6     median: 112 (5%)     max: 115 s
120.3 s (5%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
100%
1 E-350 +
min: 2410     avg: 2466     median: 2460 (11%)     max: 2539 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
min: 9290     avg: 9647     median: 9790 (5%)     max: 9860 MIPS
min: 3750     avg: 4097     median: 4270 (2%)     max: 4270 MIPS
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
min: 7490     avg: 7520     median: 7530 (6%)     max: 7540 MFLOPS
min: 3520     avg: 3730     median: 3520 (3%)     max: 4150 MFLOPS
Windows 7 Experience Index - Win7 CPU
min: 3.7     avg: 3.8     median: 3.8 (49%)     max: 3.8 Points
2.5 Points (32%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
100%
1 E-350 +
min: 1818     avg: 1933     median: 1982 (2%)     max: 1998 Points
3DMark 11 - 3DM11 Performance Physics
min: 605     avg: 638     median: 609 (2%)     max: 690 Points
269 Points (1%)

Average Benchmarks AMD E-350 → 100% n=12

Average Benchmarks AMD E-240 → 68% n=12

- 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 22. 17:13:49

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

#1 checking url part for id 1511 +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 +0.001s ... 0.001s

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

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

#6 linkCache_getLink no uid found +0.001s ... 0.009s

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

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

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

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

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

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

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

#14 composed specs +0s ... 0.009s

#15 did output specs +0s ... 0.009s

#16 getting avg benchmarks for device 1509 +0s ... 0.009s

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

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

#19 got single benchmarks 1509 +0.032s ... 0.041s

#20 getting avg benchmarks for device 1511 +0s ... 0.042s

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

#22 got single benchmarks 1511 +0.007s ... 0.05s

#23 got avg benchmarks for devices +0s ... 0.05s

#24 linkCache_getLink no uid found +0s ... 0.05s

#25 linkCache_getLink no uid found +0s ... 0.05s

#26 linkCache_getLink no uid found +0s ... 0.05s

#27 linkCache_getLink no uid found +0s ... 0.05s

#28 linkCache_getLink no uid found +0s ... 0.05s

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

#30 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.051s

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

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

#33 linkCache_getLink no uid found +0s ... 0.051s

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

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

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

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

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

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

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

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

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

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

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

#45 linkCache_getLink no uid found +0s ... 0.052s

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

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

#48 linkCache_getLink no uid found +0s ... 0.052s

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

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

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

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

#53 linkCache_getLink no uid found +0s ... 0.053s

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

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

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

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

#58 linkCache_getLink no uid found +0s ... 0.053s

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

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

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

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

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

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

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

#66 linkCache_getLink no uid found +0s ... 0.053s

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

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

#69 linkCache_getLink no uid found +0s ... 0.053s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#89 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.054s

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

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

#92 linkCache_getLink no uid found +0s ... 0.054s

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

#94 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.055s

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

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

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

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

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

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

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

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

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

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

#105 linkCache_getLink no uid found +0s ... 0.055s

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

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

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

#109 linkCache_getLink no uid found +0s ... 0.056s

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

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

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

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

#114 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#115 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

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

#117 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#118 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.056s

#119 linkCache_getLink no uid found +0s ... 0.057s

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

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

#122 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#123 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#124 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

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

#126 linkCache_getLink no uid found +0s ... 0.057s

#127 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#128 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.057s

#129 linkCache_getLink no uid found +0s ... 0.057s

#130 linkCache_getLink no uid found +0s ... 0.058s

#131 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#132 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#133 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#134 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#135 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#136 linkCache_getLink no uid found +0s ... 0.058s

#137 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#138 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#139 linkCache_getLink no uid found +0s ... 0.058s

#140 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#141 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.058s

#142 linkCache_getLink no uid found +0s ... 0.058s

#143 linkCache_getLink no uid found +0s ... 0.058s

#144 linkCache_getLink no uid found +0s ... 0.059s

#145 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#146 linkCache_getLink no uid found +0s ... 0.059s

#147 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#148 linkCache_getLink no uid found +0s ... 0.059s

#149 linkCache_getLink no uid found +0s ... 0.059s

#150 linkCache_getLink no uid found +0s ... 0.059s

#151 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#152 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#153 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#154 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#155 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#156 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.059s

#157 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#158 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#159 linkCache_getLink no uid found +0s ... 0.06s

#160 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#161 linkCache_getLink no uid found +0s ... 0.06s

#162 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#163 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#164 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#165 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#166 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#167 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.06s

#168 linkCache_getLink no uid found +0s ... 0.06s

#169 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.061s

#170 min, max, avg, median took s +0s ... 0.061s

#171 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.061s

#172 return log +0.004s ... 0.065s

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)