Notebookcheck Logo

Intel Atom 330 vs Intel Atom N270

Intel Atom 330

► remove from comparison

Der Intel Atom 330 ist eine Dual Core CPU die für Nettops (kleine Desktops) gedacht ist. Daher unterstützt er auch deutlich weniger Stromsparfunktionen als die Einkern Atom Prozessoren für Netbooks (Atom N270, N280).

An Stromsparfunktionen unterstützt der Atom 330 nur den C1 State (N270 z.B. C1, C2, C4, Enhanced Stop Grant, Enhanced Deeper Sleep State, Enhanced Speedstep) und braucht daher ohne Last deutlich mehr als (zwei) Atom N270 brauchen würden. Unter Volllast ist die Leistungsaufnahme ziemlich genau mit zwei N270 vergleichbar.

Die Performance des Dual Core Atom 330 ist zwar deutlich oberhalb eines Atom N270, jedoch noch immer deutlich unterhalb der billgsten Celeron Dual Core oder Athlon Modelle. Die Performance reicht deshalb auch beim 330 nur für anspruchslose Aufgaben (Websurfen, Office, SD Videos z.B.). In Verbindung mit einem ION Chipsatz (wie z.B. im Asus Eee PC Netbook) können einige anspruchslose Spiele und mit der richtigen Software auch HD Videos flüssig dargestellt werden (siehe dazu unseren Testbericht).

Der direkte Nachfolger der Atom 330 CPU ist die Atom D510 mit integriertem Speicherkontroller und GMA 3150 Grafikkarte (wieder nur für Desktops gedacht).

Intel Atom N270

► remove from comparison Intel N270

Der Intel Atom N270 ist eine typische "Netbook" Single Core (1-Kern) CPU von Intel und wird mit 1.6 GHz getaktet. Der Atom Kern wurde auf geringen Stromverbrauch und geringe Herstellungskosten optimiert.

Dadurch ist die Performance des N270 relativ gering und reicht nur für anspruchslose Aufgaben wie Websurfen, Email oder Office Aufgaben. Ohne Unterstützung der Grafikkarte, überfordern den Atom N270 z.B. bereits HD Videos oder mehrere parallel laufende Anwendungen. Die Performance pro Megaherzt ist im Vergleich zu anderen Single Core Prozessoren (Celeron M, Core 2 Solo) sehr gering, da der Atom auf eine in-order Ausführung setzt (er sortiert die Befehle nicht automatisch für die bessere Auslastung). Dieser Nachteil wird aber teilweise durch das integrierte Hyper-Threading wieder vermindert (die CPU gibt sich hierbei als 2 Kern CPU aus um die Aufgaben besser einteilen zu können). Die Performance des 1.6 GHz schnellen N270 ist daher vergleichbar mit einem 1.2 GHz schnellen Celeron M.

Dank der Fertigung im (für 2009) modernen 45nm Verfahren und der geringen Baugröße, bleibt der Stromverbrauch sehr geringt (max. 2.5 Watt TDP). Dadurch eignet sich der N270 für sehr kleine und mobile Notebooks / Netbooks und benötigt keine aufwändige Kühlung.

Der N270 besitzt keinerlei Virtualisierungsfunktionen und auch keinen 64 Bit Support.

Package: 437-Ball-µFCBGA, 22 mm × 22 mm

ModelIntel Atom 330Intel Atom N270
SeriesIntel AtomIntel Atom
CodenameDiamondvilleDiamondVille
Serie: Atom DiamondVille
» Intel Atom 3301.6 GHz2 / 4
Intel Atom N280 compare1.66 GHz1 / 2
Intel Atom N2701.6 GHz1 / 2
Intel Atom 3301.6 GHz2 / 4
Intel Atom N280 compare1.66 GHz1 / 2
» Intel Atom N2701.6 GHz1 / 2
Clock1600 MHz1600 MHz
FSB533533
L2 Cache1 MB512 KB
Cores / Threads2 / 41 / 2
TDP8 Watt2.5 Watt
Transistors94 Million47 Million
45 nm0.9V-1.1625V45 nm0.9-1.1625 V
Die Size52 mm226 mm2
max. Temp.85.2 °C90 °C
SocketPBGA437PBGA437
FeaturesExecute Disable Bit, Hyper-Threading, Intel 64MMX, SSE, SSE2, SSE3, SSSE3, HHT, Execute Disable Bit, Enhanced Speedstep, Hyper-Threading
Architecturex86x86
$43 U.S.$44 U.S.
Announced
ManufacturerIntel Atom 330Intel Atom N270
L1 Cache56 KB

Benchmarks

Cinebench R10 - Cinebench R10 Rend. Single (32bit)
100%
330 +
min: 535     avg: 541     median: 542 (5%)     max: 545 Points
100%
N270 +
min: 483     avg: 538     median: 541 (5%)     max: 577 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
100%
330 +
min: 1516     avg: 1528     median: 1530 (2%)     max: 1537 Points
min: 482     avg: 818     median: 830 (1%)     max: 888 Points
wPrime 2.10 - wPrime 2.0 1024m *
100%
330 +
min: 2008     avg: 3735     median: 3735 (44%)     max: 5462 s
min: 3673     avg: 4705     median: 4742 (56%)     max: 5662 s
wPrime 2.10 - wPrime 2.0 32m *
100%
330 +
min: 62     avg: 116.5     median: 116.5 (23%)     max: 170.9 s
min: 116     avg: 143.3     median: 126 (25%)     max: 177.8 s
3DMark 06 - CPU - 3DMark 06 - CPU
100%
330 +
min: 820     avg: 825     median: 824.5 (2%)     max: 829 Points
min: 461     avg: 478.8     median: 483 (1%)     max: 492 Points
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
100%
330 +
min: 92     avg: 97.5     median: 97.5 (21%)     max: 103 s
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
100%
330 +
209 s (9%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
100%
330 +
min: 4522     avg: 4575     median: 4574.5 (20%)     max: 4627 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
100%
330 +
8030 MIPS (4%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
100%
330 +
6720 MFLOPS (5%)
Windows 7 Experience Index - Win7 CPU
100%
330 +
3.3 Points (42%)
2.3 Points (29%)

Average Benchmarks Intel Atom 330 → 100% n=11

Average Benchmarks Intel Atom N270 → 78% n=11

- 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 03. 16:26:09

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

#1 checking url part for id 413 +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, 02 Jul 2022 13:13:02 +0200 +0s ... 0s

#4 linkCache_getLink no uid found +0.001s ... 0.002s

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

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

#7 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.006s

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

#9 composed specs +0s ... 0.006s

#10 did output specs +0s ... 0.006s

#11 getting avg benchmarks for device 526 +0s ... 0.007s

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

#13 got single benchmarks 526 +0.007s ... 0.014s

#14 getting avg benchmarks for device 413 +0.001s ... 0.014s

#15 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.016s

#16 got single benchmarks 413 +0.05s ... 0.066s

#17 got avg benchmarks for devices +0s ... 0.066s

#18 linkCache_getLink no uid found +0s ... 0.066s

#19 linkCache_getLink no uid found +0s ... 0.066s

#20 linkCache_getLink no uid found +0.001s ... 0.067s

#21 linkCache_getLink no uid found +0s ... 0.067s

#22 linkCache_getLink no uid found +0s ... 0.067s

#23 linkCache_getLink no uid found +0s ... 0.067s

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

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

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

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

#28 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.069s

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

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

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

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

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

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

#35 linkCache_getLink no uid found +0s ... 0.069s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#60 linkCache_getLink no uid found +0s ... 0.07s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#79 linkCache_getLink no uid found +0s ... 0.072s

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

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

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

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

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

#85 linkCache_getLink no uid found +0s ... 0.072s

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

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

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

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

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

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

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

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

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

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

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

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

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

#99 linkCache_getLink no uid found +0s ... 0.073s

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

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

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

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

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

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

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

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

#108 linkCache_getLink no uid found +0s ... 0.074s

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

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

#111 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.074s

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

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

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

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

#116 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.074s

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

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

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

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

#121 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.075s

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

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

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

#125 linkCache_getLink no uid found +0s ... 0.075s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#150 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.077s

#151 min, max, avg, median took s +0s ... 0.077s

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

#153 return log +0.004s ... 0.081s

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)