Welcome to MilkyWay@home

Posts by hoolibas

1) Message boards : Number crunching : N-body sim processing time issues (Message 69632)
Posted 31 Mar 2020 by hoolibas
Post:
It's a computer that has been on previously. It's just been thru a move and a couple reformats (and renames). It runs single core tasks fine, it's been steadily crunching away at tasks for Milkyway, Rosetta, and Asteroids @home since I reinstalled BOINC. It just seems hit or miss on the 3-CPU processes.

Since the deadline was looming and advice was rolling in slow, I abandoned the tasks so that they go back into the pool for crunching/validation.
2) Message boards : Number crunching : N-body sim processing time issues (Message 69630)
Posted 30 Mar 2020 by hoolibas
Post:
I've already pruned all of that stuff. right now the PC is set to have 75% of processors to handle BOINC tasks (for 90% of time), leaving 1 core to handle the Windows processes. As it is, it's currently running at ~72% of CPU utilization working on one of the 3-CPU tasks.

However the ~3 hour tasks inflate to days worth of processing.
3) Message boards : Number crunching : N-body sim processing time issues (Message 69628)
Posted 29 Mar 2020 by hoolibas
Post:
I have several N-Body sim tasks on one of my PCs (core 2 quad). All require 3 CPUs, when it comes time for them to process, the roughly 3 hour task turns into "elapsed - ~8:30:00 ; remaining (est) - 23 days x hours, etc" Which would put the task (well) past the deadline.
If I suspend all processing and restart BOINC, the Elapsed time drops (usually significantly) and the remaining estimate goes back to a reasonable duration, only to hyper-inflate once the task start running again.

Is there anything I can do or should I just bail on these tasks? And if no other option; how can I prevent this one PC from getting them again but leave my other PC able to get them?




©2023 Astroinformatics Group