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

Intel Pentium Dual Core T4500 vs Intel Pentium Dual Core SU4100

Intel Pentium Dual Core T4500

► remove from comparison Intel T4500

Der Intel Pentium T4500 (oder Pentium Dual Core T4500) ist ein Einstiegs-Mittelklasse Doppelkernprozessor von Intel. Im Vergleich zu den Core 2 Duo Prozessoren, hat der Pentium T4500 nur 1 MB Level 2 Cache (Core 2 Duo 2-6 MB) und bietet weniger Stromsparfunktionen (abgeschaltet).

Der Intel Pentium T4500 unterstützt z.B. folgende Stromspartechnologien NICHT:

  • Intel® Virtualization Technology
  • Intel® Dynamic Acceleration
  • Intel® Dynamic FSB Frequency Switching
  • C3E
  • Deeper Sleep State (C4)
  • Intel® Enhanced Deeper Sleep State

Dadurch sollte der Stromverbrauch ohne Last etwas höher sein, als bei vergleichbaren Core 2 Duo CPUs. Auch die Virtualisierungsfunktionen (VT-x) sind wie bei den günstigen Core 2 Duo nicht aktiviert. 

Durch die mittelmäßige Taktfrequenz und den kleinen Level 2 Cache, kann die CPU bei modernen und anspruchsvollen Spielen durchaus limitieren (z.B. große Multiplayerschlachten bei Supreme Commander). Für die mittelmäßig anspruchsvolle (nicht professionelle) Anwendungen wie Office, SD Videoschnitt, Bildbearbeitung, Internet und casual Gaming sollte die Leistung jedoch ausreichen.

Der Penryn (Montevina Update) Kern bietet 2 Integer Units, 1 Floating Point Unit, 1 Load Unit und 1 Store Unit in einer 14-stufigen Pipeline. Mit der Wide Dynamic Execution Technologie kann der Kern bis zu vier volle Instruktionen gleichzeitig ausführen.

Das integrierte Enhanced Speedstep kann die Taktfrequenz des Prozessors dynamisch an die Leistungsanforderungen anpassen. 

Der Core 2 Duo T4500 passt in den Socket P (PGA478)

Intel Pentium Dual Core SU4100

► remove from comparison

Der Intel Pentium SU4100 ist ein Einstiegs-Doppelkernprozessor für kleine und leichte Notebooks (CULV Prozessor). Durch die Pentium Serie, bietet er wahrscheinlich weniger Stromsparmechanismen als die Core 2 Duo auf Penryn Basis. Durch die geringe Taktrate, ist der SU4100 nur für anspruchslose Aufgaben geeignet.

ModelIntel Pentium Dual Core T4500Intel Pentium Dual Core SU4100
SeriesIntel Pentium Dual CoreIntel Pentium Dual Core
CodenamePenrynPenryn
Serie: Pentium Dual Core Penryn
» Intel Pentium Dual Core T45002.3 GHz2 / 2
Intel Pentium Dual Core T4400 compare2.2 GHz2 / 2
Intel Pentium Dual Core T4300 compare2.1 GHz2 / 2
Intel Pentium Dual Core T4200 compare2 GHz2 / 2
Intel Pentium Dual Core SU41001.3 GHz2 / 2
Intel Pentium Dual Core T45002.3 GHz2 / 2
Intel Pentium Dual Core T4400 compare2.2 GHz2 / 2
Intel Pentium Dual Core T4300 compare2.1 GHz2 / 2
Intel Pentium Dual Core T4200 compare2 GHz2 / 2
» Intel Pentium Dual Core SU41001.3 GHz2 / 2
Clock2300 MHz1300 MHz
FSB800800
L1 Cache128 KB
L2 Cache1 MB2 MB
Cores / Threads2 / 22 / 2
TDP35 Watt10 Watt
Transistors410 Million410 Million
Technology45 nm1.05-1.15V45 nm
Die Size107 mm2107 mm2
SocketPGA478BGA956
FeaturesMMX, SSE, SSE2, SSE3, SSSE3, Enhanced Intel SpeedStep Technology (EIST), Intel 64, XD bit, iAMT2 (Intel Active Management), TXTIntel64, Enhanced Speedstep, ExBit
Architecturex86x86
Announced
ManufacturerIntel Pentium Dual Core T4500Intel Pentium Dual Core SU4100
max. Temp.100 °C

Benchmarks

Cinebench R11.5 - Cinebench R11.5 CPU Multi 64 Bit
100%
1 T4500 +
1.3 Points (2%)
Cinebench R10 - Cinebench R10 Rend. Single (32bit)
min: 2234     avg: 2315     median: 2331 (21%)     max: 2367 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 4283     avg: 4366     median: 4337 (6%)     max: 4490 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
min: 4458     avg: 4594     median: 4578 (4%)     max: 4747 Points
2881 Points (3%)
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
min: 2388     avg: 2447     median: 2416 (15%)     max: 2538 Points
1542 Points (9%)
wPrime 2.10 - wPrime 2.0 1024m *
min: 1137     avg: 1142     median: 1137 (13%)     max: 1152 s
min: 1986     avg: 3179     median: 3754 (44%)     max: 3796 s
wPrime 2.10 - wPrime 2.0 32m *
min: 35.7     avg: 35.9     median: 35.7 (7%)     max: 36.2 s
3DMark 06 - CPU - 3DMark 06 - CPU
min: 1887     avg: 1920     median: 1898 (4%)     max: 1995 Points
min: 1110     avg: 1158     median: 1168.5 (2%)     max: 1183 Points
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
min: 25     avg: 25.6     median: 25.6 (6%)     max: 26.2 s
Super Pi mod 1.5 XS 2M - Super Pi mod 1.5 XS 2M *
min: 62     avg: 62.9     median: 62.9 (3%)     max: 63.8 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
1502 s (7%)
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
21100 MIPS (10%)
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
15460 MFLOPS (12%)
PCMark 05 - PCMark 05 - Standard
min: 3747     avg: 3865     median: 3865 (24%)     max: 3983 Points
min: 3108     avg: 3274     median: 3274 (21%)     max: 3440 Points
Windows 7 Experience Index - Win7 CPU
5.8 Points (74%)
min: 3.9     avg: 4     median: 4 (51%)     max: 4 Points

Average Benchmarks Intel Pentium Dual Core T4500 → 100% n=14

Average Benchmarks Intel Pentium Dual Core SU4100 → 73% n=14

- 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. 16:44:30

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

#1 checking url part for id 504 +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 +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 +0s ... 0.005s

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

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

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

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

#11 composed specs +0s ... 0.005s

#12 did output specs +0s ... 0.005s

#13 getting avg benchmarks for device 593 +0s ... 0.005s

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

#15 got single benchmarks 593 +0.014s ... 0.02s

#16 getting avg benchmarks for device 504 +0s ... 0.02s

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

#18 got single benchmarks 504 +0.019s ... 0.04s

#19 got avg benchmarks for devices +0s ... 0.04s

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

#21 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.041s

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

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

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

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

#26 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.042s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#54 linkCache_getLink no uid found +0s ... 0.045s

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

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

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

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

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

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

#61 linkCache_getLink no uid found +0s ... 0.046s

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

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

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

#65 linkCache_getLink no uid found +0s ... 0.046s

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

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

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

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

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

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

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

#73 linkCache_getLink no uid found +0s ... 0.047s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#88 linkCache_getLink no uid found +0s ... 0.049s

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

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

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

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

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

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

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

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

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

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

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

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

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

#102 min, max, avg, median took s +0s ... 0.051s

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

#104 return log +0.004s ... 0.055s

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)