Message boards : Questions and problems : One project at a time
Message board moderation
Author | Message |
---|---|
Send message Joined: 15 Jan 21 Posts: 2 |
I am fairly new to BOINC but I have an issue which I can't see how to fix. My computer will only execute one project at a time. I had subscribed to three projects Climateprediction, World Community Grid and Rosetta. I have never been given any climateprediction tasks but World Community Grid took all the processing tasks - I can run run 24 in parallel, but none for any other project. Then I rebooted my computer and now Rosetta runs all 24 tasks while World Community Grid has loads of tasks ready to start. I have set all projects to equal resource share. Is there some other configuration I need to look at? |
![]() Send message Joined: 28 Jun 10 Posts: 2842 ![]() |
Climate Prediction only has tasks for Linux at the moment. If you look at the server status page the only current model type to run on Windows is the Weather At Home 2 (wah2) type tasks and you will see there are none ready to send. With regards to the other two projects I suspect this is down to the deadlines of the tasks and how the client scheduler sets priorities. |
Send message Joined: 15 Jan 21 Posts: 2 |
Thanks Dave. But does not resolve the issue between Rosetta and World Community Grid. The latter has tasks ready. Where can I see the client priorities? |
![]() Send message Joined: 28 Jun 10 Posts: 2842 ![]() |
Thanks Dave. But does not resolve the issue between Rosetta and World Community Grid. The latter has tasks ready. Where can I see the client priorities? Assuming you are using the manager, in advanced view you can see the deadlines for the different tasks. Also worth keeping both the amount of work and additional amount of work low (0.1 or 0.2 days work.) If you do this after a day or things start behaving. If you add CPDN into the mix it starts getting more complicated as the task durations are much longer though nothing like the nine or more months they were in the early days of the project. The other thing that goes into the mix when requesting work is the weighting you give to each project. This is done on the project websites. They should all default to 100 if you haven't played around with them. BOINC should in theory default to first in first out behaviour with tasks unless a task needs to be promoted in order to avoid the risk of missing a deadline. I think the best thing to do is unless you have a project you want to give priority to (I do this with CPDN) is ignore what it is doing and between the work requests and deadlines it should eventually sort itself out. The more projects and the more you play about with it manually as I do when testing work is released for CPDN the longer it will take. |
Send message Joined: 31 Dec 18 Posts: 314 ![]() |
Another thing that can distort the mix of jobs and can end up with Boinc just running one project at the expense of all others is the attempt to match the credit score to the project weighting over several day’s processing. To make Boinc settle down more quickly I set rec_half_life_days in cc-config.xml from 10 down to 1. |
![]() ![]() Send message Joined: 17 Nov 16 Posts: 906 ![]() |
set rec_half_life_days in cc-config.xml from 10 down to 1. +1 |
![]() Send message Joined: 3 Apr 21 Posts: 1 |
Climate Prediction only has tasks for Linux at the moment. If you look at the server status page the only current model type to run on Windows is the Weather At Home 2 (wah2) type tasks and you will see there are none ready to send. With regards to the other two projects I suspect this is down to the deadlines of the tasks and how the client scheduler sets priorities. Do you know you can also use Android mini PCs? They cost about 20-25$ on AliExpress and they have 4 / 8 cores at 1.5 / 2.0 GHz. I have 3 running World Community Grid and Universe@Home 24/7 and they work really well. With 200$ you can buy about 8-10 mini PCs, and the processor consumes about 5-10W, nothing. |
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.