Originally posted by: clarkey01
Originally posted by: Pabster
Originally posted by: Duvie
I always felt in my testing my HT was qute consistent...so it seems hard for me to understand this flopping...so one could see my conspiracy theory on this...
Keep in mind that the HT behavior might well be different on the Smithfield dual cores than it is on Prescott. It is entirely possible that Intel has made a few revisions to it.
That said, I'll hope your "conspiracy theory" is simply that Tom has made a fool of himself and that the results are invalid. Considering Tom has 99% AMD advertising now I find it hard to believe he has any real incentive to hand Intel anything.
Smithfield is no more then prescott x 2. I doubt Intel have touched it since there's been zero talk about it. When prescott came out there was mention of it's new and improved hyperthreading, no such changes have happend for smithfield.
The point here is, does winXP support dual HT cores ? We all know that winXP has support for hyperthreading, but supporting two cores with HT is another thing. then you dont have virtual processor 1 and 2 but you have 1, 2, 3 and 4 of which 1 and 2 are one real core and 3 and 4 one real core. and the OS has to take all into account. assigning threads should go like this:
first: 1
second: 3
fourth: 2 or 4 if 1 or 3 are not 100 % loaded, etc (this is still from assumption the OS cannot ask how loaded a CPU is, anyone more knowledgable may jump in and clarify, but I think the OS has to deduct by its workload handed out how loaded a CPU is.) so it has to see if virtual core 1 and 3 have space left and then assign it to the one with mosts space left.
as you can see the HT makes assigning threads not that easy and would require some logic, which is quite taxing for such a very basic item of a multitask OS that I think it will impact performance.
in general i'll repeat my statement that the winXP thread sheduler sees the virtual cores as real one and acts like they are, because the concensus now is that the divX thread is set to low priority which means it should barely get any work done, the fact that it does get so much work done, and the big differences in other areas make me think that the divX thread is hampering intel in the other areas. which is essentially a bad thing, you dont want something set at idle priority to interfere with items you assigned a higher priority.