My computer laptop's power cord fizzled out and it took me five days to get a new one. meantime, apparently the projects i was working on in seti became impossible to complete by the due date. I have suspended the smaller, later-due task in hopes of decreasing the cpu time needed to completeand increased the memory usage to 20 mb, i dont think it's making much of a difference. is there something else i should do? let it ride? or cancel the project now in hopes seti can re-assign the task to a faster computer? i dont know how these things work,how important the due dates are , whether there are backups, redundancies, etc.

BOINC keeps track of the fraction of time that BOINC was not running at all. Since you have spent some time not running BOINC, the program believes that you will be spending this fraction of the time not running.

The best bet would be to just let it ride for a while and see what happens.

You could also edit client_state.xml to reset the timestats to more normal values.

---

BOINC WIKI

...I have suspended the smaller, later-due task in hopes of decreasing the cpu time needed to complete

You don't need to do that, BOINC switches to Earliest Deadline First (high priority) mode in such a case.

and increased the memory usage to 20 mb, i dont think it's making much of a difference.

In fact, no difference at all. The scince application takes all the memory it needs or (if your preferences are too low) won't run at all.

is there something else i should do? let it ride? or cancel the project now in hopes seti can re-assign the task to a faster computer? i dont know how these things work,how important the due dates are , whether there are backups, redundancies, etc.

That depends on how much time is needed beyond deadline. If a task is overdue, a new copy is sent to another computer, but if your task is reported before that one finishes, you'll get credits nonetheless. In any case, there's no science lost, just your computing time.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours