Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
marty9876 said:.
edit: ingore HT crap. If running HT it will always report 1/2 but it's running wide open.
Roman79 said:Ah...I don't think it works like that; pretty sure you still need to run two instances with HT. I always had to with my P4. So in the OP's case he would need 4 instances since he has 4 logical processors.
marty9876 said:if you want to show 100% CPU utlization on the graph on HT based systems then yea you need to run 2x clients per physical core.
Running 2x clients in HT systems will at best yeild a 15% increase in over all points. Some WU sets you get a huge PPD hit.
Point being 2x clients on HT not needed to the one core to run ar 100% (windows reports 50% usage)
marty9876 said:Differance is HT is not a core.
Dual core= 2x clients per physcial CPU.
HT= 1x client and windows reports 50% usage
Dual core HT Xeon chips= 2x clients
Ahh I give up. This coversation has been had so many dimes.![]()
ND40oz said:You're still wasting parts of the pipeline if you don't run 4 clients on a dual HT xeon box. I run 4 on my dual prestonia, ever bit helps.
OC-AMD per Larry said:Folks, for many the HT (HyperThreading) issue is one that they just don't understand. While Stanford allows you to run more than one instance of the Folding@Home client on your computer, you are not really helping them if the number of clients you are running is not equal to the number of REAL CPU's you actually have. While running two instances of the F@H client will return two work units more quickly than doing one at a time, that is not what is important. Returning one work unit 70% faster and starting the next generation of tests on the work unit, is what Stanford wants. Speed in working through each protein generation is very, very important. Sometimes quality is better than quantity. Quality in this case is work being returned more quickly. While it is well known that an HT CPU can run 2 work units because the OS treats it like two CPU's, and you can gain a possible 15-30 percent increase in points for that computer, it also means that each work unit is returned more slowly. In simple terms, if the project has 300 generations needed to test a theory on a protein model, and running two instances at once delays the return of work for 1 day each time, you end up with a 300 day delay. That translates to about a 10 month delay in examining your data for the final result. The bottom line is simply this: Run 1 instance for each CPU you have. An HT CPU is not two CPU's, it is one. Let's work to advance the science and spend a little less time worrying about the number of points you get.
This is a direct quote from Dr. Vijay Pande:
1) If you care primarily about points, running 2 procs on HT is still the best bet. We are grateful for all contributions and if people choose to run 2 procs on HT, our approach is that all contributions are welcome.
2) If you care about the science foremost and are interested in our recommendations, then do not run 2 procs on HT, but please just run one process. That won't be best for points, but is best for the science.
3) If your machine cannot make the deadlines, then one should run the timeless WUs.
I hope that clears these issues up and thanks to all for their contributions.
Thanks for listening and please do the right thing.
Larry
zim01 said:Who can argue with mary03 [H]ard|DCer of the Month - February 2006
zim01 said:Who can argue with mary03 [H]ard|DCer of the Month - February 2006
