Thread 'fair scheduling with 7.0.x'

Message boards : BOINC client : fair scheduling with 7.0.x
Message board moderation

To post messages, you must log in.

AuthorMessage
RoSi

Send message
Joined: 10 Feb 12
Posts: 3
Germany
Message 42511 - Posted: 10 Feb 2012, 1:24:34 UTC

Hi all,

how is the fair scheduling with boinc 7.0.x supposed to work when there are projects involved which have different queue strategies? Currently, I see that projects with block queuing (WCG, POEM, Rosetta, QMC, ...) will download a maximum of tasks to fill up the buffer, projects with no queuing (T4T) won't load new tasks and intermittent projects (LHC1) won't load new tasks either.

What would be the ideal work buffer setting (min/max value) in such a scenario that all projects get an equal chance to download (and then execute) tasks?

Cheers,
Rob
ID: 42511 · Report as offensive
RoSi

Send message
Joined: 10 Feb 12
Posts: 3
Germany
Message 42538 - Posted: 12 Feb 2012, 9:06:06 UTC

According to this new scheduling process the request will only take place when the min boundary of the work cache is hit. However, intermittent projects like LHC1 most likely won't have at this single point in time tasks available. And when new tasks appear then the requester won't ask for it because its work cache is above the min boundary. I think this approach discriminates those projects and only systems which are tied exclusively to such projects will work on their tasks which shouldn't be general goal. Maybe it is possible to allow requests at any time for projects which are below a certain threshold of the duration_correction_factor or whatever value is responsible to calculate the scheduling debt.
ID: 42538 · Report as offensive

Message boards : BOINC client : fair scheduling with 7.0.x

Copyright © 2025 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.