Boinc Not Seeing 4 CPU's
DaveT
the CPU benchmarks, BOINC is only seeing two CPU's. What am I doing wrong? Shouldn't there be four?
Thanks
Dave T
Rodney Pont
>I just upgraded from a dual-core to an AMD X4 955 Phenom II 3.2 GHz Quad-Core. However, when I run
>the CPU benchmarks, BOINC is only seeing two CPU's. What am I doing wrong? Shouldn't there be four?
Have you set your preferences to only use 2 cpus in the past or set
ncpus in cc_config.xml to 2?
--
Regards - Rodney Pont
The from address exists but is mostly dumped,
please send any emails to the address below
e-mail ngpsm4 (at) infohitsystems (dot) ltd (dot) uk
DaveT
>On Wed, 28 Oct 2009 11:52:05 -0700, DaveT wrote:
>
>>I just upgraded from a dual-core to an AMD X4 955 Phenom II 3.2 GHz Quad-Core. However, when I run
>>the CPU benchmarks, BOINC is only seeing two CPU's. What am I doing wrong? Shouldn't there be four?
>
>Have you set your preferences to only use 2 cpus in the past or set
>ncpus in cc_config.xml to 2?
No. Plus, I can't find cc_config.xml. Wouldn't it be in C:\Documents and Settings\All
Users\Application Data\BOINC? Do I need one?
DaveT
Well. Either I screwed it up or I fixed it. I put a cc_config.xml file in
C:\Documents and Settings\All Users\Application Data\BOINC
containing the lines:
<cc_config>
<options>
<ncpus>4</ncpus>
</options>
</cc_config>
Then I did a "Read Config File". Boinc freaked out for a bit and couldn't connect to the client.
Then all the tasks dissappeared. I stopped and started Boinc a couple of times. Then I renamed the
cc_config.xml to X cc_config.xml and stopped and started Boinc. Now it seems to be working with four
CPU tasks and one CUDA as expected. I guess it's fixed, I dunno. Thanks.
Dave
Rodney Pont
>>Have you set your preferences to only use 2 cpus in the past or set
>>ncpus in cc_config.xml to 2?
>
>No. Plus, I can't find cc_config.xml. Wouldn't it be in C:\Documents and Settings\All
>Users\Application Data\BOINC? Do I need one?
It depends on what version you have but mine is in c:\ProgramData\Boinc
and no, you don't need one. If you had one it could upset things.
Rodney Pont
>Well. Either I screwed it up or I fixed it. I put a cc_config.xml file in
>C:\Documents and Settings\All Users\Application Data\BOINC
>containing the lines:
><cc_config>
> <options>
> <ncpus>4</ncpus>
> </options>
></cc_config>
>Then I did a "Read Config File". Boinc freaked out for a bit and couldn't connect to the client.
>Then all the tasks dissappeared. I stopped and started Boinc a couple of times. Then I renamed the
>cc_config.xml to X cc_config.xml and stopped and started Boinc. Now it seems to be working with four
>CPU tasks and one CUDA as expected. I guess it's fixed, I dunno. Thanks.
The cc_config file was needed when cuda workunits first came out
because the Boinc manager didn't know anything about gpus. It only
allowed as many jobs as cpus to run so if a cuda job was running on the
gpu there was a cpu doing nothing. For 4 cpus and one gpu you would set
the ncpus to 5.
The current version know about the gpu so you don't need the ncpus
option and it upsets things if there. I can't remember if it causes
workunits to fail but since things are now working I'd delete it and
just keep my fingers crossed :-)
DaveT
>On Wed, 28 Oct 2009 16:29:23 -0700, DaveT wrote:
>
>>>Have you set your preferences to only use 2 cpus in the past or set
>>>ncpus in cc_config.xml to 2?
>>
>>No. Plus, I can't find cc_config.xml. Wouldn't it be in C:\Documents and Settings\All
>>Users\Application Data\BOINC? Do I need one?
>
>It depends on what version you have but mine is in c:\ProgramData\Boinc
>and no, you don't need one. If you had one it could upset things.
Originally, (for some unknown reason) I ran it with all the model settings like
<ncpus>N</ncpus>
That really upset Boinc. BTW, it's 6.6.38. Then I ran it with nothing.
That seemed to fix it. Then I ran it with
<cc_config>
<options>
<ncpus>4</ncpus>
</options>
</cc_config>
That got it to recognize all 4 CPU's plus the GPU. Then I took away the XML file.
It still recognizes all 5 processors. There must be some memory thing happening.
It downloaded a whole bunch more jobs. This was probably good, because it hasn't been ablt to get
any more lately, and has already chewed through about half of them.