|
|
|
| ||||
|
|
Hyper-Threading takes one processor and theoretically turns it into two. Without Hyper-Threading the threads have the form a line and wait until the first is executed before the second can be processed. Adding the Hyper-Threading technology allows the second thread to be processed simultaneously by making its way to the second visible processor. With one physical processor switching between two is avoided, saving additional time.
By allowing the second thread to make its way to the second visible processor both tasks will therefore be completed quicker than if they had to be executed one at a time. Normally with out Hyper-Threading present the instructions would have to be handled in order (one after the other). Additionally, the code can be executed by alternations between the processes being handled. Hyper-Threading saves time and allows those that need to take advantage of it or are just impatient to see the results they are looking for sooner.
The physical processor die diagram is below. Not much has been altered physically to the processor (ie: there are not two processors crammed into one). Mapped out below are some of the physical changes that allow Hyper-Threading to do what it does.
Now things get more technical. Below you can see how Hyper-Threading handles the processes it is sent. Hyper-Threading is capable of taking advantage of things you do daily and all software does not have to be re-written to do so.
Andrew would be the perfect example of taking advantage of the above. The co-owner of this site loves to have in excess of thirty windows and ten or so programs open at any given time. He is the type of person that would benefit from the Hyper-Threading technology with out changing the way he does anything or updating the software that he uses. (Pictures from Intel) Next Page: More
explanation [Page 1] [Page
2] [Page
3] [Page
4] [Page
5] [Page 6] [Home] |
|
|
|
