Notebookcheck Logo

Intel Celeron M 540 vs Intel Celeron M 520 vs Intel Celeron M 530

Intel Celeron M 540

► remove from comparison

Der Celeron M 540 ist ein Einstiegsprozessor basierend auf den Merom-Kern mit 64 KB L1 Cache (32 KB Daten + 32 KB Instruktionen) und 1024 KB L2 Cache, der mit vollem Prozessortakt läuft. Er wird verbaut auf dem Sockel 479, AGTL+ mit 133 MHz (quadpumped 533 MHz).

Intel Celeron M 520

► remove from comparison

Basierend auf den Merom kern mit 64 KB L1 Cache (32 KB Daten + 32 KB Instruktionen) und 1024 KB L2 Cache, der mit vollem Prozessortakt läuft.

Verbaut auf Sockel 479, AGTL+ mit 133 MHz (quadpumped 533 MHz)

Intel Celeron M 530

► remove from comparison

Basierend auf den Merom kern mit 64 KB L1 Cache (32 KB Daten + 32 KB Instruktionen) und 1024 KB L2 Cache, der mit vollem Prozessortakt läuft.

Verbaut auf Sockel 479, AGTL+ mit 133 MHz (quadpumped 533 MHz)

show full text
ModelIntel Celeron M 540Intel Celeron M 520Intel Celeron M 530
SeriesIntel Celeron MIntel Celeron MIntel Celeron M
CodenameMeromMeromMerom
Serie: Celeron M Merom
Intel Celeron M 5702.26 GHz1 / 1
Intel Celeron M 5852.16 GHz1 / 1
Intel Celeron M 5602.13 GHz1 / 1
Intel Celeron M 5752 GHz1 / 1
Intel Celeron M 5502 GHz1 / 1
» Intel Celeron M 5401.86 GHz1 / 1
Intel Celeron M 5301.73 GHz1 / 1
Intel Celeron M 5201.6 GHz1 / 1
Intel Celeron M 5702.26 GHz1 / 1
Intel Celeron M 5852.16 GHz1 / 1
Intel Celeron M 5602.13 GHz1 / 1
Intel Celeron M 5752 GHz1 / 1
Intel Celeron M 5502 GHz1 / 1
Intel Celeron M 5401.86 GHz1 / 1
Intel Celeron M 5301.73 GHz1 / 1
» Intel Celeron M 5201.6 GHz1 / 1
Intel Celeron M 5702.26 GHz1 / 1
Intel Celeron M 5852.16 GHz1 / 1
Intel Celeron M 5602.13 GHz1 / 1
Intel Celeron M 5752 GHz1 / 1
Intel Celeron M 5502 GHz1 / 1
Intel Celeron M 5401.86 GHz1 / 1
» Intel Celeron M 5301.73 GHz1 / 1
Intel Celeron M 5201.6 GHz1 / 1
Clock1860 MHz1600 MHz1730 MHz
FSB533533533
L2 Cache1 MB1 MB1 MB
Cores / Threads1 / 11 / 11 / 1
TDP30 Watt30 Watt30 Watt
Technology65 nm65 nm65 nm
FeaturesMMX, SSE, SSE2, SSE3, SSSE3, Intel 64, XD-BitMMX, SSE, SSE2, SSE3, SSSE3, Intel 64, XD-BitMMX, SSE, SSE2, SSE3, SSSE3, Intel 64, XD-Bit
Architecturex86x86x86
Announced
ManufacturerIntel Celeron M 540Intel Celeron M 520Intel Celeron M 530

Benchmarks

Cinebench R10 - Cinebench R10 Rend. Single (32bit)
100%
1 540 +
1744 Points (16%)
93%
1 530 +
1615 Points (14%)
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
0 Points (0%)
wPrime 1.55 - wPrime 1.55 1024m *
100%
1 520 +
3639 s (14%)
wPrime 1.55 - wPrime 1.55 32m *
100%
1 520 +
112 s (59%)
3DMark 06 - CPU - 3DMark 06 - CPU
100%
1 540 +
min: 795     avg: 803     median: 802.5 (2%)     max: 810 Points
92%
1 530 +
739 Points (2%)
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
100%
540 +
33 s (7%)
99%
520 +
min: 39     avg: 39.2     median: 39.2 (8%)     max: 39.3 s
99%
530 +
38 s (8%)
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
100%
1 540 +
82 s (4%)
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
100%
1 520 +
2015 s (9%)
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
100%
1 520 +
7400 MIPS (4%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
100%
1 520 +
5078 MFLOPS (4%)
PCMark 05 - PCMark 05 - Standard
100%
1 540 +
2231 Points (14%)
87%
1 520 +
min: 1845     avg: 1942     median: 1942 (12%)     max: 2039 Points

Average Benchmarks Intel Celeron M 540 → 100% n=1

Average Benchmarks Intel Celeron M 520 → 99% n=1

Average Benchmarks Intel Celeron M 530 → 99% n=1

- 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

v1.17
log 16. 18:19:29

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

#1 checking url part for id 321 +0s ... 0s

#2 checking url part for id 320 +0s ... 0s

#3 not redirecting to Ajax server +0s ... 0s

#4 did not recreate cache, as it is less than 5 days old! Created at Tue, 16 Aug 2022 13:13:41 +0200 +0s ... 0s

#5 linkCache_getLink no uid found +0.002s ... 0.003s

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

#7 linkCache_getLink no uid found +0s ... 0.004s

#8 linkCache_getLink no uid found +0s ... 0.004s

#9 linkCache_getLink no uid found +0s ... 0.004s

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

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

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

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

#14 linkCache_getLink no uid found +0s ... 0.004s

#15 linkCache_getLink no uid found +0s ... 0.004s

#16 linkCache_getLink no uid found +0s ... 0.004s

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

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

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

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

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

#22 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.004s

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

#24 composed specs +0s ... 0.004s

#25 did output specs +0s ... 0.004s

#26 getting avg benchmarks for device 341 +0s ... 0.005s

#27 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.005s

#28 got single benchmarks 341 +0.01s ... 0.015s

#29 getting avg benchmarks for device 321 +0s ... 0.015s

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

#31 got single benchmarks 321 +0.01s ... 0.025s

#32 getting avg benchmarks for device 320 +0s ... 0.026s

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

#34 got single benchmarks 320 +0.007s ... 0.033s

#35 got avg benchmarks for devices +0s ... 0.033s

#36 linkCache_getLink no uid found +0.001s ... 0.033s

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

#38 No cached benchmark found, getting uncached values +0s ... 0.034s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#54 min, max, avg, median took s +0s ... 0.039s

#55 return log +0s ... 0.039s

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)