Notebookcheck Logo

Intel Pentium Dual Core T4500 vs Intel Pentium Dual Core T4200 vs Intel Pentium Dual Core T4400

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 T4200

► remove from comparison

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

 

Der Intel Pentium T4200 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 Pentium T4200 passt in den Socket P (PGA478)

Intel Pentium Dual Core T4400

► remove from comparison Intel T4400

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

Der Intel Pentium T4400 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 Core 2 Duo T4400 passt in den Socket P (PGA478)

ModelIntel Pentium Dual Core T4500Intel Pentium Dual Core T4200Intel Pentium Dual Core T4400
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 MHz2000 MHz2200 MHz
FSB800800800
L1 Cache128 KB128 KB128 KB
L2 Cache1 MB1 MB1 MB
Cores / Threads2 / 22 / 22 / 2
TDP35 Watt35 Watt35 Watt
Transistors410 Million410 Million410 Million
45 nm, 1.05-1.15V45 nm45 nm, 1.05-1.15V
Die Size107 mm2107 mm2107 mm2
SocketPGA478PG478PGA478
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), TXTMMX, SSE, SSE2, SSE3, SSSE3, Enhanced Intel SpeedStep Technology (EIST), Intel 64, XD bit, iAMT2 (Intel Active Management), TXT
Architecturex86x86x86
Announced
ManufacturerIntel Pentium Dual Core T4500Intel Pentium Dual Core T4400
max. Temp.105 °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: 2200     avg: 2231     median: 2231 (20%)     max: 2262 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 4283     avg: 4366     median: 4337 (6%)     max: 4490 Points
min: 4191     avg: 4227     median: 4200 (6%)     max: 4289 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
100%
1 T4500 +
min: 4458     avg: 4594     median: 4578 (4%)     max: 4747 Points
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
100%
1 T4500 +
min: 2388     avg: 2447     median: 2416 (15%)     max: 2538 Points
wPrime 2.10 - wPrime 2.0 1024m *
min: 1137     avg: 1142     median: 1137 (13%)     max: 1152 s
min: 1236     avg: 1643     median: 1242 (15%)     max: 2451 s
1203 s (14%)
wPrime 2.10 - wPrime 2.0 32m *
min: 35.7     avg: 35.9     median: 35.7 (7%)     max: 36.2 s
min: 39     avg: 51.4     median: 39.3 (8%)     max: 76 s
38.2 s (8%)
3DMark 06 - CPU - 3DMark 06 - CPU
min: 1887     avg: 1920     median: 1898 (4%)     max: 1995 Points
min: 1578     avg: 1660     median: 1636 (3%)     max: 1784 Points
min: 1850     avg: 1890     median: 1897 (4%)     max: 1915 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: 26.4     avg: 26.6     median: 26.6 (6%)     max: 26.8 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: 61     avg: 61.1     median: 61.1 (3%)     max: 61.1 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
1502 s (7%)
1489 s (7%)
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
21100 MIPS (10%)
min: 18119     avg: 18259     median: 18259 (9%)     max: 18399 MIPS
min: 18500     avg: 19350     median: 19350 (9%)     max: 20200 MIPS
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
15460 MFLOPS (12%)
min: 14415     avg: 14562     median: 14561.5 (11%)     max: 14708 MFLOPS
15800 MFLOPS (12%)
PCMark 05 - PCMark 05 - Standard
100%
1 T4500 +
min: 3747     avg: 3865     median: 3865 (24%)     max: 3983 Points
106%
1 T4200 +
min: 3910     avg: 4188     median: 4110.5 (26%)     max: 4756 Points
Windows Vista Experience Index - Windows Vista Leistungsindex - Prozessor
100%
1 T4200 +
min: 4.9     avg: 5     median: 5 (71%)     max: 5.1 Points
Windows 7 Experience Index - Win7 CPU
100%
1 T4500 +
5.8 Points (74%)
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
100%
1 T4200 +
3434 Points (4%)
108%
1 T4400 +
3724 Points (4%)

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

Average Benchmarks Intel Pentium Dual Core T4200 → 94% n=10

Average Benchmarks Intel Pentium Dual Core T4400 → 98% n=10

- 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.18
log 27. 23:04:11

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

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

#2 checking url part for id 565 +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 Sun, 25 Sep 2022 13:14:15 +0200 +0s ... 0s

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

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

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

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

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

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

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

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

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

#19 got single benchmarks 593 +0.016s ... 0.025s

#20 getting avg benchmarks for device 456 +0s ... 0.025s

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

#22 got single benchmarks 456 +0.028s ... 0.054s

#23 getting avg benchmarks for device 565 +0s ... 0.055s

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

#25 got single benchmarks 565 +0.014s ... 0.069s

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

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

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

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

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

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

#32 linkCache_getLink no uid found +0.001s ... 0.07s

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

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

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

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

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

#38 linkCache_getLink no uid found +0.001s ... 0.071s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#55 linkCache_getLink no uid found +0s ... 0.072s

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

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

#58 linkCache_getLink no uid found +0s ... 0.073s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#81 linkCache_getLink no uid found +0s ... 0.076s

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

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

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

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

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

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

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

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

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

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

#92 linkCache_getLink no uid found +0s ... 0.077s

#93 linkCache_getLink no uid found +0s ... 0.077s

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

#95 linkCache_getLink no uid found +0s ... 0.077s

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

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

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

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

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

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

#102 linkCache_getLink no uid found +0s ... 0.078s

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

#104 linkCache_getLink no uid found +0s ... 0.078s

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

#106 linkCache_getLink no uid found +0s ... 0.078s

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

#108 linkCache_getLink no uid found +0s ... 0.079s

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

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

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

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

#113 linkCache_getLink no uid found +0s ... 0.08s

#114 linkCache_getLink no uid found +0s ... 0.08s

#115 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.08s

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

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

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

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

#120 linkCache_getLink no uid found +0s ... 0.081s

#121 linkCache_getLink no uid found +0s ... 0.081s

#122 linkCache_getLink no uid found +0s ... 0.081s

#123 linkCache_getLink no uid found +0s ... 0.081s

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

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

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

#127 linkCache_getLink no uid found +0s ... 0.082s

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

#129 linkCache_getLink no uid found +0s ... 0.082s

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

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

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

#133 linkCache_getLink no uid found +0s ... 0.083s

#134 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.084s

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

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

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

#138 linkCache_getLink no uid found +0s ... 0.084s

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

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

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

#142 linkCache_getLink no uid found +0s ... 0.084s

#143 linkCache_getLink no uid found +0s ... 0.085s

#144 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.085s

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

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

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

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

#149 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.086s

#150 linkCache_getLink no uid found +0s ... 0.086s

#151 linkCache_getLink using $NBC_LINKCACHE +0s ... 0.086s

#152 linkCache_getLink no uid found +0s ... 0.086s

#153 min, max, avg, median took s +0s ... 0.087s

#154 return log +0s ... 0.087s

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)