Posts by BellyNitpicker

1) Message boards : Number crunching : how long can "long tasks" be? (Message 1912) Posted 21 Jan 2023 by BellyNitpicker Post: I've suspended SiDock for the time being. I run BOINC in Ubuntu virtual machines on Mac hardware and VirtualBox. The last few long SiDock tasks (running in different machines) showed more time remaining after three day's execution than they had before they started. The CPU was trivial, but watching them run, I could see the remaining time increase more rapidly than the elapsed. I don't know at which point they failed, but I'm not really interested. I don't have time to babysit. If tasks are unreliable, the project gets shut down, and the capacity handed to another project. Nick
2) Message boards : Cafe : SIDock taking over! (Message 632) Posted 8 Mar 2021 by BellyNitpicker Post: Thank you for your thoughts. I'll do some experimenting.
3) Message boards : Cafe : SIDock taking over! (Message 628) Posted 7 Mar 2021 by BellyNitpicker Post: Good morning all. I'm from the UK, and running BOINC on a couple of virtual machines just for European / UK projects. I've just set up SIDock on one of those - Ubuntu Focal Fossa running five CPU threads under Virtualbox on an Intel Mac Mini. I set the relative share for SIDock to 100 initially - about 9%, and it immedately took all the available processing and put everything else into a wait state. I suspended all, set the relative share to 10 - about 0.9% and unsuspended the projects one at a time, leaving SIDock until last. As soon as I unsuspended it, it put everyone else back on hold and grabbed all the CPUs. So I currently have the project not allowing new tasks and am releasing them one at a time to give everyone else a look in. This is the first time I've experienced a project doing this - I'm not a master of BOINC, but have been running for about nine months with this setup. If I can't find a way around it, I'll make another VM with one thread and run it on its own, though that's not very efficient! Any thoughts?