The Core i5-6500T is at least 2x faster gaming CPU than the Core i7-2600S. We cannot compare value as at least one CPU is out of stock.
Advantages of the Core i5-6500T
- At least 2x faster CPU for gaming
- Consumes up to 46% less energy – 35 vs 65 Watts
Advantages of the Core i7-2600S
- Can execute more multi-threaded tasks simultaneously – 8 vs 4 threads
Core i5-6500T vs Core i7-2600S for Gaming
The CPU's performance in selected game and settings
Core i5-6500T
Jul 2nd, 2015
Average FPS
179
100%
Min 1% FPS
119
100%
Price, CA$
Out of Stock
Value, CA$/FPS
Not Available
All items are out of stock.
Core i7-2600S
Jan 9th, 2011
Average FPS
169
94%
Min 1% FPS
114
96%
Price, CA$
Out of Stock
Value, CA$/FPS
Not Available
All items are out of stock.
Core i5-6500T vs Core i7-2600S in My Games
The FPS you'll get in saved games
The FPS you'll get in saved games
Add a Game
Select Settings
Synthetic Benchmarks
The Core i5-6500T vs Core i7-2600S in synthetic CPU benchmarks
Performance Specifications
The Core i5-6500T vs Core i7-2600S in core CPU performance specifications
Core i5-6500T
Jul 2nd, 2015
Cores
4-core
100%
L3 Cache
6 MB
75%
Base Frequency
2.5 GHz
89%
Turbo Frequency
3.1 GHz
82%
Max. DDR4 RAM Speed
2133 MHz
100%
Core i7-2600S
Jan 9th, 2011
Cores
4-core
100%
L3 Cache
8 MB
100%
Base Frequency
2.8 GHz
100%
Turbo Frequency
3.8 GHz
100%
Max. DDR3 RAM Speed
MHz
Specifications
Comparison of all specifications
Core i5-6500T | SpecificationsComparison of all specifications | Core i7-2600S |
---|---|---|
General | ||
Jul 2nd, 2015 | Release Date | Jan 9th, 2011 |
Not Available | MSRP | Not Available |
Desktop | Segment | Desktop |
Intel Socket 1151 | Socket | Intel Socket 1155 |
Skylake | Codename | Sandy Bridge |
35 W | Power Consumption | 65 W |
Performance | ||
4 | Cores | 4 |
4 | Threads | 8 |
2.5 GHz | Base Frequency | 2.8 GHz |
3.1 GHz | Turbo Frequency | 3.8 GHz |
6 MB | L3 Cache | 8 MB |
Other Features | ||
DDR3 @ 2133 MHz, DDR4 @ 2133 MHz | RAM | DDR3 |
HD Graphics 530 | Integrated Graphics | Intel HD 2000 |
No | Overclockable | No |