Notebookcheck Logo

Intel Pentium Dual Core T4300 vs Intel Pentium Dual Core SU4100

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 T4300Intel Pentium Dual Core SU4100
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 T4200 compare2 GHz2 / 2
Intel Pentium Dual Core SU41001.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 T4200 compare2 GHz2 / 2
» Intel Pentium Dual Core SU41001.3 GHz2 / 2
Clock2100 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
max. Temp.100 °C
ManufacturerIntel Pentium Dual Core SU4100

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)
4415 Points (4%)
2881 Points (3%)
Cinebench R10 - Cinebench R10 Rend. Single (64bit)
2040 Points (12%)
1542 Points (9%)
wPrime 2.10 - wPrime 2.0 1024m *
1252 s (15%)
min: 1986     avg: 3179     median: 3754 (44%)     max: 3796 s
wPrime 2.10 - wPrime 2.0 32m *
39 s (8%)
3DMark 06 - CPU - 3DMark 06 - CPU
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: 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
SiSoft Sandra Whetstone (MFLOPS) - SiSoft Sandra Whetstone (MFLOPS)
min: 13927     avg: 14231     median: 14231 (11%)     max: 14535 MFLOPS
PCMark 05 - PCMark 05 - Standard
100%
1 SU4100 +
min: 3108     avg: 3274     median: 3274 (21%)     max: 3440 Points
Windows 7 Experience Index - Win7 CPU
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 T4300 → 100% n=13

Average Benchmarks Intel Pentium Dual Core SU4100 → 76% 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

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 08. 18:18:51

#0 checking url part for id 490 +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 Sat, 06 Aug 2022 13:13:32 +0200 +0s ... 0s

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

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

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

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

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

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

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

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

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

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

#18 got single benchmarks 504 +0.023s ... 0.049s

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

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

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

#22 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.051s

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

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

#25 linkCache_getLink no uid found +0.001s ... 0.051s

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

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

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

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

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

#31 linkCache_getLink no uid found +0.001s ... 0.053s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#84 linkCache_getLink using $NBC_LINKCACHE +0.001s ... 0.061s

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

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

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

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

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

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

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

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

#93 min, max, avg, median took s +0s ... 0.062s

#94 linkCache_getLink using $NBC_LINKCACHE +0.025s ... 0.087s

#95 return log +0.004s ... 0.091s

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: Sebastian Jentsch,  8.09.2017 (Update: 19.05.2020)