Cast your vote Do you agree or disagree with CPUBoss?

Thanks for adding your opinion. Follow us on Facebook to stay up to date with the latest news!
VS

Differences What are the advantages of each

Front view of Intel Core2 Duo E4200

Reasons to consider the
Intel Core2 Duo E4200

Report a correction
Much more l2 cache 2 MB vs 0 MB Compared to all cpus, 2 MB l2 cache is just OK
Much newer manufacturing process 65 nm vs 90 nm A newer manufacturing process allows for a more powerful, yet cooler running processor
Much more l2 cache per core 1 MB/core vs 0 MB/core Compared to all cpus, 1 MB/core l2 cache per core is just OK
More cores 2 vs 1 Twice as many cores; run more applications at once
Front view of AMD Sempron 3600+

Reasons to consider the
AMD Sempron 3600+

Report a correction
Higher clock speed 2 GHz vs 1.6 GHz Around 25% higher clock speed
Better overclocked clock speed (Air) 2.16 GHz vs 1.6 GHz Around 35% better overclocked clock speed (Air)
Better overclocked clock speed (Water) 2 GHz vs 1.6 GHz Around 25% better overclocked clock speed (Water)

Features Key features of the Core2 Duo E4200  vs Sempron 3600+ 

clock speed

L2 cache

overclocked clock speed (air)

Core2 Duo E4200
1.6 GHz
Sempron 3600+
2.16 GHz

overclocked clock speed (water)

Specifications Full list of technical specs

summary

Core2 Duo E4200  vs
Sempron 3600+ 
Clock speed 1.6 GHz 2 GHz
Cores Dual core Single core
Socket type
LGA 775
AM2
S1
754

features

Has a NX bit Yes Yes
Instruction set extensions
SSE2
MMX
SSE3
SSE
3DNow!
Supplemental SSE3
Supports dynamic frequency scaling Yes Yes

bus

Clock speed 800 MHz 333 MHz

details

Core2 Duo E4200  vs
Sempron 3600+ 
Threads 2 1
L2 cache 2 MB 0 MB
L2 cache per core 1 MB/core 0 MB/core
Manufacture process 65 nm 90 nm
Max CPUs 1 1

overclocking

Overclocked clock speed 1.6 GHz 2.16 GHz
Overclocked clock speed (Water) 1.6 GHz 2 GHz
Overclocked clock speed (Air) 1.6 GHz 2.16 GHz

power consumption

Typical power consumption N/A 50.38W
Intel Core2 Duo E4200
Report a correction
AMD Sempron 3600+
Report a correction

Comments

comments powered by Disqus