How does hyperthreading even work? What kind of bullshit magic

>>52424914
It doesn't. It's a huge scam. It's just one core running at 2x speed.

The jewish consortium needs to keep the goyim thinking that processor speeds have to be really low, so they can fund their weapons research and mind control with the really fast processors.

The magic is called lying. If you keep repeating the lie, retards will believe you.

>>52424914
You just jack up the gigahertz. That's all it is.

>>52424914
what techquickie on it, have linus-senpai explain it to you

>>52424914
Retard.

https://en.wikipedia.org/wiki/Hyper-threading

>>52424939
Retard.

>>52424962
Retard.

>>52424976
Retard.

>>52424993
>he cant detect shitposting
back to /r/4chan with you.

>>52424914
The 'core' doesn't always utilise its full resources, so you can use some of them while waiting for others. this is possible with out of order execution.

Say, your core 1 is waiting for a floating point calculation to finish, you have unused ALUs, memory paths, etc. hyper threading uses some of the core resources while they are free. it is (in theory) almost as good as two actual cores. in practice, it's not as good, every jump fucks up your predictions

>>52425017
Retard.

>>52425083
>he really cant detect shitposting
back to /r/funny with you

>>52425112
Retard.

Well, to put things into perspective, consider what a superscalar processor does. It takes multiple instructions operating on different data, and executes them simultaneously or out of order. Can you add eax + ebx and mov rsi into rdi at the same time? Of course you can! So given that each core has multiple arithmetic units for dealing with superscalar architectures, it stands to reason that one should be able to process multiple threads using those multiple arithmetic units, at a possible cost of single threads getting less superscalar action.

"But what about registers?" you may ask. Surely, there's going to be conflicts between a core sharing registers between multiple threads, yes? Again, this is where we bring in the nice thing about superscalars... they can have multiple sets of registers. Intel's CPUs actually have hundreds of them... it's just that from the programmer's perspective, one can only see 16 at a time. In reality, the processor can take multiple branches simultaneously, operating on multiple sets of registers, and then chuck out one set once the time for branching comes.

One of my professors gave a lecture on this very topic a few days ago. The complexity put into CPUs these days is pretty fucking fascinating.