need help for 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 ?
|ID: 6113 · Rating: 0 · rate: / Reply Quote|
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.
|ID: 6114 · Rating: 0 · rate: / Reply Quote|
the BOINC scheduler will adjust them,
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')
|ID: 6115 · Rating: 0 · rate: / Reply Quote|
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.
|ID: 6116 · Rating: 0 · rate: / Reply Quote|
Hello ,i agree with Jim1348,
3°) I set this parameter "fetch_on_update" to 1 in the cc_config.xml file,located in "C:\ProgramData\BOINC"
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)
|ID: 6117 · Rating: 0 · rate: / Reply Quote|