I see a lot of things like these: http://albertathome.org/workunit/38376, where the task starts and doesn't finish in the same run, but is either suspended or exited and later restarted. When it restarts, it runs for ages (33,431s).
When it starts and runs continuously, it's something like http://albertathome.org/workunit/37540 (7,184s). So why will a task that was suspended or exited take up to 4.5 times as long as normal to finish when later continued? This happened with v1.19 as well.
Copyright © 2024 Einstein@Home. All rights reserved.
On the restart
)
Well since I run other projects too, I have always this runtimes.
Right now one WU is sitting and hogging with 100% done. I did already save the slot files.
stderr tells at the end 'called boinc finish'.
But it still runs.
Christoph
Hello. When a new
)
Hello.
When a new application, I have to delete the tasks to the old application?