O.K. I dont know alot about computers. but After lots of reading i am thinkling of doing my first build, but when i look online like at new egg all the intell processors say that they do not support hyper threading . The only intell processor that new egg said supported hyper threading was a single core cedar mill i think. Now wheb i look at AMD processors on new egg it says that pretty much all the x2's and phenoms support hyper threading. Whats up with this ? Is the hyperthreading thing just a misprint when it comes to new egg and intell procs supporting multi threading??? First post here so pls be kind to my newbitity!
intels havent supported HT since the days of P4 HT cpu's, it was the cheats way of making 1 core into 2 cores, however, it was pretty much a failure. Apparently they are bringing HT back with the Nehalem CPU's.
As for AMD i dont know, havent followed there architecture much.
Don't worry about hyper threading. What is your budget? Hyper Threading technology was in the old Pentium 4's. You need to get a Core 2 Duo processor. If you tell your budget we could better assist you.
Intel processors are better for gaming from all the research I've done, so don't go for AMD.
I am lookin to spend no more than $2000 i need everything bran spankin new i will mostly use it for gaming Specifically age of conan. I was thinkin of going ati for graphics like a 3870x2 so if i use intell i would need a x38 mobo. But if i used AMD i could build it much cheaper it seems. Plus i will not be Over clocking since i really now little about it and dont wanna burn up my investment
The new gaming rig I just built is with the new Intel E8400, the new 45nm chips. Runs amazingly cool. Runs anygame I throw at it with my e-8800GT 512mb
The first generation of hyper threading is nearly a failure. Except some of the programs that do take advantage of HT, you generally see decreased performance with HT enabled. This is why companies usually disable HyperThreading in their servers to maintain its performance.
HT, or HyperThreading, was originally created to take advantage of unused portion of the processor at any given time. According to Intel's document, at any given time (this only applies to regular users), CPU utilization rate is about 5~10%. Therefore they developed HyperThreading to take advantage of that unused 90~95% processing power, by "tricking" operating system to think there are two cores instead of one.
However, the early revisions of HyperThreading suffered from massive "cache thrashing", which is when two CPUs fighting for the cache space in the processor. I'm not entirely familiar with the concept, but apparently before the first core is done accessing data from the cache, the second core over-writes the cache with its own data, causing error. Then the cache has to be flushed, and data reloaded. This means wasted processing cycles, and increased processing time.
As for AMD, their HT stands for "HyperTransport", which is an interconnect between CPU and the rest of the computer. This has nothing to do with the "HyperThreading" you mentioned.
Do not purchase a CPU with HT at this time. There are numerous multi-core processors with very affordable prices, and any of them do everything better than a HT enabled Pentium 4/D.
Don't complain. Intel wants to move onto the latest process technology because it saves them dollars on each wafer they put through the fab not to mention they have to utilize each 45nm fab to get those oh so favorable tax right offs.
---------------
"Like a child in his fantasy, punching holes in the walls of reality"
intels havent supported HT since the days of P4 HT cpu's, it was the cheats way of making 1 core into 2 cores, however, it was pretty much a failure.
If you consider improved interactivity and up to about 30% better performance on multithreaded applications to be 'pretty much a failure', anyway; hopefully no-one was dumb enough to expect things to run twice as fast.
If you consider improved interactivity and up to about 30% better performance on multithreaded applications to be 'pretty much a failure', anyway; hopefully no-one was dumb enough to expect things to run twice as fast.
Or Slower in other cases.
Or Causing Complete System Instability in others. (Even when true Dual CPU Systems are fine.)
---------------
If its good in theory but not in practice,
its not good theory.
AMD is suppose to come out with reverse HT so that single threaded apps will work better with multiple cores.
Only problem I see with that is how can you guarantee no problems? When an app is made for a single thread ripping it into 2 or 4 parts the recombining it could cause problems.
Maybe thats why they decided not to do it yet since they couldn't guarantee that. We will see. Although Nehalem will have a advanced and better version of HT so that might make it better.
Only problem I see with that is how can you guarantee no problems? When an app is made for a single thread ripping it into 2 or 4 parts the recombining it could cause problems.
Maybe thats why they decided not to do it yet since they couldn't guarantee that. We will see. Although Nehalem will have a advanced and better version of HT so that might make it better.
I think AMD had thought about Reverse HT. But they leaked it to the media (Charlie in specific) before their engineering team gave them the "I don't think its going to work" response. All in all, miscommunication between the management team and engineering team may cause the project to fail.
One of the most difficult problem that needs to be solved in Reverse HT is, like you said, how can a program that's written in a single thread be separated into multiple different threads, and re-combine?
What if the program follows a very strict in-order execution, where A-> B, B-> C, C-> D? Then even with RHT, in order to obtain D, C must first be obtained, and so on. Therefore, without A-> B executed, the program simply cannot move on.
In reality, I think RHT is still implemented, but just not in the sense AMD (Charlie) was touting; such as Intel's OoO capability, as well as AMD's. They are both good out of order execution engines (with Intel's being far superior), but it'll take a long while before RHT can actually become a reality.
I'm merely speculating here, so anyone who has extensive knowledge in this area please also contribute to this topic .
I think AMD had thought about Reverse HT. But they leaked it to the media (Charlie in specific) before their engineering team gave them the "I don't think its going to work" response. All in all, miscommunication between the management team and engineering team may cause the project to fail.
One of the most difficult problem that needs to be solved in Reverse HT is, like you said, how can a program that's written in a single thread be separated into multiple different threads, and re-combine?
What if the program follows a very strict in-order execution, where A-> B, B-> C, C-> D? Then even with RHT, in order to obtain D, C must first be obtained, and so on. Therefore, without A-> B executed, the program simply cannot move on.
In reality, I think RHT is still implemented, but just not in the sense AMD (Charlie) was touting; such as Intel's OoO capability, as well as AMD's. They are both good out of order execution engines (with Intel's being far superior), but it'll take a long while before RHT can actually become a reality.
I'm merely speculating here, so anyone who has extensive knowledge in this area please also contribute to this topic .
Agreed. But I think that OoO is for if a thread is waiting to be executed and another with top priority comes behind it it will process the high priority thread first. I might be wrong but I think thats what I read.
I don't think reverse HT will be possible. Since multi threading is the future there will be a time, and maybe soon with nehalem and AMDs next architecture, the single threaded applications will cease to exists. Might be a while away but it will happen. Then RHT will be useless and they will develop a RHT for dual threaded apps to be used on quad/octo cores.
What they need to work on is enhancing the communication between cores to even better heights that way in multi-threaded apps they can increase performance. But I am just a crazy guy what do I know?