I have running boinc for 4 months and I have 2 cpu's so all the time I have 2 running proccesses and the rest waiting to start or ready to run.
I have added freehal@home to my list of projects today and downloaded a project I find for the first time I have 3 running processes.
is this ok as all 3 have there percent increasing although only the original 2 show up on the task manager as using 50% each.
if it is ok is there a way to run 3 all the time
thanks as this has puzzled me today
Paul

Do you have a CUDA capable Nvidia graphic card (GPU) in your computer?
If in addition Freehal has a GPU application, that would explain the third process.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

Hi Jahn

no mine is an intel(r)cor(Tm) 2Cpu 6400 at 213 ghz 2gb of ram
if this makes sense

Paul

I'm suspecting that FreeHAL is a non-CPU-intensive project:

A 'non-CPU-intensive' project is one whose applications use little CPU time. Examples include:

* Host measurements
* Network measurements
* Web crawling
* Network data access

A non-CPU-intensive project is treated specially by the core client:

* The core client maintains one result for the project
* The core client executes this result whenever computation is enabled, bypassing the normal CPU scheduling mechanism.

A project labels itself as non-CPU-intensive by including the <non_cpu_intensive> flag in its configuration file.

This attribute is at the project level; there is no provision for a project to have some applications that are CPU intensive and some that aren't.

Non-CPU-intensive applications can use chunks CPU time; this won't break anything, and the CPU scheduler will adjust to it by changing its estimates of 'CPU efficiency'. However, non-CPU-intensive applications should try not to use more CPU time than their resource share fraction indicates.

---

I'm suspecting that FreeHAL is a non-CPU-intensive project:

It is, but it shouldn't be. The app doesn't do network activity or anything like that, only CPU. It takes around 6 seconds of CPU time, the developer added intentional delays all over the code to make it use less than 1% CPU and take hours...

---