need help for app-info


Advanced search

Message boards : Number crunching : need help for app-info

Author Message
Chris Skull
Send message
Joined: 11 Aug 15
Posts: 19
Credit: 154,704
RAC: 0
    
Message 6113 - Posted: 5 Feb 2017, 10:11:01 UTC

Hello,

i want to run only one atlas unit at once on my quad-core.
I use app info:

<app_config> <!-- ATLAS Simulation --> <app> <name>ATLAS</name> <max_concurrent>1</max_concurrent> </app> </app_config>


That works fine... only one unit runs at once.
but the problem is that atlas downloads 4 units at once and so my other projects runs out of work because boinc says: no work needed (3 atlas units are waiting)
How can i tell boinc to download only one atlas unit at once ?
____________

Profile Jim1348
Send message
Joined: 15 Nov 14
Posts: 111
Credit: 1,319,885
RAC: 0
    
Message 6114 - Posted: 5 Feb 2017, 13:21:01 UTC - in response to Message 6113.
Last modified: 5 Feb 2017, 13:30:12 UTC

The solution I use is to adjust the resource share of the projects, which you do on your account page for each project. For example, if you have 8 CPU cores, then set the total of the resource shares to some number that is easily divisible by 8. For example, set ATLAS to 10%, and the others should then be set to add up to 70%, so that the total is 80%. If you have two other projects and want them to run equally to each other, set them each to 35% for example.

It does not have to be an exact percentage; the BOINC scheduler will adjust them, you just don't want to be so far off that you run out of work. Occasionally, you will probably run out of work anyway. The more projects, the harder it is to get them all to run. I like to use only two projects at most on each machine, but I have several machines to spread the work around.

It is actually best to simply use the resource shares themselves, and not bother limiting each project with an app_config. That pretty much guarantees that you won't run out of work, and the average run time for each project will be what you set over a period of time. I think 10 days is the average time for convergence, but that can be adjusted. I often want a shorter period of adjustment time, and use a cc_config.xml to set it for one day:

<cc_config>
<options>
<rec_half_life_days>1.000000</rec_half_life_days>
</options>
</cc_config>

Chris Skull
Send message
Joined: 11 Aug 15
Posts: 19
Credit: 154,704
RAC: 0
    
Message 6115 - Posted: 5 Feb 2017, 15:45:38 UTC - in response to Message 6114.

the BOINC scheduler will adjust them,


Hello Jim,

thats the problem... in early versions of boinc , i guess < 4 or 5 working with resource shares work fine... adding 4 projects with 25% and each core of my quad-core runs a unit of each project... exactly what i want. Unfortunately than someone decide to let boinc to adjust the share of average credit and not the number of cores... since than i dont use the resource share at all..
there must be a solution to let boinc exactly do what i want... download 1 unit of atlas, run it, load it up and take 1 new unit... no ' adjustment' from boinc... just do what the user wants...
I don't need to do this for each project... only for atlas i need because my 8G RAM is not enough to let run 2 units at once.. (what will happens also during boinc-'adjustment')

Profile Jim1348
Send message
Joined: 15 Nov 14
Posts: 111
Credit: 1,319,885
RAC: 0
    
Message 6116 - Posted: 5 Feb 2017, 17:08:09 UTC - in response to Message 6115.

You could then limit Atlas to one using the app_config, and then also set the resource share accordingly. If you also use the cc_config.xml that I gave, it should adjust things fairly quickly - in a day or two. But BOINC has its limitations for sure, and it will not work 100% of the time.

PHILIPPE
Send message
Joined: 24 Jul 16
Posts: 84
Credit: 53,413
RAC: 0
    
Message 6117 - Posted: 5 Feb 2017, 20:38:30 UTC - in response to Message 6116.
Last modified: 5 Feb 2017, 20:40:26 UTC

Hello ,i agree with Jim1348,

I had the same problem (4 cores and only one for atlas because ram memory not enough)and i solved it in this way :

1°) I Adjusted the ressource share (100% for atlas and 300% for WCG)-->traduced by the scheduler (25% for atlas and 75% for wcg)

2°) I used an app_config.xml for atlas located in "C:\ProgramData\BOINC\projects\atlasathome.cern.ch " which can be reduced to :(for single-core wu but you have to adapt for multi-core wu)

<app_config>
<project_max_concurrent>1</project_max_concurrent>
</app_config>


3°) I set this parameter "fetch_on_update" to 1 in the cc_config.xml file,located in "C:\ProgramData\BOINC"
<fetch_on_update>1</fetch_on_update>

So you can have wus coming from different projects with no priority in the scheduling.

4°) You will have perhaps to modify the queue in your options (0.1 job / day + 0.5 additional job / day) and the space disk assignated to boinc to allow the storage of the wu downloaded by the boinc manager.

As Jim1348 wrote, it can last 2 days before the changes are applied...

just do what the user wants...

It's often possible but not always easy to do ...
It works most of the times excepted when wus crash for a particular project and then a debt in time running is created for this project.(In this case the scheduler wants to reduce the discrepancies because of the set-up in the ressource share) You have then to try the download of the wus manualy (updating the project)

official documentation
and faq mundayweb for configuration files (cc_config.xml)

Message boards : Number crunching : need help for app-info