The airport part was the best hyperthreading explanation I've ever seen. Good job

That example was really made it easier to understand. Thumbs up from my side :)

This channel is arguably one of the best when it comes to explaining computer concepts. Gary you the best.

Helpful as always, thank you Gary Sensei.

Great video, like the drawings, amazing as always - thank you Gary 😇

Again .. what a great demo Gary .. really good job

I just love your explanation 😊 Sir Gary

This was a really great explanation. Love the fact that you took the airport example and in the end compared the 6C/12T vs 8C/8T speed differences. There has been a lot of talk around the next gen Intel CPU with "only" 8C with no HT vs the current 6C/12T CPU. For some it does not make sense, while for me it makes perfect sense. :-) Keep them explanations coming!

Thanks again for unpacking this

Gary, as always, great explanation and information.

The best hyperthreading explanation I've heard so far, thank you! Thumbs up!

Wow, the best way to explain these CPUs ever. Thanks again Gary for the great work.

Thanks... superb explanation

Great video Gary. 🔥

Thank you again Professor! Wonderful video... lesson learned!😎

How have I not heard of this channel. Actual useful, correct info on technology he deserves over a million subs.

This is amazing thank you sir.

Great explanation

Awesome explanation as always. This channel is so underrated. Hope it gets larger than other so called "tech" channels that talk about things like how animation in one phone is 10ms faster than it is in another phone. One suggestion: please don't use handwriting animation (with fake hand) - it is little distracting. Thanks!

Very good explained

Very nice explanation

This channel is underrated. Subscribed.

Great video, thank you

best explanation so far...thank you!

The best instructional video i've seen in a while! lots of love for this channel. God bless you more Gary ! :)

As always, awesome explanation Gary. I would say you wore born to teach tech. :) You're helping lots of people. Thank you.

the example with the airport security check is just simply awesome. thank your very much :)

Very nicely explain and the examples are awesome. Please explain us the concepts of SOCKETS. And how cores are divided among SOCKETS and how it works. Please give us some ideas on it. Thanks a lot !!!

Omg, airport security checks example…. How brilliant! You are gifted at this, Sir! No one explained this better than you. I am preparing my CompTia A+, I got to subscribe your channel

This channel should get a million sub ASAP. so through so good video. good job man. :)

Appreciate your work man ❤️..

Thank you so much

Thank you, sir.

Loved the Airport analogy - really brilliant observation and clean way to explain hyperthreading contention.

What a great analogy on the airport queue!

this is awesome

this is one of the best video for me on UKposts and the way you have explained it made me very happy :). Can you please also helps us explain how "Intel Virtualization Technology" works. We are great full to see all your videos.

Very clear explainations! The airport example was the best♡💯

Nice one

Hello Gary, I like your analogy with the airport queue, it is a very good illustration of one of the uses of hyper threading. However, you may have forgotten (or maybe is it too technical to be explained in the same video?) the case of super scalar architecture where you have multiple ALUs in each core, which allow two threads to actually execute at the same time on the same core. It may be a subject for an other video? Keep on with your videos, I love them!

thank you your example helped me finally get the idea of it lol

When I see Gary Explains notification I know that is quality content awaits.

In short : *4C/4T* is better than *2C/4T*

Wow, this is the best hyper threading explaining video I have seen! I have some IT background but not Computer Science. Can you tell in a PC, what will a "queue" to have problem that affects it to fetch instructions into a CPU? Apart, will there is cases that hyper-threading will cause decrease in performance?

Hyperthreading helps mitigate data dependencies within a thread. To illustrate. Assume you have a superscalar processor that can execute up to 4 instructions per clock cycle. Unfortunately, most code can't take advantage of that due to data dependencies. An example would be this expression: A = B + C + D + E There's 3 additions there, so in theory, only one clock cycle is required since the processor can perform 4 instructions per clock. But that isn't so. The above could be compiled into something like this: 1. A = B + C 2. A = A + D 3. A = A + E And if you look at the above 3 instructions, you'll see that #2 can't execute until the result of #1 is known, and #3 can't execute until the result of #2 is known. So the above code sequence would take 3 cycles with an average of only 1 instruction per clock. Now a clever compiler can mitigate that somewhat. For instance, look at the following code sequence: 1. T1 = B + C 2. T2 = D + E 3. A = T1 + T2 For the above, #1 and #2 can both execute at the same time since they don't depend upon each other. But #3 has to wait for the results of #1 and #2 to be completed. So the above sequence takes only 2 cycles for an average of 1.5 instructions per clock. Now, let's make the following assumptions. 1. We have a super scalar processor capable of executing up to 4 instructions per clock. 2. Our code on average can only execute 1 instruction 50% of the time, 2 instructions 25% of the time, 3 instructions 12.5% of the time, 4 instructions 6.25% of the time, 5 instructions 3.125% ..... With the above assumptions, the processor will on average execute 1.875 instructions per clock for a total utilization of 47%. Now the goal is to make it faster. We could add extra logic and make is capable of executing up to 5 instructions per clock, which would raise the average instructions per clock to 1.9375 which is an improvement over the 1.875, but it's a fairly small improvement. But if we add an entirely separate set of registers and have it execute an independent thread which has no data dependencies with the first thread, we get an average of 3.25 instructions per clock for a 81% utilization. Unfortunately, each thread drops its performance to 1.625 instructions per clock, but the overall system performance does increase significantly. The reason each individual thread slows down is because they're no longer capable of having 4 instructions execute because the other thread is executing 1 instruction. Also some of the time when a thread would be capable of executing 3 instructions is lost because the other thread is executing 2 instructions. But the loss of going from 1.875 to 1.625 is fairly modest while the increase of system performance of going from 1.875 to 3.25 is quite significant.

this is one of the best tech channels...gj

Thanks

Excelent.

Well done, I think even normal people will understand this 👍🏻

You learned me a lot with your videos and info. Thank you man so much ❤

*GARY!!!* *Good Afternoon Professor!!!*

I am going to take a refresher course to remember what I have learned in the past. Now I remember again what multithreading and hyoerthreading is all about. Old age can make one forgetful from time to time. Especially at age 93!

Sun's UltraSPARC architecture took this to extremes, with up to 8 threads per core and making cache misses almost a feature. Early versions even shared a single FPU among several cores. Needless to say, everything was sacrificed to maximise aggregate throughput with low power consumption and single thread performance was dire. I had lots of "interesting" meetings with senior management who had been over-sold UltraSPARC and demanded to know why we weren't using more of these apparently cheap machines for a lot of their projects, and there were some disastrous examples where the wrong choice was made. This was nothing like the same issue with Intel hyper-threading as Intel did not sacrifice things like cache size, out of order execution and so on, but the non-linear throughput with (apparent) CPU utilisation could cause some confusion in capacity planning. If half the threads were idle, it did not mean there was twice the potential throughput when on a hyper-threaded machine.

*MultiThreading v.s HyperThreading:* Multithreading refers to the general task of running more than one thread of execution within an operating system. Hyperthreading, on the other hand, refers to a very specific hardware technology created by Intel, which allows a single processor core to interleave multiple threads of execution more efficiently.

Excellent, as always! 👌 Well explained, without going into too much detail 👍 P.S. Hope you don't mind my asking - do you prefer Mr Sims, or Gary? :) Cheers!

Sir please make a video on how to enable hyperthreading

Thanks! Can you explain more about the instruction pipeline?

Is it possible for you to make series a on : 1. Evolution of computer it's hardware from difference engine to 4th gen computer. 2. Computer software - first operating system - current operating system. 3. Evolution of networking to Internet. I tried to find the information but it's unstructured and I can't connect the pieces. But I am too interested to know about it. So can you please explain.

I was wondering what the hell is hyperthreading when almost every tech youtuber was like intel i7 9700k is dropping hyperthreading. Now I have a better comprehension. thanks professor gary.

great video! נהדר! (Great in Hebrew)

Thanks.

Outside of queuing, one of the things that hyperthreading does is it saves an expensive context switch. Unloading the registers and loading from RAM is expensive.With hyperthreading you have more threads and reduces the need for a context switch. One day CPUs will probably have the ability to hold all OS threads within its registers, it will probably coincide with ARMs rise.

OOh, I just harped on some terminology on another vid of yours and I hesitate to say it and sound like a broken record but I really do need to jump on you for the title here in honor of my former professor who actually came up with the idea herself and who the conflation of this term rankled so much she actually flinched in class over it. What you are describing in such general terms is "Simultaneous Multi-Threading" whereas "Hyperthreading" is Intel's implementation of it. Yes, i'm proud to say that Susan Eggars was my professor and she was phenomenal.

Hey Gary, Can you make video on Difference between SELinux and Linux ?

When you Turn of HT in i5 11400f, benchmark in CPU-Z shows more points in single thread . Some games behaving the same - strong single tread is better for them

could you please explain CPU over commit with Hyper threading as well ?

I think the process descriped in the video is more comparable to temporal multithreading than simultaneous multithreading (or hyperthreading)

Gary, How does the CPU keep track of which instruction belong to which thread? Are the instructions tagged with a thread number in some manner? Do they use some kind of shadow registers? If say a load instruction of thread 1 puts a value in register A, but the thread 2 actually needed that register for the next operation it is pushing through the core, how do we deal with that? Does it have some sort of shadow registers? Or can the thing picking instructions from the pipeline somehow sort or stall instructions based on whether they are touching registers already occupied?

well i cant find hyper threading technology in bios, what should i do to turn it on??

@6:01 That is the advantage of a Xeon E3 1231 V3 over an I7 4470, hyperthreading, in case you use it for gaming and it is cheaper if you buy it used. ;) @6:48 Ah, so my example is a good because the architecture is basically the same and the clockspeed is the same.

Hiii !!!! Hello !!!! Very good evening professor!!!!!!!! Very good video !!!!!! Thanks professor!!!!

Good.What is quantum computer?

Does a program need to be a multitasking/multithreading support program?

ok, ok, I get most of this, but I am confused about multi core CPU's, it seems like they would bottleneck as well at the "scanner" somewhere like the threads to, right? If you have 4 cores, aren't the results or outputs being sent out to the same "highway" or bus as the other cores? I am guessing memory clock speeds need to be faster than the CPU to keep things moving?

Hay sir... what the different beyween 32bit processor and 64bit processor.. and why there is 32bit operating system and 64bit operating system... i hope you make a vide o of it.. thanks

Are there single-core CPUs with hyperthreading? And are there hyperthreading CPUs with more than two threads per core? Thank you.

let's make it simple.. more core more thread the higher the speed,, plus features of hyper threading or virtualizaion technology is according to your needs..

I thought you would also mention vCPUs in all this and how it relates to hyperthreading.

What are we gonna do if we cant use hyper threading anymore intels cpu flaw says disable hyperthreding

wait is multicore cpu machine then the same as a multi cpu machine in that case?

for me useful note is rule of thumb

All good and clear but, once the entire cpu is at max load hyperthreading because useless right?

Why ARM cpus doesn’t have hyperthreding?

I don't understand what exactly can cause a not-hyper-threading core to be idle when there is still processing to be done. Let's say I want to perform a billion calculations, Why would I care if those calculations are execuded in one thread (without HT) or in two threads at half the speed each (with HT)????

Airport nailed it.

This make sense with the like of i7 8700k vs i7 9700k

Rumoured 4 threads per core. A) A slight gain in performance sometimes B) A marketing gimmick

That explanation was amazing. Now you need to explain how to get teenagers to keep their room clean. 👍

6 core 6 threads and 4 core 8 threads almost give same level of performance if rest of the things are same.

Why don't you use the actual name, SMT, as opposed to the brand name from Intel?

First...thank god

yo.. second

One implication of the performance benefits of SMT only grows as the years go by and the memory wall increasingly shows its ugly face. And that is - what happens on a cache miss? Well, one hardware thread is blocked for an eternity while it waits on slow memory to eventually come back with some data. And as it waits, it uses NO INTERNAL RESOURCES. Well, happy day to the other core which'll have absolutely NO CONTENTION.

It's when you're Hyper about stitching threads.

I don't want to crash your party here, but he did not explain how Hyperthreading actually works under the hood.

😒 hyperthreading is fake cores, depending on your applications its sometimes useless and money wasted, check and compare benchmarks on different cpus 💻💻🤓

Intel fanboys in 3..2..1..

Somehow this is too close to Techquickie