The Intel Core 2 Duo P8700 is a mid-range dual core processor for laptops. It features 2.53 GHz and a shared level 2 cache of 3 MB. Due to the smaller cache (Core 2 Duo T-Models got usually 6 MB at this clock rate), the TDP is only 25 Watt (instead of the 35 Watt of the T-models). Technically, the P8700 is a slower clocked P8800 CPU.
Due to the relatively high clock speed, modern games (in 2009) should not be limited by the CPU speed (in conjunction with a middle class graphics card). High end gamers should choose a higher clocked Dual Core instead (when using a high end GPU).
The P8700 uses a Penryn (Montevina Update) core that features 2 integer units, 1 floating point unit, 1 load unit, and 1 store unit in a 14-stages long pipeline. Due to the Wide Dynamic Execution Technology, the core is able to simultaneously execute up to four instructions.
The integrated Enhanced Speedstep is able to downclock the core dynamically as low as 1200 MHz to save power (in idle mode).
The Intel Core 2 Duo T6500 is an entry level dual core processor for laptops. It is based on the Penryn core but offers only 2 MB level 2 cache and a slow clock rate of 2.1 GHz. Compared to the Core 2 Duo T6570, the T6500 does not offer Virtualization VT-x and is therefore aimed at consumer notebooks.
The performance should be suited for non demanding applications like office, internet, entry level video editing or image correction. CPU intense games may be limited by the power of the T6500.
The Intel Core 2 Duo SU9600 is a power efficient subnotebook processor based on the Penryn 3M core. It features all functions of the Penryn core, like Virtualization (VT-x), Trusted Execution and Speedstep. Due to the low core clock, the performance is a bit limited, but should be sufficient for everyday tasks.
Average Benchmarks Intel Core 2 Duo P8700 → NAN%n=
Average Benchmarks Intel Core 2 Duo T6500 → NAN%n=
- Range of benchmark values for this graphics card - Average benchmark values for this graphics card * Smaller numbers mean a higher performance 1 This benchmark is not used for the average calculation
log 30. 04:19:16
#0 checking url part for id 451 +0s ... 0s
#1 checking url part for id 453 +0s ... 0s
#2 checking url part for id 473 +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, 25 Mar 2023 14:08:33 +0100 +0.001s ... 0.001s
#5 composed specs +0.025s ... 0.026s
#6 did output specs +0s ... 0.026s
#7 getting avg benchmarks for device 451 +0.002s ... 0.028s
#8 got single benchmarks 451 +0.048s ... 0.076s
#9 getting avg benchmarks for device 453 +0.002s ... 0.077s
#10 got single benchmarks 453 +0.043s ... 0.12s
#11 getting avg benchmarks for device 473 +0.002s ... 0.122s
#12 got single benchmarks 473 +0.006s ... 0.128s
#13 got avg benchmarks for devices +0s ... 0.128s
#14 min, max, avg, median took s +0.055s ... 0.182s