Slashdot Mirror


Leaked Benchmarks Suggest Intel Will Drop Hyperthreading From Core i7 Chips (arstechnica.com)

According to leaked benchmarks found in the SiSoft Sandra database, there is an Intel Core i7-9700K processor that doesn't appear to have hyperthreading available. "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," reports Ars Technica. "It's 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." From the report: 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. Even without hyperthreading, the new i7s should be faster than old i7s. A part with eight cores is going to be faster than the four-core/eight-thread chips of a couple of generations ago and should in general also be faster than the six-core/12-thread 8th generation chips. Peak clock speeds are pushed slightly higher than they were for the 8th generation chips, too.

199 comments

  1. Never been a fan of hyperthreading by InvalidsYnc · · Score: 5, Interesting

    I've always seen them as "pseudo" cpu's, and not been all that happy with them overall. Yeah, some workloads benefit from it just fine, but others get tanked, but you'll never know because it just looks like those CPU's are flying along (according to task mangler or whatever).

    Anyway, glad to see that there will be some parts out there that people can choose to buy that don't have it.

    1. Re:Never been a fan of hyperthreading by jader3rd · · Score: 2

      What are those workloads that actually benefit from thinking the CPU has more cores than what it actually has?

    2. Re:Never been a fan of hyperthreading by Anonymous Coward · · Score: 5, Informative

      workloads that cause a lot of switching between processes/Jobs. We have many systems that benefit hugely from hyper threading, others that get bugger all and still more where we explicitly disable it as it slows down the system.

    3. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 5, Informative

      Integer heavy workloads, sometimes branch heavy coding. The physical core 0 really can do two things at once, but only for some things. Much like how you can pet two cats in half the time with your two hands, but can only drink water at a rate limited by your mouth.

      The big things are this:
      1- It is rare to find a workload that works better with HT off
      2- It is common to find a workload that gets some speedup
      3- HT may have some vague security issues, based on recent actions from BSD etc. Maybe.

      Anyway, those three things should mostly determine whether you turn HT on or off on your box, and really just the first two unless you are Server Guy.

    4. Re:Never been a fan of hyperthreading by z3alot · · Score: 1

      Modern cpus are designed so that some instructions take multiple cycles to complete. Think floating point operations, loads and stores, probably most nontrivial instruction from extended sets (SSE, AVX, etc). During these operations, the cpu can do other business and will try to schedule all its modules maximally. Just as an example, imagine a floating point matrix multiplication. The loop bookkeeping code (index compare and branch, increment) is literally free because it can complete fast enough to keep the floating point math module 100% saturated. In this workload, the integer module is mostly idle.

      My understanding of hyperthreading is its an attempt to schedule the cpu modules maximally over 2 threads, not just 1. So maybe you would see a benefit if 1 process was doing a lot of memory operations and the other a lot of math, or if 1 was doing a lot of integer math and the other floating point math. I'm not an expert on this but my understand is that billions of dollars in research have gone to squeeze average case performance out of modern cpus and HT is one piece of the puzzle.

    5. Re:Never been a fan of hyperthreading by viperidaenz · · Score: 1

      HT can reduce context switching overheads and it can make use of more execution units at once.

    6. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 5, Funny

      I welcome these simultaneous-cat-petting analogies.

    7. Re:Never been a fan of hyperthreading by Anonymous Coward · · Score: 1

      ...if by "modern" you mean "since the 8086/8087 in 1980" then yes?

      CISC processors have had variable instruction timings pretty much as their defining feature from day one, RISC is where 'one instruction, one cycle' is far more often the norm.

      - WolfWings, too lazy to login to /. in way too long.

    8. Re:Never been a fan of hyperthreading by Tough+Love · · Score: 4, Interesting

      So what you're saying is, you have no idea what hyperthreading is but you don't like it because it does not benefit all workloads? I hope you can see what's wrong with that argument. If not, I will try to help.

      Hyperthreading (a simplified form of SMT is about putting cpu cores to work that would otherwise stall, e.g., waiting on a memory load. If your workload has everything in L1 cache then SMT won't do anything and just wastes transistors, which could have been better used by providing more cores or more cache memory. Most loads do hit enough memory that SMT is a win for parallel latency, however for those that don't, SMT can actually slow things down as multiple threads compete for limited superscalar resources such as register files. If there aren't too many parallel threads then it would be better to give each its own core.

      So here is the thing: to make best use of SMT you need to know something about how SMT works, and something about your workload. Then you can potentially use CPU affinity to tune your application. If you are ignorant about either of these things, or you can't justify the time to do the necessary tuning, or you don't have the necessary access, then sometimes, yes, SMT is just going to bite. But it wins on average, which is why all modern general purpose processors implement it, with the notable exception of ARM.

      Throughput is not the entire story about SMT, there is also power efficiency. Additional logic is required to fetch two independent instruction streams in parallel, keep them independent, and manage the additional cache complexity. This does not slow things down but eats power, which is why ARM so far does not implement it, and Intel does not use it for Atom. This sacrifices parallel throughput, and if you have any Atom devices, you will be painfully aware that they suck compared to their core arch cousins. Intel had to about face on this when AMD dropped Ryzen on them so now, some low end Intel parts also have hyperthreading.

      Fast forward to today's rumor. It should be clear that not having Hyperthreading/SMT hurts performance on average, but can improve power efficiency. Simple conclusion: these i7's are aimed at the notebook/ultrabook/chromebook market where battery life and weight are more important than performance. You don't want these for your server, desktop or fat ass laptop.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    9. Re:Never been a fan of hyperthreading by gman003 · · Score: 5, Interesting

      A lot of them, actually.

      A modern "core" has several "execution units". Unlike very early x86, where it was divided between ALU and FPU, these are divided more finely and evenly - one might do integer math, vector shifts, and branches, while another might do integer math, vector logic, and data stores. There's usually redundancy on common instruction types (eg. Haswell has three that can do address stores, but only one can do divides).

      In a single thread, this is used for superscalar execution. If you have code something like "a = b / c; d = e * f;", both instructions can be run in parallel since neither depends on the other. This also hides the cost of x86's more complicated addressing modes - computing the address gets dispatched to an execution unit just like a normal multiply/add, and the result just gets sent to the store unit.

      But sometimes a thread has lots of dependencies, or does mainly a single type of operation. Maybe it's crunching through a bunch of multiply-adds. Rather than let the remainder of the core sit idle, you can run another thread, or even another process, on it. If this second one mainly hits a different EU - say, it's doing a lot of shifting and bit-twiddling - you can get a 100% speedup.

      You rarely get so much of a boost in practice. A worker-thread type of program, splitting a parallel task across cores, will generally be using the same execution units in each thread. And SMT doesn't help if you're bottlenecked on something besides execution - well-optimized code, as often as not, is limited by memory throughput rather than execution.

      The other boost comes from covering memory latency. If one thread hits a load that isn't in L1 cache, it will stall while the load is served. If it's in L2 cache, that's not too long - a dozen cycles or so. If you're going out to main memory, you're looking at a few hundred, maybe a few thousand cycles of NOPs - so why not switch to another thread, that has all it's data in L1 cache already? Modern x86 processors have pretty low memory latency compared to other architectures, so two threads is generally the most you'd find useful for this, but other systems with harsher memory latency will go even wider - the latter-day SPARCs do eight threads per core, and some parts of a GPU will operate in the hundreds. This is why some non-superscalar architectures will still have multiple threads per core - it's only ever actually running one instruction, but it will rarely be running zero.

    10. Re:Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      Something that does a load and a few simple integer instructions, because you can execute multiple simple integer instructions in the latency shadow of a load.

    11. Re:Never been a fan of hyperthreading by arbiter1 · · Score: 1

      Good example is Twitch streamers, Ones that game and stream off same cpu. Hyper threading help's a ton in that when playing a game and encoding video at same time.

    12. Re:Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      It's 2018, why is the video encoding happening on the CPU?

    13. Re:Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      if your playing a game the last thing you want is the encoding stealing GPU cycles, you usually have more spare CPU than GPU cycles.

    14. Re:Never been a fan of hyperthreading by Tyger-ZA · · Score: 1

      if your playing a game the last thing you want is the encoding stealing GPU cycles, you usually have more spare CPU than GPU cycles.

      Or option 3: dedicated hardware for capturing the video stream, Like the PS4 has.

    15. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      You do know that hyperthreading can be disabled, right? How about being happy for that instead?

    16. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      Integer heavy workloads, sometimes branch heavy coding. The physical core 0 really can do two things at once, but only for some things. Much like how you can pet two cats in half the time with your two hands, but can only drink water at a rate limited by your mouth.

      The big things are this:
      1- It is rare to find a workload that works better with HT off
      2- It is common to find a workload that gets some speedup
      3- HT may have some vague security issues, based on recent actions from BSD etc. Maybe.

      Anyway, those three things should mostly determine whether you turn HT on or off on your box, and really just the first two unless you are Server Guy.

      4. At one point turning off HT was one recommendation to improve your max overclock. Now I don't recommend that, since its usually more trouble than its worth, but its still an interesting data point. I'm not sure if that was just because the CPU generated less heat, and I have zero idea if keeping HT off means they can sell CPUs at higher clock rates, but if they could it might be a factor.

      Basically if you could sell a CPU at a few percent higher max rating, plus get rid of the security issues, it might be worth it.

      Another factor might be in laptops. You have an extremely constrained power limitation there due to having to dissipate the heat. Is turning off hyperthreading or perhaps leaving it out entirely of the design something that helps? Basically if the cpu can maybe run at full rate more often, then maybe hyperthreading isn't helping there.

    17. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      Radeon relive from AMD, dedicated hardware on the gpu

    18. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      The gpus have dedicated video encoding hardware, it doesnt't use the cores. Overhead for the last few generations has been single digit.

      You can also use the otherwise unused igpu on intel cpus for encoding.

    19. Re:Never been a fan of hyperthreading by Anonymous Coward · · Score: 1

      It's not actually dedicated capture hardware.

      It's just using the dedicated video decoding/encoding hardware the GPU includes, which otherwise sits idle during gaming.

      NVidia supports the same thing, as does Intel, pretty much everyone for the last several generations of hardware now.

      Capturing the video buffers is rarely/never the issue, it's converting the framebuffer to the low-bitrate video encoding to upload it quickly. And CPU's have a (shrinking) advantage over even the best GPU's for encoding quality at the low ~2.5MBit-and-under bitrates that Twitch and other streaming solutions work best with. At media-center/LAN bitrates hardware encoding handily keeps up with CPU encoding.

      Heck just a year or two ago that would've said 2MBit not even 2.5MBit, because stable upstream bandwidth was often unable to handle 2.5MBit for most folks and mobile browsers would choke trying to watch the streams as well.

      In another 2 generations/years (so whatever's after Volta for NVidia at least) GPUs will possibly match CPU encoding quality at these low bitrates, especially if it becomes safer to bump that common bitrate level to 3MBit but that's too up in the air so it might be 3 generations before CPU encoding really gets a nail in the coffin.

      - WolfWings, too lazy to login to /., because why bother? :)

    20. Re: Never been a fan of hyperthreading by ezelkow1 · · Score: 1

      There are NVENC blocks on the nvidia cards as well specific for hardware encoding, all gpu's that feature encode have hardware support for it otherwise they wouldnt even bother to offer it as it would affect actual game play too much

    21. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 1

      Those cats do need to be very well-domesticated, or the simultaneous double-petter will be sorry to miss the cues of increasing agitation of one of them.

    22. Re:Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      Simple conclusion: these i7's are aimed at the notebook/ultrabook/chromebook market where battery life and weight are more important than performance. You don't want these for your server, desktop or fat ass laptop.

      These are 95W parts. Video encoding should be just fine with these high frequency non-HT parts.

    23. Re:Never been a fan of hyperthreading by Tough+Love · · Score: 3, Interesting

      Simple conclusion: these i7's are aimed at the notebook/ultrabook/chromebook market where battery life and weight are more important than performance. You don't want these for your server, desktop or fat ass laptop.

      These are 95W parts. Video encoding should be just fine with these high frequency non-HT parts.

      But obviously, it would be better with HT. Going to the Arstechnica comments, the consensus is, this is just a marketing move by Intel. To be precise, i9 is the new i7, and open your wallets wider. It is possible that I am also right by saying that these non-HT i7's are targeted at mobile. Bragging rights, ok? "I have an i7 in my laptop, so cool [apple fan voice]". The catch being, i7 is the new i5.

      This game is going to push a lot of folks to Ryzen. Intel must know that. Maybe they are trying to keep Apple from going to ARM?

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    24. Re:Never been a fan of hyperthreading by drinkypoo · · Score: 1

      Simpler conclusion: brand spanking new attack reported recently here on slashdot takes advantage of weaknesses in hyperthreading, and intel has no idea how to make it secure so they are removing it instead

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    25. Re:Never been a fan of hyperthreading by AHuxley · · Score: 1

      When someone pays a really, really smart person to work on the difficult math of video and photography software.
      Do that to some really great software standard with a supportive OS and a new CPU can really offer more.

      --
      Domestic spying is now "Benign Information Gathering"
    26. Re:Never been a fan of hyperthreading by AHuxley · · Score: 1

      Buy another computer and do the streaming external to the game playing computer.

      --
      Domestic spying is now "Benign Information Gathering"
    27. Re: Never been a fan of hyperthreading by Miamicanes · · Score: 4, Informative

      It made a big difference on WinXP with single-core CPUs because XP had lots of performance chokepoints that were limited to a single thread per "CPU".

      The name resolver (which handled not only DNS lookups, but drive-path resolution for Explorer as well) is a noteworthy example. If the browser triggered a "bad" DNS lookup, it would hang Explorer (including the Start menu) until the DNS lookup timed out (30-90 seconds later, IIRC).

      Hyperthreading mitigated 99% of that, because even if one name resolver thread got hung up, the other could keep chugging along.

      As of Win10, most of those chokepoints are gone, and HT is useful mainly with virtual machines (by simplifying program logic since each virtual core gets its own set of registers). The catch is, recently-documented security vulnerabilities suggest it can be used to leak info between VMs... a minor issue for someone using a VM to run Linux under Windows for convenience, but a potentially HUGE issue for comercial hosting services w/multiple unrelated customers.

      In any case, HT is a huge benefit with one single-core CPU, but offers little if you have 8 cores to begin with.

    28. Re:Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      dedicated hardware for capturing the video stream, Like the PS4 has.

      GPUs are not monolithic devices. While the naming convention will vary depending on who you are talking to, there is a concept of a node or engine, which is essentially an independent processor within a GPU for a given type of workload. Rendering 3D or performing compute generally keeps the most powerful node(s) within a GPU busy, functionality provided by other nodes includes copy (DMA), video encode, video decode, content protection, etc. All of these nodes have independent scheduling and are only ever in contention with each other in situations causing memory pressure or excessive bus/memory bandwidth utilization. This allows independent power/performance trade-offs to be made based on the workload each node is optimized for. Whatever feelings you may have about Microsoft products it is worth taking a look at the performance tab of the Windows 10 task manager as recent builds of that OS will show you a per-node graph of workloads scheduled on each OS visible GPU node.

    29. Re: Never been a fan of hyperthreading by Z00L00K · · Score: 1

      What if the streaming is an intrisic part of the game?
      Ok. I don't know if there are such games, but in the world of VR it wouldn't surprise me.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    30. Re: Never been a fan of hyperthreading by Z00L00K · · Score: 1

      More threads on a core also burns more cache. And if both threads need to access ram then you get even more delay.

      Personally I see the hyperthreading as a poor mans multicore solution.

      Your mileage may vary.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    31. Re: Never been a fan of hyperthreading by Z00L00K · · Score: 1

      So from this discussion it's interesting that hyperthreading has been stuck on 2 threads per core for so long. Why not 16 today?

      And what would be more power efficient - more hyperthreading or more cores?

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    32. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      Quality. Pure software encoders product better quality encoded, albeit more slowly.

    33. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      relive is NOT dedicated hardware, it is a mix of software and hardware offloading that uses a portion of the card and has an overhead for both IO and GPU that WILL affect your FPS, it is relatively small because it is so well integrated but it is definitely NOT purely dedicated hardware.

    34. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      It hides memory latency. Applications that have large data sets that are not accessed in a sequential manner gains up to 40% performance with Intel 2 way smt. Even more with more SMT threads. Some version of IBM Power has 8 for example.

    35. Re: Never been a fan of hyperthreading by tlhIngan · · Score: 2

      So from this discussion it's interesting that hyperthreading has been stuck on 2 threads per core for so long. Why not 16 today?

      Because of diminishing returns. It's called "Multithreading" and not "Multiprocessing" because even though it shows up as a separate CPU core, it's shared resources could benefit from threads of the same process far more than disparate threads, especially with respect to cache utilization.

      It comes about because a modern CPU is super-scalar. That is, there are multiple execution units - often 3 (or more) integer units doing simple operations (adds, subtracts, bitshifts, boolean operations, etc), a couple of "complex" integer operations (multiply, divide), several load/store units (at least two each for loading and storing, and sometimes the effective address calculation uses the simple integer ALUs), multiple floating point units - again 2-3 for simple operations, 1 for complex operations and other units. Thing is, one program instruction stream, even with multiple instructions in flight simultaneously may not actually use all the resources. It's fairly cheap to tack on another front end execution unit and run another set of instructions through the same execution units, with the goal to have more utilization of the idle execution units.

      Thus, disparate workloads generally work better - if one is more integer versus floating point, you can often run both together without them colliding. But if you're using all integer, and even worse, both are using the same units, then it will not speedup.

    36. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 1

      Personally I see the hyperthreading as a poor mans multicore solution.

      Sure. Poor mans core is fair enough.
      The thing is that the hyperthreading doesn't cost much chip area. Removing hyperthreading doesn't give you enough room to put in an extra core.

      So the tradeoff isn't a real core vs. hyperthreading, it is if you want hyperthreading on your cores or not.
      Essentially we are back to the tradeoff of security vs. speed.

    37. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      Well, since it takes up about 3% of my work utilization on my GPU but 35% across my 6 cores on my CPU I'd much rather do it on my GPU when gaming.
      Dota 2 drops from 80 to 60fps when encoding on my CPU, but only drops from 80 to 75fps when on the GPU.

      It's not perfect, but the difference is almost negligible on the GPU.

    38. Re: Never been a fan of hyperthreading by Tough+Love · · Score: 1

      There is such a thing as MIPS MT supporting 4 SMT threads. While 2 thread SMT is clearly worth the extra chip real estate on average, it is not clear that the additional complexity to support 4 is worth it, and nobody else followed MIPS in that direction.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    39. Re: Never been a fan of hyperthreading by AmiMoJo · · Score: 1

      Which brings us to the real question, why is Intel removing hyperthreading capability?

      There are some security issues. Maybe it can't overcome them, but AMD has their own version (simultaneous multithreading) that so far hasn't been affected by these problems.

      The other issue is complexity. Maybe they want to simplify the CPU and simply have more of them.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    40. Re:Never been a fan of hyperthreading by Anonymous Coward · · Score: 1

      I don't know of a single single cycle processor in recent history.
      Even crappy do it yourself softcores are usually pipelined.
      Unless you mean fixed pipeline length rather than single cycle.

    41. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      POWER9 processors for those HPC jobs use up to 4-way SMT as well, although they go to 8 for normal server loads in the "scale up" versions. SUN/Oracle used 8-way SMT as well for some of their processors. Each of the implementations are different, of course, and often configurable to a particular load or even dynamic like in some Oracle cores.

    42. Re: Never been a fan of hyperthreading by burhop · · Score: 2

      I welcome these simultaneous-cat-petting analogies.

      You are going to love the future. Quantum computing is based on having a herd of schrodinger cats... more or less.

    43. Re:Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      HT kicks in on a cache-miss, and basically tells the CPU "go do something else while we fetch this from main memory"

      If you're doing something that causes a lot of cache misses, normally because the CPU isn't quite sure whats coming next (i.e. failed branch prediction) then HT is a good use of the downtime. If you're just crunching numbers HT isn't going to get a look in and may as well not exist.

    44. Re:Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      Thank you Id rather have the choice of a bios option instead of having it turned off entirely.
      Every day I am more happy that I went with AMD with my latest builds.

    45. Re:Never been a fan of hyperthreading by mikael · · Score: 1

      Anything computationally intensive that could be parallelized'; numerical simulations, ray-tracing, 3D games, even a HTML get request. The ideas of hyper-threading was that if one thread got blocked with a pending IO operation (like fetching data due to a cache miss), the other thread could continue working. But they both shared the same cache memory and that led to all sorts of problems when you tried to write multi-threaded code accessing the same memory space. All data had to be cache-line aligned and every thread given it's own unique block of the memory space.

      --
      Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
    46. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      Except that intel went from 6 cores to 8 cores. The CPU bound work I do is 3d rendering -- one of those embarrassingly parallel tasks. Hyperthreading may not hurt but it sure doesn't help (in my experience the performance with hyperthreading enabled bobbled just below without hyperthreading, but not enough to be significant much less worth trying to deal with Apple's method of disabling it).

      So going from 6 cores with hyperthreading to 8 cores without will give pretty darn close to a 33% speed improvement. That is something to be happy about.

      Where hyperthreading is absolutely needed is when you have a single physical core -- context switching kills performance but hyperthreading gives zero overhead context switches. It is still good to have with only two physical cores -- but by the time you reach four cores the benefit is marginal. Sure, with the right workloads you will see improvements. But with a single core you *will* see an improvement for *all* workloads.

      In short, the more cores you have the harder you have to look for workloads that will actually benefit from hyperthreading. Hyperthreading is *absolutely* a poor man's multi-core.

    47. Re: Never been a fan of hyperthreading by justthinkit · · Score: 1

      From the summary:

      This increases the core count from the current six cores in the 8th generation Coffee Lake parts to eight cores

      Given that feature size is no longer shrinking, it seems like getting rid of HT gained back not just one but two cores.

      From the article:

      Nonetheless, this change in branding does suggest that Intel is running out of room to maneuver. The 6th, 7th, 8th, and imminent 9th generation processors all (except for some rare 8th generation parts) use cores that are close derivatives of the Skylake design, with each new generation bumping up clock speeds and core counts a little. But both appear to be near their limits. The clock speed changes amount to a mostly negligible 100 or 200MHz, and increasing core counts is of limited value, too. The utility of the extra cores (or threads) is greatly diminished for most mainstream users, and, while Intel does have designs with more than eight cores, these are Skylake-SP and Skylake-X parts; they use a different socket, they have a very different internal layout (the cores are arranged into a grid rather than a ring), and they don't include an integrated GPU.

      In a world of static feature size, they appear to have made a judgment call -- 8 cores with no HT is better than 6 cores with HT. Seems entirely reasonable to me.

      --
      I come here for the love
    48. Re:Never been a fan of hyperthreading by Anonymous Coward · · Score: 1

      actually it should be better without hyperthreading since the saved space was used to expand the number of actual cores.

      But, hey, what do I know -- I only benchmark these things. Primarily because I actually know how hyperthreading works and have to deal with morons who go "but more cores!" and point to the 100% CPU utilization across cores. But I think deep down they know because they refuse to run comparisons without hyperthreading enabled. So I obliged them.

      Clue 1: video encoding is one of those embarrassingly parallel tasks that benefit from more cores.

      But hyperthreading works by faking having more cores -- that's why you can have more "hyperthreaded" cores on the same silicon than single threaded cores. There *is* some silicon overhead (for example, to ensure that context switches between hyperthreaded cores are free -- which in Intel's original implementation they were not).

      Hyperthreading is necessary on low-core count chips because we don't use single-threaded execution environments, but the overhead works against it when you have a decent core count. Intel being able to increase core count 33% by eliminating hyperthreading is a good example.

      When core count reduces CPU clock that is still a win for things like video encoding, rendering, and so on. But not so good for things that are practically single threaded (like games -- there has been significant progress, but they are nowhere near as parallelizable as video encoding). So a gaming rig with a low core count to enable a higher clock and using hyperthreading to make up for the short fall in cores is a good approach.

      But when you are going for high core counts hyperthreading is just a waste of silicon.

    49. Re: Never been a fan of hyperthreading by bluefoxlucid · · Score: 1

      More execution threads may consume more cache, but CPUs have cache coherence algorithms and can share when accessing the same physical addresses. This reduces the impact when executing the same process in two threads.

      SMT (and multicore processing in general) would benefit greatly by coalescing L1 caches (including TLB) where the running processes are assigned the same page table. L2, of course, uses physical addresses.

    50. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      Itâ(TM)s really only useful when twitch streamers shake their massive cans. Then bam the encoder is in overdrive!

    51. Re:Never been a fan of hyperthreading by radarskiy · · Score: 1

      "the saved space was used to expand the number of actual cores"

      a) There's no way you're gonna recover enough die area from removing HT from even the most multi-core SKU to equal the area of an entire additional core.
      b) There's no way you're going to floorplan an entire new core to recover that area from HT for just this SKU. All of the non-server i3/5/7/9 SKUs use the same core layout. (Sometimes the server parts will make core edits and they definitely have different mircrocode ROMs, but all the server SKUs will use that core layout.)

    52. Re:Never been a fan of hyperthreading by radarskiy · · Score: 1

      The one point where I would disagree is the implication that Intel is doing a deliberate defeature for marketing purposes. Everybody is constrained at the high end these days and if you could make more fully featured high-end SKUs you could sell them.

      What I suspect is really happening is that there is a timing problem that's affecting their binsplits and they discovered they can recover the timing if they disable HT. So they redefine the SKU so they can defeature HT rather than down-bin the silicon.

    53. Re:Never been a fan of hyperthreading by BronsCon · · Score: 1

      It's not actually dedicated capture hardware.

      It's just using the dedicated video decoding/encoding hardware

      Okay, well, the GPU essentially captures the stream as it renders it, and encoding is generally considered part of the capture process. In short, your comment distills to "It's not using dedicated hardware, it's using dedicated hardware." This is what happens when you try to be pedantic and fall flat on your face.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    54. Re: Never been a fan of hyperthreading by BronsCon · · Score: 1

      The thing is that the hyperthreading doesn't cost much chip area.

      The extra cache it needs does, though.

      --
      APK quotes people (including myself) without context and should not be trusted. Just thought you should know.
    55. Re:Never been a fan of hyperthreading by lactose99 · · Score: 1

      Web servers, or rather front-end web proxies, tend to be highly threaded and thus benefit from technologies like hyperthreading.

      --
      Fully licensed blockchain psychiatrist
    56. Re:Never been a fan of hyperthreading by lactose99 · · Score: 1

      Interestingly this is pretty much what they did with the i5 Coffee Lake processors. They removed hyperthreading and added 2 additional cores, so instead of 4 cores / 8 threads its 6 cores / 6 threads.

      --
      Fully licensed blockchain psychiatrist
    57. Re: Never been a fan of hyperthreading by Highdude702 · · Score: 1

      Its Intel, I cant give them the benefit of the doubt. So I would bet it has to do with getting more people to shell out i9 money that dont really need i9 computing power. This also may backfire for them and hand a large chunk of the market to AMD.

    58. Re:Never been a fan of hyperthreading by jader3rd · · Score: 1

      Okay, but if all of the threads are running at the same time, wouldn't that just make for more false cache sharing? And if the threads aren't running at the same time, the OS's thread scheduler can take care of that.

    59. Re: Never been a fan of hyperthreading by jader3rd · · Score: 1

      WinXP is perfectly capable of scheduling another thread to run, when one gets hung up. It didn't need a virtual core for that.

    60. Re:Never been a fan of hyperthreading by jader3rd · · Score: 1

      Anything computationally intensive that could be parallelized

      Anything that's computationally intensive like that will start by asking "How many cores do I have?" and then break up the workload accordingly. If it got back 16, when really there were 8 cores, it would break up the work into 16 pieces instead of 8. Hyperthreading can squeeze out some performance if two threads are using completely different instructions, but are using the same cache lines. That's the opposite of what will happen here. The parallelized numerical solutions will be executing the same instructions, while accessing different parts of memory. So it's going to be spending most of the execution time, rehydrating the core caches.

    61. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      > It is rare to find a workload that works better with HT off

      Many highly optimized codes run better with HT off, since it primarily about sharing functional units, which can be driven at maximal rate in some optimized codes.

      HT causes much greater cache thrashing, and this may be the reason to disable it as physical core count continues to rise.

    62. Re:Never been a fan of hyperthreading by Tough+Love · · Score: 1

      The one point where I would disagree is the implication that Intel is doing a deliberate defeature for marketing purposes. Everybody is constrained at the high end these days and if you could make more fully featured high-end SKUs you could sell them.

      The problem with your argument is, AMD does ship an 8 core part with SMT (I thought everybody knew that?). So Intel is doing a deliberate defeature, and you are sufficiently gullible to believe otherwise.

      What I suspect is really happening is that there is a timing problem that's affecting their binsplits and they discovered they can recover the timing if they disable HT. So they redefine the SKU so they can defeature HT rather than down-bin the silicon.

      Long shot theory, marginally possible. I have trouble believing they would have enough parts failing in exactly that way to introduce a whole new SKU. Just market them as i5's.

      This is clearly all about marketing. Intel ships few parts these days, so they obviously need to sell them for more money n'est ce pas?

      Big winner here is AMD, and everyone who switches.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    63. Re: Never been a fan of hyperthreading by Tough+Love · · Score: 1

      POWER9 processors for those HPC jobs use up to 4-way SMT as well, although they go to 8 for normal server loads in the "scale up" versions. SUN/Oracle used 8-way SMT as well for some of their processors. Each of the implementations are different, of course, and often configurable to a particular load or even dynamic like in some Oracle cores.

      Right, it says so in the Wikipedia article I linked, except it says "multithreading", not necessarily simultaneous MT. The Sparc parts (now headed for extinction) do 8 way multithreading but only 2 way SMT.

      IBM Power is the most interesting one. The article says 4 way MT, but it looks like they do 8 way on some parts. Is it SMT or not? IBM's performance claims indicate it is, and they deliver big parallel gains by increasing some per-core resources. IBM would be the one to do this right, with 20 more years of throughput optimization than anyone else. But they also tend to work in a space where the processor price is not very important.

      Maybe we will see higher MT counts in PC cpus from Intel and AMD some time in the future. Maybe we will see 2 way SMT in the next high end ARM generation. My crystal ball doesn't come right out and tell me, and even for a chip architect, It seems this question is tough to call.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    64. Re: Never been a fan of hyperthreading by Tough+Love · · Score: 1

      OK, this pdf sheds some light on the Power 8 question: it has 2 instruction fetch units per core, therefore does only 2 way SMT like the others, with 8 threads per core. So now I think, nobody actually does more than 2 way SMT. I will guess that dividing the superscalar resources 3 ways is just too much of a hit to justify adding more instruction fetch units. But up to 8 threads per core via TMT looks like a somewhat popular idea, we might see it show up on day in mainstream processors.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    65. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      Reminds me of a time my ex-gf came over with her new boyfriend and he pet both of my cats at the same time with one hand each... I felt sort of bested... :/ I had never before considered petting both of them at once. The double cat pet is pretty impressive...

    66. Re: Never been a fan of hyperthreading by AHuxley · · Score: 1

      Then someone is going to have to create some new software. Buy a better computer.

      --
      Domestic spying is now "Benign Information Gathering"
    67. Re:Never been a fan of hyperthreading by radarskiy · · Score: 1

      "The problem with your argument is, AMD does ship an 8 core part with SMT (I thought everybody knew that?). So Intel is doing a deliberate defeature, and you are sufficiently gullible to believe otherwise."

      The ability of AMD to get sufficient yield for an SKU tells you nothing about the ability of Intel to get sufficient yield on a different SKU. Intel can clearly make SMT parts as shown by the existence of the i9. Remember, Intel isn't making different cores for these parts.

      "This is clearly all about marketing."

      My point is not that it isn't about marking but that it isn't DRVEN by marketing. This is marketing trying to make a silk purse out of a sows ear.

    68. Re:Never been a fan of hyperthreading by Tough+Love · · Score: 1

      It's not about yield. These are all 14nm parts, a very mature node. This is about segmenting the market to extract more dollars from high end users to fund its pushback campaign against AMD at the low end. Bad luck for Intel that AMD is already out with high end 2700 for low end price.

      The 10nm node is a yield disaster for Intel, no argument about that.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    69. Re: Never been a fan of hyperthreading by Miamicanes · · Score: 1

      WinXP in general? Yes.

      WinXP DNS specifically? No.

      I don't know the exact details of the problem's root, but it basically came down to, "Someone discovered a security vulnerability arising from a race condition that could be exploited by triggering a dysfunctional DNS lookup, then trying to do something else while the first lookup was in progress". Apparently, Microsoft felt it was safe to allow parallel resolution for unrelated threads if each resolver had its own CPU, but not if they were being scheduled by the one and only CPU. Ergo, Hyperthreading, which basically added just enough hardware to kludge around Windows' own limitation (but a very useful kludge, because so many people used Windows).

    70. Re: Never been a fan of hyperthreading by toddestan · · Score: 1

      Read the fine summary. They aren't removing hyper-threading, it's just that you don't get it on the i7 - you have to pony up the cash for the i9*. Kind of like how you now generally don't get hyperthreading on the desktop i5's - you've got to buy the i7. It's just Intel playing their market segmentation games again.

      * Or buy an i3 or a Pentium or whatever where you suddenly get hyperthreading again, but less cores.

    71. Re:Never been a fan of hyperthreading by toddestan · · Score: 1

      The Coffee Lake i7's are 6 cores / 6 threads. So the i5 is basically the i7 with hyperthreading disabled, just like most previous generations. It's a near certainty they are the same silicon.

      The difference is soon the i7 will basically be the i9 with hyperthreading disabled.

    72. Re: Never been a fan of hyperthreading by Anonymous Coward · · Score: 0

      SMT is a wider concept than the Intel's HT implementation. Intel's choice of 2-way SMT is probably at least the function of latency hiding, implementation efficiency and power use. Intel's current cores have a very low latency memory/cache interface and wouldn't necessarily benefit enough from wider SMT in balance against the added implementation work and power use. Particularly considering the typical use cases of Intel's client cores, which are mostly latency sensitive, of low thread count and not consisting of a huge amount of VMs. But things can change. Xeon Phi's have a 4-way SMT implementation, for example.

    73. Re:Never been a fan of hyperthreading by radarskiy · · Score: 1

      "It's not about yield. These are all 14nm parts, a very mature node."

      A marginal design on a mature process can still have poor yield. Sometimes they can hide it a bit like slowing the frequency for long runs of AVX instructions so they don't have to lower the advertised frequency. Other times it's a bit harder to hide.

    74. Re:Never been a fan of hyperthreading by Tough+Love · · Score: 1

      A marginal design on a mature process can still have poor yield.

      There are no credible reports of that, instead Intel draws attention to how successful they have been with incremental improvements at 14nm. But there are pervasive reports, including from Intel, of problems at 10nm. You're just throwing shit at the wall to see if it sticks.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    75. Re:Never been a fan of hyperthreading by radarskiy · · Score: 1

      "There are no credible reports of that"

      I just pointed out one. They have NEVER FIXED AVX.

  2. Does hyperthreading make sense by Anonymous Coward · · Score: 1

    in a multi-core chip past 2-4?

    I guess not.

    1. Re:Does hyperthreading make sense by Anonymous Coward · · Score: 0

      If you have a workload that needs it ... yes.

      Servers of all kinds
      Rendering
      Compiling
      etc.

    2. Re:Does hyperthreading make sense by Tough+Love · · Score: 1

      in a multi-core chip past 2-4? I guess not.

      I guess it depends on your workload. Video encoding or compiling will happily consume as many processors, including simulated processors, as you have, and both are known to benefit from Hyperthreading/SMT regardless of core count. The new generation of Vulkan-style game engines will also eat as many cores as you have, assuming a well designed engine.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    3. Re:Does hyperthreading make sense by Anonymous Coward · · Score: 0

      You don't think IBM POWER does *8*-way SMT (hint: Intel's HT is 2-way) just for the heck of it, do you? Each POWER8/9 core has eight hardware threads (and would look like 8 "cpus" to Linux or Windows).

      Anything multi-threaded potentially benefits a great deal from SMT, especially when the caches are very large. Too bad neither Linux nor Windows do a decent job of only scheduling threads of the same process to sibling hardware threads, that would also defeat a lot of the speculation-related (such as Spectre) and other such side-channel issues that SMT has.

    4. Re: Does hyperthreading make sense by Z00L00K · · Score: 1

      Spreading the threads on multiple cores or multiple threads within the same core is dependent on the application which one that will yield best result. So I don't think that the OS could even make a good decision there.

      --
      If builders built buildings the way programmers wrote programs, then the first woodpecker would destroy civilization.
    5. Re: Does hyperthreading make sense by Anonymous Coward · · Score: 0

      Cinebench 11 sees about 25% improvement with ht enabled. Adding 33% more corea should more than cover the loss of ht.

    6. Re:Does hyperthreading make sense by Anonymous Coward · · Score: 1

      Yes, if you are doing anything on your PC.
      Maybe GCC is a particularly good use case for HT, but I have a 4 core with HT, so 8 logical cores, And compiling with -j8 is significantly faster than j4.

  3. Maybe they improved cache enough by Anonymous Coward · · Score: 0

    Marketing or improved latency enough no more opportunity for HT on low core counts.

  4. spectre mitigation? by Anonymous Coward · · Score: 2, Interesting

    spectre-related attacks rely on predictive execution in hyperthreading.

    could this be a mitigation, while providing improved performance so the new part still exceeds the outgoing part?

    1. Re: spectre mitigation? by Anonymous Coward · · Score: 0

      I have an i5 2500k that is quad core and no HAT.

      Seems like Intel is just offering i7's with this option now.

    2. Re:spectre mitigation? by bhcompy · · Score: 1

      I would think this is far too soon in the development cycle to have a product ready to go out the door with that level of a fundamental change at this point.

    3. Re:spectre mitigation? by Anonymous Coward · · Score: 0

      I would think this is far too soon in the development cycle to have a product ready to go out the door with that level of a fundamental change at this point.

      "No hyperthreading" just might be "hardwire it to the 'off' position" while still leaving all the transistors.

    4. Re:spectre mitigation? by viperidaenz · · Score: 4, Informative

      spectre related attacks rely on speculative execution. hyperthreading is not speculative execution.
      There are plenty of CPU's vulnerable to spectre attacks that have no hyperthreading capability. turning it off on your Intel CPU doesn't mitigate it either.

    5. Re:spectre mitigation? by Tough+Love · · Score: 1

      spectre-related attacks rely on predictive execution in hyperthreading. could this be a mitigation, while providing improved performance so the new part still exceeds the outgoing part?

      A thought that occurred to me also, but I don't think so. Intel isn't going to drop Hypthreading on all its parts, or AMD will happily kick their tail with its superior SMT implementation. This is about low power parts aimed at the ultraportable market, see my longer post in this thread.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    6. Re: spectre mitigation? by Anonymous Coward · · Score: 0

      SpectreRSB targets multiple logical processors on a single physical one, ie ht

    7. Re:spectre mitigation? by Zorpheus · · Score: 1

      Not my field, but as far as I know speculative execution is the first step, the second step is a side channel attack to get the results of the speculative execution from the cache. And hyperthreading seems perfect for side channel attacks.

    8. Re:spectre mitigation? by Zorpheus · · Score: 1

      Yeah maybe this is more about side channel attacks such as this one:
      https://www.theregister.co.uk/...

    9. Re:spectre mitigation? by Targon · · Score: 1

      To address Specter and Meltdown problems, Intel needs a more significant change to the core design, and that won't happen until 2019 or 2020. These chips won't have those fixes.

    10. Re:spectre mitigation? by Khyber · · Score: 1

      "This is about low power parts aimed at the ultraportable market,"

      Actually, no. Increasing physical core count means increasing actual power consumption. This would be a shitty move to make towards the portable market, versus just having HT on a lower core count CPU where you can keep power consumption lowered.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    11. Re:spectre mitigation? by Anonymous Coward · · Score: 0

      There's no need to speculate on this, no "might", it's a given that it's the same silicon, same die. AMD does it too on quad core Ryzen and Intel has been doing since 2010 or 2009 (i5 750 and i7 860, then i5 2500K and i7 2600K, then every CPU since)

  5. More important question: by Gravis+Zero · · Score: 2, Interesting

    Will these still need to have Meltdown and Spectre patches? If Intel are just pooping out new chips with no fix for the root cause then it's kind of a moot point to talk about it's speed.

    --
    Anons need not reply. Questions end with a question mark.
    1. Re:More important question: by 110010001000 · · Score: 1

      There is no way Intel is going to rearchitect their chips. They are just tweaking cache and clock speeds at this point. There is no reason to do anything else - they are rolling in the money.

    2. Re:More important question: by Anonymous Coward · · Score: 0

      Given the huge lead times on CPUs, there's no way they've managed to isolate and fix the root cause and get it into a finished product ready for launch. I wouldn't expect to see any architecture level changes until at least the 10th gen, maybe later. I'm sure these chips will come with the microcode mitigations already baked in, but that's about it.

    3. Re:More important question: by JenovaSynthesis · · Score: 1

      These chips were already in the making when Meltdown/Spectre were first identified. Intel locks the design of chips a year ahead of release. So of course they are not going to yank them especially when Microsoft and other vendors were taking care of it at the OS level.

      Ice Lake Chips are the ones redesigned to not be susceptible to these exploits and will be released in 2019.

      --
      Anonymous Cowards generally receive no replies because you're a coward and I'm a bitch :)
    4. Re:More important question: by 110010001000 · · Score: 2

      No they won't. Don't count on it. They will just speed up the mitigations.

    5. Re:More important question: by Tough+Love · · Score: 1

      Will these still need to have Meltdown and Spectre patches?

      Spectre, Meltdown and other speculative execution exploits can work more rapidly with Hyperthreading/SMT but they also work perfectly well with single threaded cores. Cache timings are the leakage point.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    6. Re:More important question: by AHuxley · · Score: 1

      After Ice Lake then? Will the fix just be software for a long time after 2021?

      --
      Domestic spying is now "Benign Information Gathering"
    7. Re:More important question: by Anonymous Coward · · Score: 0

      Meltdown should be fixed in hardware at some point. That is just a failure on Intel's part.
      But spectre (or other cache timing attacks) is not a real thing. The whole point of caches is to speed up memory access.
      If you want to fix that, disable caching. Better yet, fix your fucking software so you can't inject arbitrary values into array offsets.

    8. Re:More important question: by thegarbz · · Score: 1

      then it's kind of a moot point to talk about it's speed

      Why would it be moot?

      a) Talking about speed when the software fix for the problems have a speed cost is entirely relevant.
      b) Talking about a security problem that doesn't affect the vast majority of people should have no impact on speed.

      To be honest the presence or absense of Spectre / Meltdown patches will have no bearing on my purchasing decision going forward. I do not provide computers to 3rd parties to analyse my system and execute code as they please. I do not need to segregate systems via virtualisation.

      Take a breath.

    9. Re: More important question: by Anonymous Coward · · Score: 0

      Yes

    10. Re:More important question: by Anonymous Coward · · Score: 0

      Reputational damage.
      A German would say knowingly making defective products in volume is bad. No re-architecture needed - just fix the errant pipeline with hardware protection. I sense Icelake or whatever will be a divided fix - some strict application of the rules, some not. Averaging will make the fudge look better than reality.

      These flaws were also given or cross licenced to other chipsets. lets get on fixing the product. Lets hope a Intel sees a Facebook like one day drop when people see banking security trashed by a real good exploit.

  6. Can we get more pci-e lanes on the desktop? by Joe_Dragon · · Score: 2

    Can we get more pci-e lanes on the desktop?

    Not pay more or get less.

    AMD FOR THE WIN!!!!!!!!!!

    1. Re:Can we get more pci-e lanes on the desktop? by Targon · · Score: 1

      In some cases, the PCI Express lanes are a function of the chipset, not the CPU. AMD is closer to the system on a chip approach by having the PCI Express lanes having dedicated lanes right on the CPU itself. The only downside to that is that socket AM4 places limits due to the number of pins, so more PCI Express lanes and more memory channels would actually require a new socket. On the positive side, Zen2 cores will be the 2019 generation, and in 2020, even though AM4 will still be used, we may see an AM5 socket for DDR5 memory support, and with the new socket I expect there will be 4 channel memory support in the socket as well, even if lower end chips may not support that much RAM, at least the socket will support it for CPU upgrades.

      I also have a hope that we will see Gen-Z showing up in 2020 or 2021, which has a lot of potential to shake up the industry.

    2. Re:Can we get more pci-e lanes on the desktop? by Anonymous Coward · · Score: 0

      Why do you need more PCI-e lanes? Running a mining rig? Fuck you to death!

    3. Re:Can we get more pci-e lanes on the desktop? by WorBlux · · Score: 1

      Mining isn't all that bandwidth intensive. NVME and 10G+ networking are.

    4. Re:Can we get more pci-e lanes on the desktop? by WorBlux · · Score: 1

      I'm hoping for a high-clock 2 CCX threadripper part on Zen2.

    5. Re:Can we get more pci-e lanes on the desktop? by Anonymous Coward · · Score: 0

      More lanes aren't free, they cost room and money. Multiplexing done by the chipset is fine (oh noes the sound card, 1000BaseT and keyboard and a disk drive or two have to share 4GB/s!). I expect PCIe 4.0 will be used instead (on some new chips in the near future) and this will double bandwith between the CPU and chipset, and bandwith of slots.

      If you really need these lanes you can pay for them, and this won't necessarily cost thousands dollars.
      Threadripper 1900X and 2900X are an option, Intel had Xeon E5-1620v3 before and whatever newer stuff.

  7. Everyone who cares disables it anyway by jader3rd · · Score: 3, Interesting

    I know we have to disable CPU level Hyper Threading anyway. Too many false cache swaps when it's on.

    1. Re:Everyone who cares disables it anyway by Anonymous Coward · · Score: 3, Informative

      anyone who cares tests to see if they are in one of the fringe cases that gets worse performance. Far more likely to either have no effect on performance or a slight increase.

    2. Re:Everyone who cares disables it anyway by thegarbz · · Score: 1

      No, anyone who doesn't have a clue disables it anyway.

      Anyone who cares assesses their workloads against the benefits. Nearly all people who care find they are far better off leaving it on.

    3. Re:Everyone who cares disables it anyway by Anonymous Coward · · Score: 0

      Really? Because for an ESX host, or for an application which has a lot of concurrent requests but not a CPU intensive workload, hyperthreading is awesome.

      Our applications all benefit from it, precisely because concurrency is more important than raw compute power. Our database has 12 physical cores with 24 hyperthreads, and performs much better with that than it would with fewer threads. It's also got a lot of memory on it, so it's not CPU or memory bound.

      Hell, even on my own personal machine, I've got an AMD "8-core", which is really just a 4-core machine with hyperthreading .. being able to have multiple tasks running concurrently feels a lot faster, and I can be ripping a CD while playing music, surfing the web, downloading a file, running a backup, and running at least one VM. And even on the VMs, I give them two CPUs instead of one, and overall they are more responsive since the VM doesn't devolve into a single CPU single active thread situation.

      How much of a benefit you get from hyperthreading depends on the kind of workload. But for many many profiles of workload, HT actually makes for a more responsive machine capable of more concurrency.

      My personal experience is the kinds of stuff I work with benefit far more from hyperthreading than not. Obviously there will be situations where that isn't the case, but for the situations where it is a help, it's a big help.

    4. Re:Everyone who cares disables it anyway by jader3rd · · Score: 1

      No, anyone who doesn't have a clue disables it anyway.

      Anyone who cares assesses their workloads against the benefits. Nearly all people who care find they are far better off leaving it on.

      How many times do you go "I wonder if turning off hyper threading will help", and then it does, every time, before it just becomes an SOP.

    5. Re:Everyone who cares disables it anyway by thegarbz · · Score: 1

      How many times do you go "I wonder if turning off hyper threading will help", and then it does

      Very close to zero for most computing loads.

    6. Re:Everyone who cares disables it anyway by WorBlux · · Score: 1

      Not really, most real-world workloads don't have enough instruction level parallelism to make use of current Intel cores as it is. If the workload isn't strictly single threaded, and the scheduler is halfway decent, hyper-threading is usually beneficial.

    7. Re:Everyone who cares disables it anyway by thegarbz · · Score: 1

      Not really, most real-world workloads don't have enough instruction level parallelism to make use of current Intel cores as it is.

      Except for the types of workloads people would normally buy i7s for.

    8. Re:Everyone who cares disables it anyway by WorBlux · · Score: 1

      Like? I know There are a few graphics and video application than can bring the ILP needed to saturate an intel core, though hyper-threading tends to have less than a 1% penalty there. https://www.phoronix.com/scan..... The other kind of workload that doesn't benefit are can only utilize a few threads, in which case an i3 or i5 with 4 cores and an equal clock would perform just as well on the workload. The reason I bough the sylake i7 over the i5 was precisely hyperthreading to speed up compiling and the virtualization extensions.

    9. Re:Everyone who cares disables it anyway by thegarbz · · Score: 1

      Like?

      Like using any normal computer. You're thinking small if you're talking about workload. The reality is your computer is constantly doing many things. You have a single thread somewhere? It may benefit anyway while your 35 chrome processes are sitting in a wait state, defender constantly scanning things in the background, think graphics and video editing is so rare? Maybe you should actually look at your fellow people.

      Hyperthreadding may have negative impacts on single threads that peg a core when your computer is doing absolutely nothing else at all, but it benefits precisely because that use case is rare. People often complain about a lack of multithreadding and completely fail to see precisely how many hundreds of things their computer are trying to do at once just to keep the UI running smoothly in the face of a varied CPU load.

    10. Re:Everyone who cares disables it anyway by Anonymous Coward · · Score: 0

      You can do quite a lot of such multitasking on even a dual core dual thread CPU too. Even give two CPUs to the VM, in the hope it may still run better. There are schedulers to sort it out.
      I was stuck with "only" 8GB on that machine too. I would take a dual core machine with 16GB over an eight core with 8GB. But that's also because I don't care much if things get slow as long as it's reliable enough - not devolve into out of memory, permanent 100% HDD I/O, or both.
      Some CPU loads can get annoying (e.g. a VM taking 100% of a core just unzipping gigabytes of stuff, for however long?) so it's reasonable to want a better CPU still.

    11. Re:Everyone who cares disables it anyway by WorBlux · · Score: 1

      Read the thread again, I'm more disagreeing with the OP than you. Hyperthreading is sometimes useful, and sometimes neutral, and occasionally harmful.

      Graphics and video are one of the main use cases that don't really benefit from hyper-threading, because they can use all the resources in a intel core just by running one thread on it. Most production code can't. However the penalty for using it is fairly low even in those cases, and they tend to be the type of operations that are good candidates for GPU offload anyways.

      Secondly not all computers are desktops (though i5 and i7 is almost exclusively targeted as the desktop market), and we are getting into scheduling considerations. Sometimes having more hands is helpful to juggle tasks even if each hand is weaker and it's capacity is tied in a unpredictable way with a partner hand. Other times stronger individual hands that are more predictable are easier to coordinate and give better results, especially if one or tow of the balls are heavy and make up a large part of the routine. And in most applications, even multi-threaded ones there is one thread or process controlling the flow and logic of that application.

  8. Gotta cheapen those i7 chips by Anonymous Coward · · Score: 0

    How else are you going to convince suckers to buy the i9 chips. Either way, Ryzen is certainly superior.

  9. Yeah hyperthreading can go by Anonymous Coward · · Score: 0

    I will always take physical cores over hyperthreading any day. Back when hyperthreading was a thing, many tested out exactly how much it benefitted. Most of the time it really wasn't anything to brag about. Considering how much the new i7 will have in more effective performance benefits. Hyperthreading does appear ready for the heap of out dated technology.

    1. Re:Yeah hyperthreading can go by viperidaenz · · Score: 2

      HT on the old P4's was pretty shit. In most cases the overhead outweighed the benefits.
      Modern CPU's have a higher number of execution units per core now. the only way to keep them all running at once is speculative execution or hyperthreading. Using both is even better.

  10. Works for me by duke_cheetah2003 · · Score: 0

    If this is how they plan to deal with the Spectre/Meltdown issues permanently, I'm ok with that.

    It will degrade power performance I believe, since HT allowed a CPU's execution engine to stay busy flipping back and forth between the two instruction pipelines. Now you're just going to have full blown cores doing the same work. There's gunna be more dead time on these non-HT CPU's since when a CPU normally would be waiting in previous setups, it would just execute it's other pipeline, now it'll just wait.

    And the end of the day, if I can still play my games, I really don't care what's inside that hunk of silicon, as long as my games still work as good as they always have.

    1. Re:Works for me by slack_justyb · · Score: 5, Informative

      If this is how they plan to deal with the Spectre/Meltdown issues permanently, I'm ok with that.

      HT has nothing to do with that issue. That's part of the instruction pipeline within the CPU. The core of it is a thing called speculative execution, where a CPU goes and fetches things before the actual instruction hits the core. The true fix will be to detect unprivileged instructions in the pipe (because actually getting rid of the pipe is *NOT* ever going to be an option) and then act on that.

      And the end of the day, if I can still play my games, I really don't care what's inside that hunk of silicon, as long as my games still work as good as they always have.

      Yeah I think that's ultimately what matters most here so I wouldn't worry too much about it anyway, just stay up to date on patches, which I'm sure you do.

    2. Re: Works for me by Anonymous Coward · · Score: 0

      Speculative execution is when two logic branches of code are executed simultaneously. Only one will be used, but the branch may happen later. When the branch occurs the unchosen one is discarded entirely.

  11. Maybe an attempt to amp their i9 line? by slack_justyb · · Score: 3, Informative

    So to recap the 8th gen of Intel. The i7 had the most cores at six with HT enabled. i5 was just like the i7 but with HT turned off. The i3 had HT in gen 7 so it was two cores/four threads, in 8th gen they gave it two more cores and turned off HT. So: i7=6/12, i5=6/6, i3=4/4. The i9 in gen 8 was really weird. The clock would scale down the more cores you used, it was very odd and minus the fact that the 18 core version was roughly the price of a used car, it was expensive. The price per performance with the i9 was incredibly low. A 3.4 Ghz i7 would give you a better CPU mark / $ by almost 200%, not to mention that an AMD six core FX-6300 would give you better CPU mark/$ by almost 800%. So clearly the i9 wasn't going to win you an award for price sensitive consumers.

    So all that said, and this is my opinion so it's literally worth whatever value you choose to give it, I think Intel is going to reposition the line up to disable HT on all "consumer" processors and focus on just keeping HT and "pro" features in the i9. I personally think it's a back hand to Intel consumers, but I'm an AMD fanboy so full disclosure there. But yeah, I think the i3, i5, and i7 are all going to eventually be labelled as the "cheapy", "actual desktop", "gamer" CPUs in that order and the i9 is going to be viewed as "workstation" and thus the i9 isn't going to focus on price/performance balance. So, i3 will be 4/4, i5 will be 6/6, and i7 will be 8/8 with the i9 being whatever crazy numbers they throw at the chips with hopefully not any of that weird scaling core/HT/Ghz stuff.

    That's just my hot take on this, open to hear what others think.

    1. Re:Maybe an attempt to amp their i9 line? by Anonymous Coward · · Score: 2, Insightful

      "Workstation" absolutely requires ECC support. So, no, i9 ain't going workstation anytime soon, that's for the gimped try-out low-end Xeons (the Xeon E3 in the old nomeclarture, maybe they're called Xeon "Tin" nowadays? because Bronze is the low-end Xeon E5)

    2. Re:Maybe an attempt to amp their i9 line? by AmiMoJo · · Score: 1

      Just buy Ryzen or Threadripper.

      Cheaper, better, no performance crippling security flaws, and AMD CPU sockets last much longer than Intel ones so you will probably be able to upgrade in a few years without replacing mobo/RAM as well.

      Threadripper in particular gives you loads of PCIe lanes which means better future proofing too (lots of bandwidth available for that USB 4 and 9000Gb LAN card you will want in 2023). With TR or Ryzen Pro you also get stuff like hardware RAM encryption so the dream of a physically secure PC is finally possible.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    3. Re:Maybe an attempt to amp their i9 line? by thegarbz · · Score: 1

      Why would workstation absolutely require ECC support? And before you answer have a think about the benefits of ECC vs the risk you're actually mittingating working on a workstation. Not a bank, not some critical file server, but a workstation.

    4. Re:Maybe an attempt to amp their i9 line? by WorBlux · · Score: 1

      If Ryzen 2 is as good as AMD says it well be (projected to match Icelake level IPC), then not having HT on the flagship lines will backfire on Intel. AMD has consistently been great on on not using segregated features. (even if Motherboard vendors don't always enable them)

      Maybe Intel wants to simplify cores to improve yields, and having dies without HT at all lets them do that, but it's going to be at the expense of raw performance, right when the competition is closer than it's been in a long time, might not be the best move(AMD, POWER9, ARM).

    5. Re:Maybe an attempt to amp their i9 line? by Anonymous Coward · · Score: 0

      Statistician doing work on a workstation, some medical or science related work? You probably need ECC if the data is important enough, and if you're having a workstation with 256GB, 512GB RAM you won't have a choice (Registered ECC memory)

      Graphics or audio work? I don't thing you absolutely need ECC. If doing something GPU accelerated it will be common to use a gaming GPU too, which doesn't use ECC.

    6. Re:Maybe an attempt to amp their i9 line? by Anonymous Coward · · Score: 0

      They don't

  12. HPC Xeon chips always had it disabled by I_Wrote_This · · Score: 1
    ....well, they did up to a few years ago at least.

    Without it you could get better "standard" chip speeds, and it made more sense for the expected workload.

  13. Don't they disable things per chip anyway? by raymorris · · Score: 1

    I'm no CPU expert, but it's my understanding that to increase yields, Intel already disables features or entire cores that don't work right on a particular chip. If HT isn't all that useful on the new chip, and it reduces Spectre-type risks, would it not be rather easy to disable it? It can already be disabled in the BIOS, right, so disabling it doesn't require any changes to the silicon.

  14. Ever since intel stole it from the DEC Alpha by Anonymous Coward · · Score: 0

    They have been unwilling to properly implement SMT and only went for the fake version they sold as hyperthreading to get status points with the press but not actually deliver the performance possible. Apparently they feel like the press points are of diminishing value and they no longer need to maintain the charade where it's too hard on their profit margins.

  15. Stop wining, just turn if off by thesjaakspoiler · · Score: 1

    as you could have done since it was introduced decades ago.

  16. i7, i9..... by Bing+Tsher+E · · Score: 1

    AMD should simply go to i11.

  17. It's? by DontBeAMoran · · Score: 4, Insightful

    It's base clock speed is 3.6GHz

    Surely you mean "Its base clock speed is 3.6GHz" and not "It is base clock speed is 3.6GHz".

    --
    #DeleteFacebook
    1. Re:It's? by Anonymous Coward · · Score: 0

      You must get ALOT of dates dude.

    2. Re:It's? by Anonymous Coward · · Score: 0

      All your base.

    3. Re:It's? by AmiMoJo · · Score: 1

      Thanks, it's been too long since Slashdot had a good grammar nazi post. Some days it feels like no-one cares about apostrophes any more.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    4. Re:It's? by davek · · Score: 1

      After all, the crux of the biscuit, IS THE APOSTROPHE.

      --
      6th Street Radio @ddombrowsky
    5. Re:It's? by hawk · · Score: 1

      All of your apostrophes are belong to us!!! :)

      hawk

  18. More cores experiences diminishing returns by perpenso · · Score: 1

    Intel isn't going to drop Hypthreading on all its parts, or AMD will happily kick their tail with its superior SMT implementation.

    Doubtful. Increasing cores experiences diminishing returns. The difference between 8 cores and 8 cores + HT may be quite minimal except in very rare instances.

    1. Re:More cores experiences diminishing returns by Tough+Love · · Score: 1

      Intel isn't going to drop Hypthreading on all its parts, or AMD will happily kick their tail with its superior SMT implementation.

      Doubtful. Increasing cores experiences diminishing returns. The difference between 8 cores and 8 cores + HT may be quite minimal except in very rare instances.

      Those rare instances tend to the be ones you care about, like compiling or video encoding. If you don't care about performance then by all means accept a wimpy processor, it's right for you.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    2. Re:More cores experiences diminishing returns by perpenso · · Score: 1

      Intel isn't going to drop Hypthreading on all its parts, or AMD will happily kick their tail with its superior SMT implementation.

      Doubtful. Increasing cores experiences diminishing returns. The difference between 8 cores and 8 cores + HT may be quite minimal except in very rare instances.

      Those rare instances tend to the be ones you care about, like compiling or video encoding. If you don't care about performance then by all means accept a wimpy processor, it's right for you.

      Actually compiling would not be one of those rare instances. I/O and RAM are also huge factors. And again, **diminishing returns**, 8 core vs 8 core + HT will probably be less helpful than 2 vs 4 cores or 4 vs 8 cores. 8 cores without hyper threading is not wimpy.

    3. Re:More cores experiences diminishing returns by Tough+Love · · Score: 1

      Increasing cores experiences diminishing returns. The difference between 8 cores and 8 cores + HT may be quite minimal except in very rare instances.

      Those rare instances tend to the be ones you care about, like compiling or video encoding. If you don't care about performance then by all means accept a wimpy processor, it's right for you.

      Actually compiling would not be one of those rare instances. I/O and RAM are also huge factors.

      You have it exactly backwards. The more RAM accesses you have, the more SMT helps. And I/O has almost nothing to do with SMT because the OS takes care of that... a thread waiting for I/O is not running, or in other words, not in any CPU core, so not affected by SMT.

      And again, **diminishing returns**, 8 core vs 8 core + HT will probably be less helpful than 2 vs 4 cores or 4 vs 8 cores. 8 cores without hyper threading is not wimpy.

      You are talking nonsense. I get my fastest compiles with 8x2 SMT cores, exactly what I my Ryzen part gives me. I just don't care about your other comparisons, they look like smokescreen to me. A decent compiler (gcc, llvm) will use as many cores as you have. You just tell it how many threads you want and away it goes. Compiling is embarrassingly parallel, it approaches best case for SMT. Linking was a serializing bottleneck historically but there is no good reason for it, and is now largely fixed.

      Your evident confusion coupled with confident pronouncements that are flat wrong is a little concering. Is this somehow normal for the circles you move in?

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    4. Re:More cores experiences diminishing returns by Aighearach · · Score: 1

      Intel isn't going to drop Hypthreading on all its parts, or AMD will happily kick their tail with its superior SMT implementation.

      Doubtful. Increasing cores experiences diminishing returns. The difference between 8 cores and 8 cores + HT may be quite minimal except in very rare instances.

      Those rare instances tend to the be ones you care about, like compiling or video encoding. If you don't care about performance then by all means accept a wimpy processor, it's right for you.

      No, only people with giant bushy neckbeards care about those things these days, for everybody else it is fast enough. Video encoding doesn't need to be fast for normal use cases. And slow compilation isn't really improved by a faster CPU; everybody else who has to compile it will still complain about your sucky code and insufficient build system, if it is actually slow in a use case where that matters.

    5. Re:More cores experiences diminishing returns by Tough+Love · · Score: 1

      The performance processor market is clearly not for you. For those of us who do care about performance because time equals money will continue to invest in high performance equipment. A rubbernecking bystander such as you should be perfectly fine with an Atom, it will suit you perfectly.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    6. Re:More cores experiences diminishing returns by perpenso · · Score: 1

      Actually compiling would not be one of those rare instances. I/O and RAM are also huge factors.

      You have it exactly backwards. The more RAM accesses you have, the more SMT helps.

      You misunderstand, its the amount of RAM that can greatly effect compilation speed.

      ... And I/O has almost nothing to do with SMT because the OS takes care of that... a thread waiting for I/O is not running, or in other words, not in any CPU core, so not affected by SMT.

      You misunderstand, its the amount of I/O that can greatly effect compilation speed.

      And again, **diminishing returns**, 8 core vs 8 core + HT will probably be less helpful than 2 vs 4 cores or 4 vs 8 cores. 8 cores without hyper threading is not wimpy.

      You are talking nonsense. I get my fastest compiles with 8x2 SMT cores, exactly what I my Ryzen part gives me. I just don't care about your other comparisons, they look like smokescreen to me. A decent compiler (gcc, llvm) will use as many cores as you have. You just tell it how many threads you want and away it goes. Compiling is embarrassingly parallel, it approaches best case for SMT. Linking was a serializing bottleneck historically but there is no good reason for it, and is now largely fixed. Your evident confusion coupled with confident pronouncements that are flat wrong is a little concering. Is this somehow normal for the circles you move in?

      Again, you evade the point, **diminishing returns**, and substitute a different goal, "faster", and offer an apples and oranges comparison, Intel v AMD.

      Merely saying faster with HT than without is not a meaningful counterargument. If you want to have a meaningful counterargument you might compare an Intel 8 core with hyperthreading enabled and disabled (again the same physical CPU), and an Intel 4 core vs an Intel 8 core. Oh, and please do so with a large software project, something that would take 10+ minutes to compile. In such projects improvements are somewhat linear when threads equal physical cores but when there are multiple threads per core (ie Hhyperthreading) the improvements drop off dramatically. Going from 4 cores to 8 might show a 60% improvement but 8 non-HT and 8 HT might only show a 10% improvement.

      And again, the point I am trying to make is not what is fastest. What I am trying to convey is that dropping hyperthreading is not necessarily a big deal when you are starting with a CPU that has 8 physical cores due to diminishing returns.

    7. Re:More cores experiences diminishing returns by bluefoxlucid · · Score: 1

      It'll be the gaming crowd with $1,000 CPUs they're going to replace in 4 months with another $1,000 CPU talking about how many AIs and individual bullets they can have on-screen at any given time without lag.

    8. Re:More cores experiences diminishing returns by Anonymous Coward · · Score: 0

      Does it seriously hurt to be as cuckold as you?

    9. Re:More cores experiences diminishing returns by Khyber · · Score: 1

      "For those of us who do care about performance because time equals money will continue to invest in high performance equipment."

      WRONG. Those who care about performance learn to code at the bare metal level and OPTIMIZE. Meanwhile, you keep using shitty bloated high-level languages that need so much beefy hardware because y'all don't know how to code for shit.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    10. Re:More cores experiences diminishing returns by Tough+Love · · Score: 1

      Those who care about performance learn to code at the bare metal level and OPTIMIZE.

      Whoosh. Those of us who code professionally want to do it on fast hardware so we don't waste our own time.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    11. Re:More cores experiences diminishing returns by Anonymous Coward · · Score: 0

      You forget something. When the avenues for increasing system performance narrow (as they have), that puts pressure on the programmers. Parallel scaling efficiency has lagged because that is more complex coding work and easier wins have been available.

      Upgrading software to perform better in parallel is becoming ever more important. We are nowhere near any practical or theoretical ceiling on how many parallel tasks should be supported.

      How do I know? I used to work on a system that achieved ~97% scaling efficiency. Far better than x86/x64.

    12. Re:More cores experiences diminishing returns by Khyber · · Score: 1

      Fail. That's what you're charging extra for. You think if I'm doing line drops I'm just charging per drop? Hell no, there's a time rate included.

      You also need to learn how to sell yourself on top of learning low-level coding.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
    13. Re:More cores experiences diminishing returns by Aighearach · · Score: 1

      That is exactly, literally, what I said.

    14. Re:More cores experiences diminishing returns by Aighearach · · Score: 1

      People who write code, don't write it faster or slower if it is going to run on a faster or slower piece of hardware. That is daft.

      You don't even realize you called your own bluff! *ROFLCOPTER*

      Is this the 1970s and people only know how to scale vertically? Give me a break.

    15. Re:More cores experiences diminishing returns by bluefoxlucid · · Score: 1

      You cited video encoding not being fast (for streamers, it does) and source code compilation, trying to describe a tiny segment of the population who are engaged in nerd things. That seems to exclude consumers of something called "entertainment", who make up a rather large market segment: the video game industry is over twice the size of the film industry.

      Unless you want to suggest that movies only appeal to a vanishingly-small sector of the market--so much so that video games don't count as anything significant to the PC industry at large--you've got to account for those $1,000 CPUs becoming the new $200 CPU a year down the line, at which point they suddenly matter to your average PC gamer. They don't matter to your average secretary, who still won't use the bazillion cores in last year's top-end CPU to make Microsoft Word run any faster.

      If you're putting SMT and non-SMT next to each other this generation, only those super-elite gamers who buy tons of bullshit will care...this year. Next year, it's going to be everybody else.

    16. Re:More cores experiences diminishing returns by Aighearach · · Score: 1

      Personally, I'd hope that I'd be able to either spend a bunch of time writing optimized code for bare metal, or else implement algorithms quickly using a high level language, as the use case dictates.

      The embarrassingly horrible part was only where he claimed that the programmer needs the code to run on powerful hardware in order to meet a "time equals money" type of argument. Whose time equals money? The CPU's time? Or the programmers? And if the solution needed to be performant, would that normally be done with a faster processor, or by horizontal scaling? Somebody who wants a faster processor is putting a very hard upper cap on how fast the solution can run! Whereas using modern scaling methods, the same code can run on a faster processor while you have one, or be distributed when it outgrows the training wheels.

      Pretty much the only time where you can't increase performance by horizontal scaling is when you need to go bare metal, and the solution with the lowest latency might be an 8 bit microcontroller that actually has low total throughput.

    17. Re:More cores experiences diminishing returns by Aighearach · · Score: 1

      Watching movies not only doesn't require high-end hardware, it doesn't even require hardware built within the past 10 years.

      Even 10 years ago, watching a DVD used almost no system resources, and didn't require shutting down other programs. You could recompile a linux kernel, and watch DVDs. At the same time.

      And yes, I do put surface mount technology next to through-hole, wtf are you talking about? (Don't use acronyms you didn't introduce)

      And yes, if games required a $1000 CPU, they would not be a mainstream market. They are a large mainstream market precisely because regular computers play games just fine; even a regular computer that is a few years old, plays games just fine.

    18. Re:More cores experiences diminishing returns by bluefoxlucid · · Score: 1

      Watching movies not only doesn't require high-end hardware, it doesn't even require hardware built within the past 10 years.

      Reading comprehension: the gaming industry is bigger than the entire film industry--theater, DVD, everything. If watching movies is a significant use case for a PC, then gaming (which does benefit from huge processors with many cores and SMT) is an even more-significant use case.

      wtf are you talking about? (Don't use acronyms you didn't introduce)

      Simultaneous multi-threading. It's branded as "Hyperthreading" in Intel chips and as something else in AMD. It's the name of the technology, like SMP is symmetric multi-processing (multiple physical CPUs). It's the topic at hand.

      Would you like a definition of CPU, too?

      And yes, if games required a $1000 CPU, they would not be a mainstream market. They are a large mainstream market precisely because regular computers play games just fine;

      This year's regular computer has a CPU similar to last year's $1,000 CPU. This year's neckbeards have next year's everyday hardware. Do you think Intel's going to spend hundreds of millions to design a new CPU without shoving it through the large-margin pipeline first?

    19. Re:More cores experiences diminishing returns by Aighearach · · Score: 1

      Watching movies not only doesn't require high-end hardware, it doesn't even require hardware built within the past 10 years.

      Reading comprehension: the gaming industry is bigger than the entire film industry--theater, DVD, everything.

      Stopped reading right there. That's just daft.

      First of all, it isn't even close to true.

      Second of all, you don't seem to comprehend what I said. If you needed a high end computer to play video games, that industry wouldn't even be the size of one large local television market. When they talk about video games being big money, most of that money is from things similar to Angry Birds. Don't be such a tool.

    20. Re:More cores experiences diminishing returns by bluefoxlucid · · Score: 1

      First of all, it isn't even close to true.

      Gaming industry revenue, 2017: $108 billion.

      Film industry revenue, 2017: $40.3 billion at the box office, globally. $20 billion home video consumption, globally. Yes, that's $60 billion for video--only $20 billion of which might be consumed at home.

      If you needed a high end computer to play video games, that industry wouldn't even be the size of one large local television market.

      You don't need today's high-end computer to play video games; you need last year's high-end computer. The CPU design process costs a lot of money, and CPUs are at best tweaked a bit as new low-end processors come out.

      I bought a Chevy Volt. I paid $12,000. It was $40,000 new; they depreciate fast.

      You bought a $300 CPU. It has the same specs as a $1,200 CPU did at the end of 2016.

      So imagine that $300 CPU in 2020 is descended from a $1,000 CPU that has lower specs. Things that didn't matter to anyone except a few folks in 2019 suddenly matter to everyone in 2020, and aren't being delivered because the new 2020 basic CPU is 2019's crippled high-end CPU.

      When they talk about video games being big money, most of that money is from things similar to Angry Birds

      Global mobile game revenue was $40 billion of $108 billion total . That leaves $68 billion of non-mobile game revenue--more than the box office and home movie industry drew in total.

      The CPU in mobile phones now contains a high-end GPU and 8-core asymmetric hybrid multi-processing. That means it runs 4 cores at high clock (2.1GHz) and 4 cores at low clock (500Mhz) and very low power consumption (like 1/100 as much), either being able to run 8 all at once or able to run any individual core as one or the other. Old mobile processors had to switch all cores to a high or low mode simultaneously.

      To put this into perspective: the OnePlus One is four years old. OnePlus released the SIX in May. That's from 166GFLOPS to 737GFLOPS on the GPU, and from a quad-core 2.5GHz to an eight-core 2.8GHz and 1.8GHz asymmetric CPU architecture. Four years.

      The cheap phones are going to have these chips next year.

    21. Re:More cores experiences diminishing returns by Aighearach · · Score: 1

      I'm not going to read all that, because you put lies at the start.

      You said the whole movie industry, everything, and then you quoted only the small parts that they put on the teevee newsvertainment shows. It is just idiocy; you're using numbers that even include game hardware, but are you including video hardware like DVD/BR players? No. No you're not. Your numbers include merchandising tie-ins for games, but you're not including that for movies. If you do apples to apples, the game industry isn't just a little bit smaller, it is way smaller.

      I'm assuming the rest of your analysis is of similar qual-i-tay.

  19. Workloads may shift to GPU by perpenso · · Score: 1

    With GPUs relatively ubiquitous some (many ?) of these workloads may just shift to the GPU.

    1. Re:Workloads may shift to GPU by Tough+Love · · Score: 1

      I was talking about GPU, This is what somebody means when they say "Vulkan". Hint: if you don't know the words then google before you post.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    2. Re:Workloads may shift to GPU by Anonymous Coward · · Score: 0

      Vulkan is a "3D graphics and compute API". It makes better use of multi core CPUs than DirectX and OpenGL. Why would you be talking about GPU cores when the article is about CPU cores?

    3. Re:Workloads may shift to GPU by Tough+Love · · Score: 1

      You still need multiple CPU cores to drive the GPU efficiently, that is the entire point of Vulkan. If either CPU or GPU is not fully utilized at peak load then your hardware configuration is not optimal for the load.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    4. Re:Workloads may shift to GPU by AHuxley · · Score: 1

      Depends on the software, the code, the limitations of a consumer GPU and the CPU math thats supported for the task.
      A game supporting consumer GPU that needs really great code may not always be the best for a given math task.

      --
      Domestic spying is now "Benign Information Gathering"
    5. Re:Workloads may shift to GPU by perpenso · · Score: 1

      Depends on the software, the code, the limitations of a consumer GPU and the CPU math thats supported for the task. A game supporting consumer GPU that needs really great code may not always be the best for a given math task.

      True but the parallelization can go way beyond the 8 threads of the CPU, that can make up for a bit a relative inefficiency.

      I'm thinking of some consumer tasks that lends itself to parallelization, like image processing.

    6. Re:Workloads may shift to GPU by perpenso · · Score: 1

      I was talking about GPU, This is what somebody means when they say "Vulkan". Hint: if you don't know the words then google before you post.

      Actually you were talking about both CPU and GPU, and your reference to Vulkan was game specific. I am referring to some non-gaming tasks that can also move to the GPU.

    7. Re:Workloads may shift to GPU by Anonymous Coward · · Score: 0

      GPU's ubiquitous? maybe in your home PC's. they are just about non existent in workstations or servers unless they have a very specific need for them.

    8. Re:Workloads may shift to GPU by Tough+Love · · Score: 2

      I am referring to some non-gaming tasks that can also move to the GPU.

      Some can, most can't. Many parallel loads could in theory be ported to GPU but this is a specialized, prohibitively expensive engineering task. Many parallel loads do not parallelize at the SIMD level. Without SIMD, a GPU becomes a fairly small number of low-clocked and non-superscaler CPUs with crappy branching characteristics and severely limited cache, basically turning the GPU into a decellerator. For these and other reasons, the vast majority of parallel loads will stay on the CPU for the forseeable future.

      --
      When all you have is a hammer, every problem starts to look like a thumb.
    9. Re:Workloads may shift to GPU by AHuxley · · Score: 1

      It can be a risk if the CPU, GPU maker suddenly drops support for something in a past generation of hardware that made the math work great.
      How much money, skill and time for software can go to a part of GPU, CPU that can totally change in a year?

      --
      Domestic spying is now "Benign Information Gathering"
    10. Re:Workloads may shift to GPU by Anonymous Coward · · Score: 0

      Nicely put.

  20. not all of them! by Anonymous Coward · · Score: 0

    only some. the highest-end part in that line (i9-9900K) is still shipping with ht.

    the decision is likely the result of not getting enough 'perfect' dies off their fabrication process and absolutely nothing to do with the known flaws in the architecture (which may or may not be partially mitigated by disabling ht)

  21. I see your grammar nazi-ism and raise you... by Anonymous Coward · · Score: 1

    It was a quote from the original ArsTechnica article so surely it was meant to be "It's [sic] base clock speed is 3.6GHz...". It looks like it was fixed in the original article though (or it was correct to begin with and copied incorrectly, in which case double shame on BeauHD)

  22. If you're a low end gamer it's a god send by rsilvergun · · Score: 1

    You can buy a $99 dollar processor with decent single thread performance and not have to worry about games that require 4 threads.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  23. It's not "it's", it's "its", dammit by Anonymous Coward · · Score: 0

    > "It's base clock speed is 3.6GHz..."

    Yeah. Now call me grammar nazi. Then I'll say "Hitler". Then this thread be Goodwin'd.

  24. On my 1950X with 16 cores.. by Anonymous Coward · · Score: 0

    Having SMT enables gives lower performance in almost every workload, only specifically parallel tasks (computational tools) or Cinebench benefits.

  25. Spectre by Anonymous Coward · · Score: 0

    It is the best way to stop the page table bugs.

  26. Was HT turned off and all this is a hoax? by Anonymous Coward · · Score: 0

    You may easily turn off HT in BIOS and Sandra will be none-the-wiser. This may be a test of an engineering prototype or R&D sample that is not aimed for mass production. Or it could be faked by most anybody - it is quite easy to submit fake SSS reports.

    In a nutshell, we have no idea what the conditions of the "leaked" sandra report were, so this article is pure speculation.

  27. No hyperthreading by Anonymous Coward · · Score: 0

    I will not buy a processor without hyperthreading.
    intel is dead long live AMD

  28. Intel by Anonymous Coward · · Score: 0

    This is their fix for melt down and Spectre. Cripple the CPU. Hyperthreading is just speculative execution. Instead of doing the right thing and creating rings they cut the branch prediction and speculative execution out of the CPU Core. They're hoping the increased CPU clock will offset the performance loss of doing this. I hate to say it, but Intel is fucked. I hope AMD is able to continue development on this technology. It is going to take a complete redesign, something Intel doesn't want to do.

  29. Intel confusion with product branding by Targon · · Score: 1

    From Intel, it has been confusing for a long time. Is a CPU 2 core/2 thread, 2 core/4 thread, 4 core/4 thread, 4 core/8 thread, 6 core/6 thread, 6 core/12 thread, or now, 8 core/8 thread, or 8 core/16 thread? The name alone does not really tell you much, so doing a lookup online is needed. To make it worse, the U series of chips has tended to be dual-core, even if it is branded as an i7.

    In general, we have seen the i3 line cover the 2 core and up to the 4 core/4 thread mark(as of the 8th generation i3, the i3 can now be a quad-core chip). i5 has generally been either 2-core/4 thread, or 4-core/4-thread, though with the 8th generation, we are seeing 6 core/6 thread. i7 has been your 4-core/8-thread chip, or 6-core/12-thread. Once 8 core chips came into the picture, suddenly Intel added the i9, and things got really messy, because now, the 6-core/12 thread falls into the i9 range, 8 core/8-thread falls into the i7 range, and 8-core/16-thread will also be i9. This idea of "some chips get HyperThreading and some don't" is what makes it a mess. If it were a simple case of i3 is 4 core/4 thread, no Hyperthreading at all, then saying 4 and 6 core without HT being i5, i7 being 4 and 6 core with HT, and then the 8 core being i9, that would make more sense, make the version with HT have a H at the end of the name, the version without not having the H...it would make it easy to keep track of.

    Intel may simply be playing the game of, "sell a crap chip in machines with an i7 brand" to improve sales of crap chips, but it will upset users when their i7 branded laptop with only two cores runs worse than an i5 with 4 cores.

  30. Not that long ago games only used a few threads by Babel-17 · · Score: 1

    I remember when Intel released its "Core 2" lineup some gamers eschewed getting the quad core ones because the dual core CPUs clocked higher, were less expensive, and most games only used one or two threads. Given how popular the slighter older i7s (4 cores, eight threads) and i5s (4 cores) have been, and how prominent they are in populating gaming PCs, it seems doubtful to me that any PC game will be incapable of running blisteringly fast on 8 physical cores. Games running on an i5 6600k/i7 7600k, with just four cores, generally go fast enough even for gamers running monitors at high refresh rates. https://www.pcgamesn.com/intel... https://www.pcgamer.com/intel-... These new CPUs will more than double their performance, and given the enormous number of customers for games with older i5s and i7s it's hard to imagine any game developer with an eye to sales who'll think that "Too bad, it's 16 threads or bust!". Non-gaming applications have been impressive in their improving on the ability to make use of more threads, but even there there are often diminishing returns, and it will be the pro's, and serious semi-pro's, who notice the savings in time by going to 16 threads (or more). But my point here goes to gamers/power users of the PC. For many of them, myself included, eight physical cores represents the opportunity for a solid upgrade. Though personally, I'd be a lot more excited if this was on 10 nanometer, it ran cooler when getting stressed, and it used less juice under all circumstances. At 10 nm it would be gold. As is, I think a lot of people will wait and see for what's on the horizon.

  31. I've always been a fan of hyperthreading by OrangeTide · · Score: 1

    If you're bound by memory I/O or limited by cache then something like hyperthreading won't improve throughput and will probably make it worse. But even in that case you can have better fairness between threads and less bursty behavior at high load when doing hyperthreading.

    Even in an optimal case total throughput doesn't improve very much with hyperthreading. So results are disappointing if your only performance metric is how many operations you can perform a second or how much memory bandwidth you can blast through. I don't see much value in hyperthreading for a desktop user that has relatively few ready tasks at any given instant (often in single digits and low double digits), especially now that quad core is pretty commonplace. When your ready tasks is many times your number of cores, you will need to context switch often to distribute the work fairly.

    On a server where you do have lots of tasks ready to run (sometimes 100+), having 2-way or even 4-way SMT is way cheaper than adding more cores (less silicon area, less power, reduced bus infrastructure, etc). Even if an individual thread runs more slowly because of hyperthreading sharing resources of a CPU, not having to context switch as often is a net gain.

    tl;dr - hyperthreading is not a panacea.

    --
    “Common sense is not so common.” — Voltaire
  32. For gaming, I'm actually going AMD next time by Anonymous Coward · · Score: 0

    AMD was shit for games for a good while, but Intel got sloppy.

    I went from a 2500k to a 7700k. Not happy with it; too hot, and Intel said to not OC it (what's the point of buying the K series then?).

    Plus it looks like the z270 chipset (7700k) is essentially the same as the z370 chipset (8700k), but z270 doesnt support 8X00 series CPUs. (Of course this is standard for Intel, but it's still lame.)

    Intel... you done goofed too many times. Your CPUs need to absolutely destroy AMD's in gaming to win my next purchase.

    1. Re:For gaming, I'm actually going AMD next time by Anonymous Coward · · Score: 0

      7700K is like it's factory-overclocked. Tons of MHz and GHz already. Your option is be pretty much to delid it (do heatspreader surgery and replace thermal interface material with some with high performance)

  33. I Don't Really Care by Anonymous Coward · · Score: 0

    While I totally get that a hyperthreading core isn't as good as a real core, who cares? The system gets 20% faster with those HT cores and I'm happy to take the 20% performance advantage.

    Also, if Intel takes HT out of the i7 line... I don't think I care. As long as they add in real cores to replace them it's all good. They don't even have to replace HT cores with real cores on a 1:1 basis, just add enough real cores to make up for the missing HT cores, plus some extra to continue growing the value add for tech progress and to keep some notional parity with AMD offerings.

    I don't think it helps much for tech analysts to obsess too much about where their CPU performance comes from. As long as each generation is better than the last generation, what does it matter whether it is due to more/better cache designs, more cores, faster DRAM subsystems, HT, better CPU interlinks, more efficient IPC, specialized CPU subsystems, new CPU instructions, etc.?

    With Dennard Scaling slowing down, we have much bigger fish to fry than whether i7 = HT.