Notebookcheck Logo

Intel Pentium Dual Core T4300 vs Intel Pentium Dual Core T4200

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 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)

ModelIntel Pentium Dual Core T4300Intel Pentium Dual Core T4200
SeriesIntel Pentium Dual CoreIntel Pentium Dual Core
CodenamePenrynPenryn
Serie: Pentium Dual Core Penryn
Intel Pentium Dual Core T4500 compare2.3 GHz2 / 2
Intel Pentium Dual Core T4400 compare2.2 GHz2 / 2
» Intel Pentium Dual Core T43002.1 GHz2 / 2
Intel Pentium Dual Core T42002 GHz2 / 2
Intel Pentium Dual Core SU4100 compare1.3 GHz2 / 2
Intel Pentium Dual Core T4500 compare2.3 GHz2 / 2
Intel Pentium Dual Core T4400 compare2.2 GHz2 / 2
Intel Pentium Dual Core T43002.1 GHz2 / 2
» Intel Pentium Dual Core T42002 GHz2 / 2
Intel Pentium Dual Core SU4100 compare1.3 GHz2 / 2
Clock2100 MHz2000 MHz
FSB800800
L1 Cache128 KB128 KB
L2 Cache1 MB1 MB
Cores / Threads2 / 22 / 2
TDP35 Watt35 Watt
Transistors410 Million410 Million
Technology45 nm1.05-1.15V45 nm
Die Size107 mm2107 mm2
SocketPGA478PG478
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), TXT
Architecturex86x86
Announced
max. Temp.105 °C

Benchmarks

Cinebench R10 - Cinebench R10 Rend. Single (32bit)
min: 2153     avg: 2243     median: 2242 (20%)     max: 2335 Points
Cinebench R10 - Cinebench R10 Rend. Multi (32bit)
min: 3963     avg: 4148     median: 4057 (6%)     max: 4425 Points
Cinebench R10 - Cinebench R10 Rend. Multi (64bit)
100%
1 T4300 +
4415 Points (4%)
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
100%
1 T4300 +
2040 Points (12%)
wPrime 2.10 - wPrime 2.0 1024m *
1252 s (15%)
min: 1236     avg: 1643     median: 1242 (15%)     max: 2451 s
wPrime 2.10 - wPrime 2.0 32m *
39 s (8%)
min: 39     avg: 51.4     median: 39.3 (8%)     max: 76 s
3DMark 06 - CPU - 3DMark 06 - CPU
min: 1692     avg: 1798     median: 1825 (4%)     max: 1848 Points
min: 1578     avg: 1660     median: 1636 (3%)     max: 1784 Points
Super Pi mod 1.5 XS 1M - Super Pi mod 1.5 XS 1M *
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: 54     avg: 62.3     median: 64 (3%)     max: 69 s
Super Pi Mod 1.5 XS 32M - Super Pi mod 1.5 XS 32M *
min: 1341     avg: 1469     median: 1528 (7%)     max: 1539 s
SiSoft Sandra Dhrystone (MIPS) - SiSoft Sandra Dhrystone (MIPS)
min: 17767     avg: 18550     median: 18550 (9%)     max: 19333 MIPS
min: 18119     avg: 18259     median: 18259 (9%)     max: 18399 MIPS
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
min: 13927     avg: 14231     median: 14231 (11%)     max: 14535 MFLOPS
min: 14415     avg: 14562     median: 14561.5 (11%)     max: 14708 MFLOPS
PCMark 05 - PCMark 05 - Standard
100%
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 T4300 +
min: 5.3     avg: 5.4     median: 5.4 (69%)     max: 5.4 Points
3DMark Vantage - 3DM Vant. Perf. CPU no Physx
min: 3590     avg: 3788     median: 3787.5 (4%)     max: 3985 Points
3434 Points (4%)

Average Benchmarks Intel Pentium Dual Core T4300 → 100% n=11

Average Benchmarks Intel Pentium Dual Core T4200 → 97% n=11

- 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 13. 17:59:27

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

#1 checking url part for id 456 +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 Thu, 11 Aug 2022 13:13:36 +0200 +0.001s ... 0.001s

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

#5 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.006s

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

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

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

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

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

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

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

#13 getting avg benchmarks for device 490 +0s ... 0.008s

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

#15 got single benchmarks 490 +0.017s ... 0.025s

#16 getting avg benchmarks for device 456 +0s ... 0.026s

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

#18 got single benchmarks 456 +0.031s ... 0.057s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#35 linkCache_getLink using $NBC_LINKCACHE +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 no uid found +0s ... 0.059s

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

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

#42 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.06s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#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 no uid found +0s ... 0.062s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#86 linkCache_getLink no uid found +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 using $NBC_LINKCACHE +0s ... 0.066s

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

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

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

#98 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.067s

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

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

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

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

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

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

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

#106 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.068s

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

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

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

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

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

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

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

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

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

#116 min, max, avg, median took s +0s ... 0.069s

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

#118 return log +0.004s ... 0.073s

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)