Originally posted by: chsh1ca
Interesting results. I'm hopeful we start to see multi-core on a single die.
Originally posted by: Accord99
Actually, I think Jeff is referring to the large benefit of HT for SETI. Using a single instance does 1 WU every 150min, with 2 instances, each instance processes 1 WU every 165min, or effectively 82min per WU, which is a massive gain. Most likely, the cause of this gain is due to the relatively poor coding of the SETI client, resulting in stalls that slows down the performance with 1 instance, but ironically enables opportunities to better utilize the P4's execution resources with 2 instances.
Actually, it is likely related to how Seti@home is written. I have noted this behaviour many times before, even on non-HT systems (I've even mentioned it before on a few boards). On my Athlon XP 2000+, Seti on Linux would do one WU in ~4:15. With two running, it would finish 2 in less than 6:00, meaning that for an extra 1:45 I could have two WUs completed. I noted similar behaviour on Dual PIII/933 boxes (running 4 processes only took about +50% longer). +50% seems to be the delta for non-HT processors.
It's still good to see that HT makes it +90-95%. It isn't necessarily only a benefit of HT, but more of simply how Seti is written. If you ask me for an explanation, I haven't got one. All I have is observed behaviour. HT should give that difference a great boost simply because of it's half multi-threaded capability.
EDIT:
By the way, just as a point, it's not as if HyperThreading is new anymore. It's not like "today's apps" weren't expected to already support it. After all, it was almost a year ago that Anandtech put out its article on the
P4 3.06 w/HT.
For such a touted feature, I'd expect to have seen more games making use of it.