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

Intel Celeron 1000M vs Intel Celeron 1017U

Intel Celeron 1000M

► remove from comparison

Der Intel Celeron 1000M ist ein Doppelkernprozessor aus dem Einstiegssegment. Er taktet mit 1,8 GHz und basiert auf der Ivy Bridge Architektur. Im Vergleich zu den Core-i3-, i5- und i7-Prozessoren sind jedoch die meisten Features deaktiviert (Turbo Boost, AES, HyperThreading). Die integrierte Grafikkarte basiert auf der HD Graphics 2500, wird jedoch von Intel nur HD Graphics genannt und mit 650 bzw. 1000 MHz (Turbo Boost) getaktet. Ausserdem ist ein DDR3-1600-Speicherkontroller in dem Prozessor integriert.

Die Performance liegt dank der verbesserten Architektur etwas oberhalb einer ähnlich getakteten Sandy-Bridge-CPU und somit knapp unter dem Level eines Intel Pentium B940.

Die Ivy Bridge Prozessoren beinhalten in der angegebenen TDP auch die Grafikkarte und den Speicherkontroller. Mit 35 Watt TDP eignet sich der Prozessor für Notebooks ab etwa 13 Zoll.

Intel Celeron 1017U

► remove from comparison

Der Intel Celeron 1017U ist ein sparsamer Doppelkernprozessor aus dem Einstiegssegment. Er taktet mit 1,6 GHz und basiert auf der Ivy Bridge Architektur. Im Vergleich zu den Core-i3-, i5- und i7-Prozessoren sind jedoch die meisten Features deaktiviert (Turbo Boost, AES, HyperThreading). Die integrierte Grafikkarte basiert auf der HD Graphics 2500, wird jedoch von Intel nur HD Graphics genannt und mit 350 bzw. 1000 MHz (Turbo Boost) getaktet. Ausserdem ist ein DDR3-1600-Speicherkontroller in dem Prozessor integriert.

Die Performance liegt dank der verbesserten Architektur etwas oberhalb einer ähnlich getakteten Sandy-Bridge-CPU und etwa auf dem Level eines Intel Celeron B820.

Die Ivy Bridge Prozessoren beinhalten in der angegebenen TDP auch die Grafikkarte und den Speicherkontroller. Mit 17 Watt TDP eignet sich der Prozessor für kleine Notebooks und Subnotebooks.

ModelIntel Celeron 1000MIntel Celeron 1017U
SeriesIntel CeleronIntel Celeron
CodenameIvy BridgeIvy Bridge
Serie: Celeron Ivy Bridge
Intel Celeron 1020E compare2.2 GHz2 / 22 MB
Intel Celeron 1020M compare2.1 GHz2 / 22 MB
Intel Celeron 1005M compare1.9 GHz2 / 22 MB
» Intel Celeron 1000M1.8 GHz2 / 22 MB
Intel Celeron 1037U compare1.8 GHz2 / 22 MB
Intel Celeron 1017U1.6 GHz2 / 22 MB
Intel Celeron 1007U compare1.5 GHz2 / 22 MB
Intel Celeron 1047UE compare1.4 GHz2 / 22 MB
Intel Celeron 1019Y compare1 GHz2 / 22 MB
Intel Celeron 927UE compare1.5 GHz1 / 11 MB
Intel Celeron 1020E compare2.2 GHz2 / 22 MB
Intel Celeron 1020M compare2.1 GHz2 / 22 MB
Intel Celeron 1005M compare1.9 GHz2 / 22 MB
Intel Celeron 1000M1.8 GHz2 / 22 MB
Intel Celeron 1037U compare1.8 GHz2 / 22 MB
» Intel Celeron 1017U1.6 GHz2 / 22 MB
Intel Celeron 1007U compare1.5 GHz2 / 22 MB
Intel Celeron 1047UE compare1.4 GHz2 / 22 MB
Intel Celeron 1019Y compare1 GHz2 / 22 MB
Intel Celeron 927UE compare1.5 GHz1 / 11 MB
Clock1800 MHz1600 MHz
L1 Cache128 KB128 KB
L2 Cache512 KB512 KB
L3 Cache2 MB2 MB
Cores / Threads2 / 22 / 2
TDP35 Watt17 Watt
Technology22 nm22 nm
Die Size94 mm294 mm2
max. Temp.105 °C105 °C
SocketrPGA988BFCBGA1023
FeaturesHD Graphics (650 - 1000 MHz), DDR3 Memory Controller, Enhanced Speedstep, Thermal Monitoring, Execute Disable BitHD Graphics (350 - 1000 MHz), DDR3 Memory Controller, Enhanced Speedstep, Thermal Monitoring, Execute Disable Bit
iGPUIntel HD Graphics (Ivy Bridge) (650 - 1000 MHz)Intel HD Graphics (Ivy Bridge) (350 - 1000 MHz)
Architecturex86x86
$86 U.S.
Announced
ManufacturerIntel Celeron 1000MIntel Celeron 1017U

Benchmarks

Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
1.5 Points (3%)
1.3 Points (2%)
Cinebench R11.5 - Cinebench R11.5 CPU Single 64 Bit
0.7 Points (21%)
0.6 Points (17%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
2480 Points (22%)
2201 Points (20%)
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
4757 Points (6%)
4155 Points (6%)
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
6023 Points (5%)
5280 Points (5%)
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
3151 Points (19%)
2797 Points (17%)
wPrime 2.10 - wPrime 2.0 1024m *
1314 s (16%)
1449 s (17%)
wPrime 2.10 - wPrime 2.0 32m *
41.6 s (8%)
46.4 s (9%)
WinRAR - WinRAR 4.0
1285 Points (7%)
1150 Points (7%)
X264 HD Benchmark 4.0 - x264 Pass 2
8.5 fps (4%)
7.6 fps (3%)
X264 HD Benchmark 4.0 - x264 Pass 1
47.2 fps (13%)
41.9 fps (11%)
TrueCrypt - TrueCrypt Serpent
0.1 GB/s (3%)
0.1 GB/s (2%)
TrueCrypt - TrueCrypt Twofish
0.1 GB/s (2%)
0.1 GB/s (2%)
TrueCrypt - TrueCrypt AES
0.2 GB/s (1%)
0.1 GB/s (1%)
3DMark 06 - CPU - 3DMark 06 - CPU
1923 Points (4%)
1719 Points (4%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
21.3 s (5%)
24.3 s (5%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
47.1 s (2%)
53.5 s (2%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
1076 s (5%)
1219 s (5%)
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
22230 MIPS (11%)
19720 MIPS (9%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
13410 MFLOPS (10%)
11800 MFLOPS (9%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
4757 Points (5%)
4130 Points (4%)
3DMark 11 - 3DM11 Performance Physics
1779 Points (6%)
1532 Points (5%)
3DMark - 3DMark Ice Storm Physics
13537 Points (9%)
11797 Points (8%)
3DMark - 3DMark Cloud Gate Physics
1214 Points (3%)
1041 Points (3%)
3DMark - 3DMark Fire Strike Standard Physics
100%
1 1000M +
1648 Points (4%)
Geekbench 2 - 32 Bit - Geekbench Stream
4938 Points (40%)
3985 Points (32%)
Geekbench 2 - 32 Bit - Geekbench Memory
4298 Points (39%)
3500 Points (32%)
Geekbench 2 - 32 Bit - Geekbench Floating Point
3016 Points (6%)
2631 Points (5%)
Geekbench 2 - 32 Bit - Geekbench Integer
2848 Points (6%)
2494 Points (5%)
Geekbench 2 - 32 Bit - Geekbench Total Score
3405 Points (9%)
2892 Points (8%)
Geekbench 3 - Geekbench 3 32 Bit Multi-Core
100%
1 1017U +
2308 Points (4%)
Geekbench 3 - Geekbench 3 32 Bit Single-Core
100%
1 1017U +
1367 Points (28%)

Average Benchmarks Intel Celeron 1000M → 100% n=29

Average Benchmarks Intel Celeron 1017U → 89% n=29

- 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 23. 17:28:44

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

#1 checking url part for id 3947 +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 Mon, 23 May 2022 13:12:29 +0200 +0.001s ... 0.001s

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

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

#6 linkCache_getLink no uid found +0.002s ... 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 composed specs +0s ... 0.008s

#18 did output specs +0s ... 0.008s

#19 getting avg benchmarks for device 3717 +0s ... 0.008s

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

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

#22 got single benchmarks 3717 +0.009s ... 0.017s

#23 getting avg benchmarks for device 3947 +0s ... 0.018s

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

#25 got single benchmarks 3947 +0.006s ... 0.024s

#26 got avg benchmarks for devices +0s ... 0.024s

#27 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.025s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#46 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.033s

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

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

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

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

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

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

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

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

#55 linkCache_getLink using $NBC_LINKCACHE +0s ... 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 +0s ... 0.038s

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

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

#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.042s

#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.043s

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

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

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

#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.044s

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

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

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

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

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

#86 min, max, avg, median took s +0s ... 0.046s

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

#88 return log +0.004s ... 0.05s

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)