BOINC projects using 100% of CPU on FreeBSD

uFluids doesn’t send to my platform. Quantum Monte Carlo does. And I’ve decided to give Rosetta@Home one more shot.

Reason? Oh, the reason is great news.

As I’ve written before, some projects somehow take up 100% of processor time, even though the settings unambiguously specify 50%. The reason for this, as I have accidentally found out by fooling around with Wine-emulated BOINC, is idprio.

Idle-time priority is being set to 31 in the /usr/local/etc/rc.d/boinc script. To a logical mind, this would mean that BOINC would only run its 50% share in the idlest of time, when no other process wants it. In reality, BOINC projects get 100% of idle time.

I guess this might be related to the fact that BOINC projects are run as separate threads. On the other hand, this might just be an idprio issue.

Right now, QMC@Home is running with priority nice 19, which it set by itself. The “Show graphics” button doesn’t do anything, probably graphics aren’t installed properly in my system.

It will take 150 hours to finish this workunit. I’d rather test result compatibility on a faster project.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: