SoylentNews

Intel Could Drop Hyperthreading from Next-Generation Core i7 Chips

posted by mrpg on Thursday July 26 2018, @01:33AM   
from the i-see dept.

takyon writes:

Leaked benchmarks show Intel is dropping hyperthreading from i7 chips

Benchmarks found in the SiSoft Sandra database list a Core i7-9700K processor. This increases the core count from the current six cores in the 8th generation Coffee Lake parts to eight cores, but, even though it's an i7 chip, it doesn't appear to have hyperthreading available. Its base clock speed is 3.6GHz, peak turbo is 4.9GHz, and it has 12MB cache. The price is expected to be around the same $350 level as the current top-end i7s.

For the chip that will sit above the i7-9700K in the product lineup, Intel is extending the use of its i9 branding, initially reserved for the X-series High-End Desktop Platform. The i9-9900K will be an eight-core, 16-thread processor. This bumps the cache up to 16MB and the peak turbo up to 5GHz—and the price up to an expected $450.

Below the i7s will be i5s with six cores and six threads and below them, i3s with four cores and four threads.

Meanwhile, AMD's 7nm Ryzen 2 is rumored to boost instructions per clock (IPC) by 10-15% and increase the number of cores per core complex (CCX) from 4 to 8, potentially resulting in mainstream 16 core, 32 thread CPUs.

---

Original Submission

• You can't legitimately generalize here You can't legitimately generalize here (Score: 3, Interesting) by fyngyrz on Thursday July 26 2018, @12:27PM (2 children)

  by fyngyrz (6567) on Thursday July 26 2018, @12:27PM (#713044) Journal

  Congratulations, HT, with #threads doubled, and 5% more clock cycles, you managed 4% more processing. I think that means you made things worse.

  It's not that simple.

  It depends - a lot - on the instruction mix, how much memory outside the caches is being hit, and for many CPUs, whether there are FPU operations going on.

  Knowing what the various issues are, one can tailor c/c++ code to take considerable advantage of hyperthreads in image processing, for instance.

  For "just code" where the author(s) of the code are not paying attention to these issues, threading can certainly bog down. But that's not a hardware problem, per se. It's a programmer problem. The world has a lot of those problems. :)

  Parent

  Starting Score:	1		point
  Moderation		+1
  Interesting=1, Total=1
  Extra 'Interesting' Modifier		0
  Karma-Bonus Modifier		+1
  Total Score:		3

• Re:You can't legitimately generalize here (Score: 2, Funny) by Anonymous Coward on Thursday July 26 2018, @04:05PM

  by Anonymous Coward on Thursday July 26 2018, @04:05PM (#713180)

  Yes, if not for those pesky people, then great things like IA-64 and Soviet communism would have been a success!

  Parent

• Re:You can't legitimately generalize here (Score: 2) by sjames on Thursday July 26 2018, @06:37PM

  by sjames (2882) on Thursday July 26 2018, @06:37PM (#713296) Journal

  For a simple rule of thumb, if you're doing heavy floating point, turn HT off. If it's a network server or desktop, turn HT on.

  Parent