Message boards : Number crunching : BOINC for Android and R@H web-site computing preferences
Author | Message |
---|---|
Eternum Send message Joined: 14 Mar 20 Posts: 6 Credit: 2,276,628 RAC: 149 |
In my computing preferences I set both "Store at least ... days of work" and "Store up to an additional ... days of work" to 0. All my computers seem to follow this settings and download a new task only after the current one is finished. The only exception is my phone. I allocated 2 cores for BOINC, yet my phone routinely has 2 running WUs plus 3-4 in the pipeline. Does BOINC for Android use/follow R@H computing preferences? If not, how can I limit Android version of BOINC to only actively running tasks and force it to not download any extra WUs? Thank you. |
brendi000 Send message Joined: 28 Mar 20 Posts: 3 Credit: 108,917 RAC: 0 |
It seems to be boinc issue since I also getting excessive cache on other projects. You could set 1 core while downloading then stop fetching new task and swap back. It is pretty annoing sollution but it should work. |
Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1677 Credit: 17,756,393 RAC: 22,891 |
Does BOINC for Android use/follow R@H computing preferences? If not, how can I limit Android version of BOINC to only actively running tasks and force it to not download any extra WUs?I know that for some settings some projects have issues with accepting a value of 0. if you set Store at least 0.01 days of work Store up to an additional 0.01 days of workyou should get the result you're after. Grant Darwin NT |
Grant (SSSF) Send message Joined: 28 Mar 20 Posts: 1677 Credit: 17,756,393 RAC: 22,891 |
It seems to be boinc issue since I also getting excessive cache on other projects.With your system hidden it's hard to help. But it takes a while for BOINC to work out just how long it will take to process work when you first join a project, and you process the first Task on the first application. And if there is more than one application, it has to make a guess for all the other applications it has to run as well. Over time (hours, days or weeks depending on how long it take to process the particular Tasks) the Estimated completion times will eventually get pretty close to the actual value, unless the project issues a different type of Task, or another new application. Then it has to start figuring thing out all over again. Starting with a very small cache, generally 0.5 days & additional 0.02 days is best as it willstop you from getting more work than you can actually process when things change & while the Manager is working out the Estimated completion times. Grant Darwin NT |
Raistmer Send message Joined: 7 Apr 20 Posts: 49 Credit: 797,293 RAC: 0 |
If you set project share of 0 BOINC should fetch work for such project only when there is idle computational device available. That is, no more than one task per CPU, |
Message boards :
Number crunching :
BOINC for Android and R@H web-site computing preferences
©2024 University of Washington
https://www.bakerlab.org