Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have been contributing to Stanford's Folding@Home project for some time with most of the computers I own.

I just installed the Windows client on a new machine running Windows 7, but see that the F@H process only binds to one CPU core. Is this due to it being run on Windows? (I have the 64-bit edition of Windows 7 installed.)

On the Mac and under 64-bit Linux distros, it will run across all available CPU cores.

share|improve this question
up vote 3 down vote accepted

Windows 7 is as fully multi-threaded as Linux, so Windows itself is not the reason.

The explanation must be that the Windows implementation of F@H has fallen behind the Linux one.

share|improve this answer
    
that's what I was afraid the answer would be... oh well. Maybe the upcoming 7.x release of the f@h client will solve that :) – warren Feb 21 '11 at 15:28
1  
thats kinda weird... usually the linux app is the one to fall behind. – monksy Feb 21 '11 at 15:33

BOINC lets you set the max number of cores to use -- you could run BOINC and attach to a project similar to F@h (e.g. GPUGRID or POEM) if you aren't too attached to F@h specifically, until a F@h BOINC version comes out.

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .