Hi,
On Wed, Sep 23, 2009 at 04:42:59PM +0100, Clive Messer wrote:
> I've spent much time fiddling with Linux kernel schedulers and priorities. I
> found that rather than just setting the priority of a task to 19, in the case
> that the machine is not a dedicated cruncher, the desktop responsiveness is
> improved by setting the tasks schedule policy to BATCH, which gives it a
> slight scheduling disadvantage compared to a task running with a standard
> NORMAL/OTHER schedule policy and nice'd to 19.
>
> Basically, the patch results in CPU tasks running BATCH/19 and GPU tasks
> OTHER/10. In the case of a headless dedicated cruncher the PPD is not
> affected,
> but in the case that the machine is also running general tasks (like a code
> build and a desktop), the desktop responsiveness is greatly improved under
> heavy load.
The Debian initscript for the BOINC client prefers IDLE over BATCH if it
is available. IMHO that would be more appropriate for desktops, while
BATCH should be preferred for dedicated machines. If this is going to be
integrated, then there should be a way to specify the scheduler class,
priority and nice level in the configuration somehow.
Debian also uses ionice to set the I/O scheduling class to IDLE, so that
should be integrated too. The I/O class should be set for the core
client as well, not just for the applications.
Gabor
--
---------------------------------------------------------
MTA SZTAKI Computer and Automation Research Institute
Hungarian Academy of Sciences
---------------------------------------------------------
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
