explicit CPU controll

Message boards : Questions and problems : explicit CPU controll
Message board moderation

To post messages, you must log in.

AuthorMessage
rflulling

Send message
Joined: 9 Oct 10
Posts: 1
United States
Message 35150 - Posted: 9 Oct 2010, 2:27:37 UTC

I would like to set BOINC to use the Full Power of my HyperThreaded Dual Core CPU, one work unit at a time. Provided, that this does not some how create bad work unit results.

Currently restricting function to 50%, and usage at 90%, the result is activity in all 4 cores running 2 work units at a time, shared with restricted power. Cores fluctuate in activity.

With restricting function to 100%, and usuage at 90%, the result is is activity in all 4 cores running 4 work units at a time, without sharing of power. Pulsing action from the CPU every time 90% is reached. Work unit take about 24hrs each to produce.

Every project has it's own set of controlls many seem highly outdated, though it's obvious they all use a common source template. I am aware of the onboard settings and they are set. However, what I seek is further controll of the BOINC application. I would like then to Apply this to all incoming project files.
ID: 35150 · Report as offensive
Les Bayliss
Help desk expert

Send message
Joined: 25 Nov 05
Posts: 1654
Australia
Message 35151 - Posted: 9 Oct 2010, 3:22:18 UTC - in response to Message 35150.  

Set On multiprocessors, use at most to 25
i.e. 25% of 4 cores (processors), is one, so you'll only get one work unit at a time. For the amount of time that you have set in the 1st 2 options of Network usage.

Set Use at most
Can be used to reduce CPU heat
to 100. i.e. Run that processor continually, not 9 seconds on, and 1 second off, which is what 90% means.

What is show/used by different projects depends on how up to date they are with their server side BOINC version. And some are known to be a loooong way behind.

ID: 35151 · Report as offensive

Message boards : Questions and problems : explicit CPU controll

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.