Notebookcheck Logo

Intel Atom N280 vs Intel Atom N270

Intel Atom N280

► remove from comparison Intel N280

Der Intel Atom N280 ist eine typische "Netbook" Single Core CPU von Intel und wird mit 1.66 GHz getaktet. Im Vergleich zum gängigen N270 wurde der Frontsidebus etwas höher getaktet (effektiv 667 MHz versus 533 MHz) und auch die Prozessortaktrate minimal erhöht (von 1.6 auf 1.66 GHz).

Der Atom Kern wurde auf geringen Stromverbrauch und geringe Herstellungskosten optimiert. Dadurch ist die Performance des N280 relativ gering und reicht nur für anspruchslose Aufgaben wie Websurfen, Email oder Office Aufgaben. Ohne Unterstützung der Grafikkarte, überfordern den Atom N280 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 N280 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 N280 besitzt keinerlei Virtualisierungsfunktionen und auch keinen 64 Bit Support.

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

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 N280Intel Atom N270
SeriesIntel AtomIntel Atom
CodenameDiamondVilleDiamondVille
Serie: Atom DiamondVille
Intel Atom 330 compare1.6 GHz2 / 4
» Intel Atom N2801.66 GHz1 / 2
Intel Atom N2701.6 GHz1 / 2
Intel Atom 330 compare1.6 GHz2 / 4
Intel Atom N2801.66 GHz1 / 2
» Intel Atom N2701.6 GHz1 / 2
Clock1660 MHz1600 MHz
FSB667533
L1 Cache56 KB56 KB
L2 Cache512 KB512 KB
Cores / Threads1 / 21 / 2
TDP2.5 Watt2.5 Watt
Transistors47 Million47 Million
45 nm, 0.9-1.1625 V45 nm, 0.9-1.1625 V
Die Size26 mm226 mm2
max. Temp.90 °C90 °C
SocketPBGA437PBGA437
FeaturesMMX, SSE, SSE2, SSE3, SSSE3, HHT, Execute Disable Bit, Enhanced Speedstep, Hyper-ThreadingMMX, SSE, SSE2, SSE3, SSSE3, HHT, Execute Disable Bit, Enhanced Speedstep, Hyper-Threading
Architecturex86x86
Announced
ManufacturerIntel Atom N280Intel Atom N270
$44 U.S.

Benchmarks

Cinebench R10 - Cinebench R10 Rend. Single (32bit)
100%
N280 +
min: 541     avg: 564     median: 567 (5%)     max: 585 Points
min: 483     avg: 538     median: 541 (5%)     max: 577 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
100%
N280 +
min: 835     avg: 868     median: 877 (1%)     max: 892 Points
min: 482     avg: 818     median: 830 (1%)     max: 888 Points
wPrime 2.10 - wPrime 2.0 1024m *
100%
N280 +
3635 s (43%)
min: 3673     avg: 4705     median: 4742 (56%)     max: 5662 s
wPrime 2.10 - wPrime 2.0 32m *
100%
N280 +
min: 114     avg: 115     median: 115 (23%)     max: 116 s
min: 116     avg: 143.3     median: 126 (25%)     max: 177.8 s
3DMark 06 - CPU - 3DMark 06 - CPU
100%
N280 +
min: 487     avg: 502     median: 507 (1%)     max: 513 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%
N280 +
min: 87     avg: 88.3     median: 89 (19%)     max: 89 s
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
100%
N280 +
min: 192     avg: 194     median: 194 (8%)     max: 196 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
100%
N280 +
min: 4292     avg: 4302     median: 4301 (19%)     max: 4313 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
100%
N280 +
min: 4128     avg: 4155     median: 4156 (2%)     max: 4180 MIPS
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
100%
N280 +
min: 3426     avg: 3458     median: 3455 (3%)     max: 3494 MFLOPS
PCMark 05 - PCMark 05 - Standard
100%
N280 +
min: 1282     avg: 1541     median: 1501.5 (9%)     max: 1864 Points
Windows 7 Experience Index - Win7 CPU
100%
1 N270 +
2.3 Points (29%)

Average Benchmarks Intel Atom N280 → 100% n=11

Average Benchmarks Intel Atom N270 → 95% 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.18
log 30. 13:49:00

#0 checking url part for id 461 +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 Fri, 30 Sep 2022 13:14:19 +0200 +0s ... 0s

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

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

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

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

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

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

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

#11 getting avg benchmarks for device 461 +0s ... 0.008s

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

#13 got single benchmarks 461 +0.024s ... 0.032s

#14 getting avg benchmarks for device 413 +0s ... 0.033s

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

#16 got single benchmarks 413 +0.054s ... 0.088s

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

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

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

#20 linkCache_getLink no uid found +0s ... 0.088s

#21 linkCache_getLink no uid found +0.001s ... 0.089s

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

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

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

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

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

#27 linkCache_getLink no uid found +0.001s ... 0.09s

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

#29 linkCache_getLink no uid found +0.001s ... 0.091s

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

#31 linkCache_getLink no uid found +0s ... 0.091s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#76 linkCache_getLink no uid found +0s ... 0.093s

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

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

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

#80 linkCache_getLink no uid found +0s ... 0.094s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#98 linkCache_getLink no uid found +0s ... 0.095s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#147 linkCache_getLink no uid found +0s ... 0.099s

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

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

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

#151 linkCache_getLink no uid found +0s ... 0.099s

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

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

#154 linkCache_getLink no uid found +0s ... 0.099s

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

#156 linkCache_getLink no uid found +0s ... 0.099s

#157 linkCache_getLink no uid found +0s ... 0.099s

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

#159 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.099s

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

#161 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.099s

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

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

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

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

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

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

#168 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.1s

#169 min, max, avg, median took s +0s ... 0.1s

#170 linkCache_getLink using $NBC_LINKCACHE +0.023s ... 0.123s

#171 return log +0.004s ... 0.127s

Teilen Sie diesen Artikel um uns zu unterstützen. Jeder Link hilft!
.170
> 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)