Notebookcheck Logo

Intel Pentium Dual Core T4500 vs Intel Pentium Dual Core T4300 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 T4300

► remove from comparison Intel T4300

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

Der Intel Pentium T4300 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. Dadurch läuft die CPU ohne Last nur mit 800 MHz.

Der Pentium T4300 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 T4300Intel Pentium Dual Core SU4100
SeriesIntel Pentium Dual CoreIntel Pentium Dual CoreIntel Pentium Dual Core
CodenamePenrynPenrynPenryn
Serie: Pentium Dual Core Penryn
» Intel Pentium Dual Core T45002.3 GHz2 / 2
Intel Pentium Dual Core T44002.2 GHz2 / 2
Intel Pentium Dual Core T43002.1 GHz2 / 2
Intel Pentium Dual Core T42002 GHz2 / 2
Intel Pentium Dual Core SU41001.3 GHz2 / 2
Intel Pentium Dual Core T45002.3 GHz2 / 2
Intel Pentium Dual Core T44002.2 GHz2 / 2
» Intel Pentium Dual Core T43002.1 GHz2 / 2
Intel Pentium Dual Core T42002 GHz2 / 2
Intel Pentium Dual Core SU41001.3 GHz2 / 2
Intel Pentium Dual Core T45002.3 GHz2 / 2
Intel Pentium Dual Core T44002.2 GHz2 / 2
Intel Pentium Dual Core T43002.1 GHz2 / 2
Intel Pentium Dual Core T42002 GHz2 / 2
» Intel Pentium Dual Core SU41001.3 GHz2 / 2
Clock2300 MHz2100 MHz1300 MHz
FSB800800800
L1 Cache128 KB128 KB
L2 Cache1 MB1 MB2 MB
Cores / Threads2 / 22 / 22 / 2
TDP35 Watt35 Watt10 Watt
Transistors410 Million410 Million410 Million
Technology45 nm1.05-1.15V45 nm1.05-1.15V45 nm
Die Size107 mm2107 mm2107 mm2
SocketPGA478PGA478BGA956
FeaturesMMX, SSE, SSE2, SSE3, SSSE3, Enhanced Intel SpeedStep Technology (EIST), Intel 64, XD bit, iAMT2 (Intel Active Management), TXTMMX, SSE, SSE2, SSE3, SSSE3, Enhanced Intel SpeedStep Technology (EIST), Intel 64, XD bit, iAMT2 (Intel Active Management), TXTIntel64, Enhanced Speedstep, ExBit
Architecturex86x86x86
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
min: 2153     avg: 2243     median: 2242 (20%)     max: 2335 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 4283     avg: 4366     median: 4337 (6%)     max: 4490 Points
min: 3963     avg: 4148     median: 4057 (6%)     max: 4425 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
min: 4458     avg: 4594     median: 4578 (4%)     max: 4747 Points
4415 Points (4%)
2881 Points (3%)
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
min: 2388     avg: 2447     median: 2416 (15%)     max: 2538 Points
2040 Points (12%)
1542 Points (9%)
wPrime 2.10 - wPrime 2.0 1024m *
min: 1137     avg: 1142     median: 1137 (13%)     max: 1152 s
1252 s (15%)
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
39 s (8%)
3DMark 06 - CPU - 3DMark 06 - CPU
min: 1887     avg: 1920     median: 1898 (4%)     max: 1995 Points
min: 1692     avg: 1798     median: 1825 (4%)     max: 1848 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
min: 22     avg: 25.3     median: 26 (6%)     max: 28 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
min: 54     avg: 62.3     median: 64 (3%)     max: 69 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
1502 s (7%)
min: 1341     avg: 1469     median: 1528 (7%)     max: 1539 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
21100 MIPS (10%)
min: 17767     avg: 18550     median: 18550 (9%)     max: 19333 MIPS
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
15460 MFLOPS (12%)
min: 13927     avg: 14231     median: 14231 (11%)     max: 14535 MFLOPS
PCMark 05 - PCMark 05 - Standard
100%
1 T4500 +
min: 3747     avg: 3865     median: 3865 (24%)     max: 3983 Points
85%
1 SU4100 +
min: 3108     avg: 3274     median: 3274 (21%)     max: 3440 Points
Windows 7 Experience Index - Win7 CPU
5.8 Points (74%)
min: 5.3     avg: 5.4     median: 5.4 (69%)     max: 5.4 Points
min: 3.9     avg: 4     median: 4 (51%)     max: 4 Points
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
100%
1 T4300 +
min: 3590     avg: 3788     median: 3787.5 (4%)     max: 3985 Points

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

Average Benchmarks Intel Pentium Dual Core T4300 → 95% n=13

Average Benchmarks Intel Pentium Dual Core SU4100 → 72% n=13

- 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 05. 12:30:25

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

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

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

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

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

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

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

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

#10 linkCache_getLink no uid found +0s ... 0.007s

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

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

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

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

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

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

#17 getting avg benchmarks for device 593 +0s ... 0.007s

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

#19 got single benchmarks 593 +0.015s ... 0.022s

#20 getting avg benchmarks for device 490 +0s ... 0.023s

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

#22 got single benchmarks 490 +0.014s ... 0.037s

#23 getting avg benchmarks for device 504 +0s ... 0.037s

#24 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.038s

#25 got single benchmarks 504 +0.019s ... 0.056s

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

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

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

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

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

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

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

#33 linkCache_getLink no uid found +0.001s ... 0.058s

#34 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.059s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#51 linkCache_getLink no uid found +0.001s ... 0.06s

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

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

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

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

#56 linkCache_getLink no uid found +0s ... 0.061s

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

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

#59 linkCache_getLink no uid found +0s ... 0.062s

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

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

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

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

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

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

#66 linkCache_getLink no uid found +0s ... 0.063s

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

#68 linkCache_getLink no uid found +0s ... 0.063s

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

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

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

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

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

#74 linkCache_getLink no uid found +0s ... 0.064s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#124 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.07s

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

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

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

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

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

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

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

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

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

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

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

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

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

#138 min, max, avg, median took s +0s ... 0.071s

#139 return log +0s ... 0.071s

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)