Geekbench has been a good source of Intel Comet Lake U series information recently, with the Core i7-10510U and Core i5-10210U appearing on the website last month. Moreover, earlier today @momomo_us tweeted a screenshot of some upcoming HP laptops powered by three Comet Lake U (CML-U) CPUs. All these are quad-core processors, but another Geekbench listing suggests that a fourth is in the works, and it offers another step-up in core count for the Core U series.
The processor in question is the Core i7-10710U, which will be the first hexacore U series chip. The CPU will support Intel Hyper-Threading too, giving it 12 threads. The 14 nm processor will also have a 1.61 GHz base clock according to Geekbench and can clock up to 4.67 GHz on all cores. Most U series can reach higher single-core clock speeds, so it would not be a stretch to suggest that the Core i7-10710U will too. The processor will have 12 MB of L3 cache, 4 MB more than the Core i7-10510U. Incidentally, the Core i7-10710U will also have 1.5 MB of L2 cache, a 0.5 MB bump on most modern U series chips.
While the Core i5-10210U and Core i7-10510U posted disappointing Geekbench scores, the Core i7-10710U posted 5,169 single-core and 15,927 multi-core scores. While the former puts the Core i7-10710U on par with the average of Core i7-8565U powered devices that we have tested in the single-core portion of Geekbench 4, it sits 16% ahead in the multi-core benchmark. By contrast, the Core i7-8565U averages over 50% more than the Core i7-7500U in the multi-core portion of Geekbench 4. The Core i7-10710U does score almost 40% more than the Ryzen 7 3750H though, although it is worth keeping in mind that the latter is only a quad-core CPU.
We are not drawing any conclusions yet about the Core i7-10710U though, as this is just one benchmark posting from what is probably an engineering sample. While it is a shame to see yet another 14 nm U series processor, we are intrigued to see how this hexacore CPU performs and how well ultrabooks can cool it.
Source(s)
Geekbench via @InstLatX64