Intel Core i5-11600K – Rocket with 6 Core boosters
Intel Rocket Lake-S with 6-cores makes a debut on the Geekbench website.
Most Rocket Lake-S leaks covered the 8-core Core i7/i9 series, leaving the Core i5 series a bit of a mystery. Today the first result of the i5-11600K CPU on Geekbench has been discovered, but it does paint a clear picture yet.
The i5-11600K is a 6-core and 12-thread Rocket Lake-S CPU with a base clock of 3.9 GHz and a boost clock of 4.9 GHz. The sample was tested on a Gigabyte Z490M motherboard and (unfortunately) with 2133 MHz DDR4 memory. This means that the score is definitely affected by relatively slow memory configuration.
Intel Core i5-11600K Specifications, Source: Geekbench
Intel Core i5-11600K Score, Source: Geekbench
With a single-core score of 1565 points, the CPU is slower than 6-core AMD Ryzen 5 5600X. The same applies to multi-threaded performance. However, in comparison to Comet Lake-S CPU, we are looking at a 19% increase in single-core performance. There appears to be an issue with multi-core performance, as right now it appears that the current-gen CPU (10600K) is 13% faster than its successor.
The chart below represents average scores, either from the official Geekbench V5 CPU ranking or manually calculated from available scores.
Geekbench V5 Performance | |||
---|---|---|---|
CPU | Configuration | Single-Core | Multi-Core |
Intel Core i9-11900K | 8C/16T @ 5.3 GHz | ||
Intel Core i7-11700K | 8C/16T @ 4.9 GHz | ||
Intel Core i5-11600K | 6C/12T @ 4.9 GHz | ||
AMD Ryzen 9 5950X | 16C/32T @ 4.9 GHz | ||
AMD Ryzen 7 5800X | 8C/16T @ 4.7 GHz | ||
AMD Ryzen 9 5900X | 12C/24T @ 4.8 GHz | ||
AMD Ryzen 5 5600X | 6C/12T @ 4.6 GHz | ||
Intel Core i7-11370H | 4C/8T @ 4.8 GHz | ||
Intel Core i9-10900K | 10C/20T @ 5.3 GHz | ||
Intel Core i5-10600K | 6C/12T @ 4.8 GHz |
Intel is set to announce its Rocket Lake-S CPUs on March 15th. The series will feature PCI Gen4 support and a new Cypress Cove core architecture. This will be the final series for the LGA1200 socket.
Source: Geekbench via @leakbench