how to prioritize one project over the others?

Message boards : Questions and problems : how to prioritize one project over the others?
Message board moderation

To post messages, you must log in.

AuthorMessage
stasuss

Send message
Joined: 4 May 16
Posts: 3
Russia
Message 69429 - Posted: 4 May 2016, 9:47:59 UTC
Last modified: 4 May 2016, 9:50:16 UTC

hello all.

i'm crunching vlhc as my favorite project. but it gives me only two tasks, and that is half of the total cores of my cpu.
the second favorite project is lhc classic, but it does not always have tasks available.

so i've added two more projects: citizen science grid and datamining.

resource share is:
vlhc - 100
lhc - 50
science grid 40
datamining 10

what i need: vlhc running constantly without interruptions. lhc running constantly on 2 spare cores, when there are tasks.

what i get: projects swapping once an hour, vlhc is frequently paused in favor of others.

for example vlhc may become paused and there will run 2 lhc and 2 grid tasks.

how to achieve at least that vlhc tasks run constantly without interruptions?
ID: 69429 · Report as offensive
SekeRob2

Send message
Joined: 6 Jul 10
Posts: 585
Italy
Message 69446 - Posted: 4 May 2016, 19:07:28 UTC - in response to Message 69429.  

Don't hesitate to read prior posts on how the BOINC scheduling works, where the balance of the resource shares is maintained over a longer period, NOT short term.

As far as project switching, the default is 60 minutes. I've got it set at 1440 minutes which helps to start-complete most tasks without interruption.
Coelum Non Animum Mutant, Qui Trans Mare Currunt
ID: 69446 · Report as offensive
stasuss

Send message
Joined: 4 May 16
Posts: 3
Russia
Message 69448 - Posted: 4 May 2016, 19:33:16 UTC - in response to Message 69446.  

Don't hesitate to read prior posts on how the BOINC scheduling works, where the balance of the resource shares is maintained over a longer period, NOT short term.

As far as project switching, the default is 60 minutes. I've got it set at 1440 minutes which helps to start-complete most tasks without interruption.


i've tried reading about scheduler, but i can't get the point. can you say if my approach to distributing resource shares is correct?

100% to highest priority project and wait a month?
ID: 69448 · Report as offensive
SekeRob2

Send message
Joined: 6 Jul 10
Posts: 585
Italy
Message 69449 - Posted: 4 May 2016, 19:50:33 UTC - in response to Message 69448.  
Last modified: 4 May 2016, 19:52:21 UTC

To get the long term percent of resources allocated you add up all the different project share values, then express the 100 of vlhc as % of the sum total, so for instance 100 / 200 = 50‰ of the total CPU time (all cores/threads combined), longer term. Effectively you can have one project take it all, then the next and the next, also taking into consideration that some projects won't have work if it is their highest fetch priority turn. Make a change, add a project and the whole mill starts churning anew, learning over time how each science app behaves and how long they are expected to run. Leave it alone and it will come right, eventually. Interfere and you'll hardly ever get to the desired time distribution.
Coelum Non Animum Mutant, Qui Trans Mare Currunt
ID: 69449 · Report as offensive
stasuss

Send message
Joined: 4 May 16
Posts: 3
Russia
Message 69451 - Posted: 4 May 2016, 20:36:38 UTC - in response to Message 69449.  

so suspending projects also breaks learning?
ID: 69451 · Report as offensive
SekeRob2

Send message
Joined: 6 Jul 10
Posts: 585
Italy
Message 69452 - Posted: 4 May 2016, 20:40:55 UTC - in response to Message 69451.  

Yes indeed, the learning stops for the projects suspended, so if you do this for 2 of your 4 projects, the client will only smart up on the two active.
Coelum Non Animum Mutant, Qui Trans Mare Currunt
ID: 69452 · Report as offensive

Message boards : Questions and problems : how to prioritize one project over the others?

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.