Hello,

I sometimes catch tasks which run for an unusually longer time. My run time is set to four hours and those show low completion rates even after longer hours. I kill them as soon as i see them.

Does anyone else have the same problem. Is there an explanation ?

Edit: They also guzzle huge amounts of RAM but sounds like some bug.

---

R@h has a "watchdog" function, which will shutdown a task if it runs for more than 4 hours (of CPU time) passed the target runtime. So, they will get cleaned up.

Sometimes when more memory is consumed, tasks do not get as much actual CPU time as they normally would. The properties of the task show you the actual CPU time the task has used (which will always be somewhat longer than the "wall-clock" time).

If you can let things clean themselves up, it becomes much more clear to the project team that the specific WU had problems running normally. Otherwise, if you end the task, it is marked as being ended by the user and more easily goes unnoticed.

---

Rosetta Moderator: Mod.Sense

Thank you for your very quick answer. :)

I think i understand the problem, but my computer is not a dump.

Edit: I don't know if that still happens but in the pasts i had had WU's running 12 hours instead of 4.

---