Advanced search

Forums : Technical Support : All camb_boinc2docker tasks are looping on my PC
Message board moderation

To post messages, you must log in.

AuthorMessage
villy
Avatar

Send message
Joined: 2 Aug 19
Posts: 5
Credit: 57,672
RAC: 0
Message 22225 - Posted: 29 Aug 2019, 18:14:52 UTC

All tasks coming from project camb_boinc2docker with running time 6:54 end up looping on my PC (Ryzen 2600x/Nvidia GTX 980Ti). Will be glad to provide more details on how I know they are looping, but I am certain they are looping and eventually end up with computation error.

Tasks for camb_legacy, which run for 11-13+ hours, and running just fine, as well as tasks from LHC@home, Cosmology@home and Rosetta@home. So it is something specific to camb_bionic2docker's tasks that someone needs to take a look at.
ID: 22225 · Report as offensive     Reply Quote
villy
Avatar

Send message
Joined: 2 Aug 19
Posts: 5
Credit: 57,672
RAC: 0
Message 22227 - Posted: 30 Aug 2019, 0:46:13 UTC - in response to Message 22225.  

These tasks keep on coming, and keep on looping and erring with the same result, so I am aborting them all. It will be very helpful if someone looks into this and do something about it. What's even worse is that BOINC sets them to run utilizing 100% of the CPU I've allotted to the network, which is 9 of my 12 cores, so they not only waste a ton of CPU's time but do so in detriment to the other projects.

I don't want to suspend all Cosmology@home tasks, but if this continues I'll eventually be force to.
ID: 22227 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 159
Credit: 7,580,022
RAC: 1,767
Message 22229 - Posted: 31 Aug 2019, 6:28:03 UTC - in response to Message 22227.  

See the FAQ section on limiting the number of cpus per task. Set it to the number six or less.

https://www.cosmologyathome.org/faq.php#limit-cpu
ID: 22229 · Report as offensive     Reply Quote
villy
Avatar

Send message
Joined: 2 Aug 19
Posts: 5
Credit: 57,672
RAC: 0
Message 22230 - Posted: 31 Aug 2019, 16:58:39 UTC - in response to Message 22229.  

I did that, thx for the response.

BTW, this should've been handled by the program itself, by scrutinizing the error, the run environment, and adjusting accordingly. I'm mildly shocked to see something like that, imho this is very, very basic, 101 dev.

Anyhow, will see how it goes and I'll report back.
ID: 22230 · Report as offensive     Reply Quote
Jonathan

Send message
Joined: 27 Sep 17
Posts: 159
Credit: 7,580,022
RAC: 1,767
Message 22234 - Posted: 1 Sep 2019, 8:06:05 UTC - in response to Message 22230.  

Virtual Box wasn't starting with more than half the cores your OS is reporting. I don't know if you could blame Microsoft, or Oracle's Virtual Box, or BOINC or Cosmology@Home for this issue. There really multiple software development groups involved.
ID: 22234 · Report as offensive     Reply Quote
villy
Avatar

Send message
Joined: 2 Aug 19
Posts: 5
Credit: 57,672
RAC: 0
Message 22240 - Posted: 2 Sep 2019, 21:53:33 UTC
Last modified: 2 Sep 2019, 21:54:48 UTC

The Box was utilizing 100% of what I had allocated to BOINC, and that's fine, no issues there - the problem is that the tasks were looping and after looping for quite awhile they end up with errors. So, was all waste.

Moving on to the fix - I added the xml as suggested, limiting the tasks to 6 cores and that seems to work exactly as needed. 7 tasks now and counting, all completed and validated, Thx again for the suggested solution.
ID: 22240 · Report as offensive     Reply Quote
villy
Avatar

Send message
Joined: 2 Aug 19
Posts: 5
Credit: 57,672
RAC: 0
Message 22245 - Posted: 5 Sep 2019, 3:33:49 UTC

Yep, fix is working beautifully, for anyone that might run into the same problem - thx again for the help Jonathan!
ID: 22245 · Report as offensive     Reply Quote

Forums : Technical Support : All camb_boinc2docker tasks are looping on my PC