I have been crunching for 26 hours and it reached 93% with 1 hr 33 minutes left now it has decided it is really 60% done and 16 hours left so this looks it will run for 42 hours for 420 points or 10 points an hour whereas most other projects are much better than this

now it has done 31 hours with 19 still left

I am going to abort it so 31 hours wasted

time to detach from the projrct

If capacity of your computers does not suffice for reception more than 10 credit in an hour are does not say that the project is worse than others...

I've seen this many times before. If I recall correctly that 60% mark is a checkpoint. So for whatever reason your WU stopped and restarted it continued from there. Increased checkpointing would fix this issue.

---

me@rescam.org

Because cosmo checkpoints seem to be far apart make shure
that `Leave applications in memory when suspended` is ticked for `yes`
otherwise you will loose work after a checkpoint restart.
Its one possible fix for the problem.

Even with leaving apps in memory I have seen C@H drop abruptly from 25 hours remaining to 7+ hours remaining, and continue from there. Go figure.

Because cosmo checkpoints seem to be far apart make shure
that `Leave applications in memory when suspended` is ticked for `yes`
otherwise you will loose work after a checkpoint restart.
Its one possible fix for the problem.

Now there's one way to max out your memory quickly.

---

me@rescam.org

I observed this phenomenon soon after I joined Cosmo group. Some WU's were completing o.k. but one in particular had gone through 14 suspend/resume iterations and was always resuming at the 60% progress (check)point. My dual CPU system works on Seti (66%) and Cosmo (33%) so the BOINC rescheduling algorithm inherently suspends WU's at intervals far shorter than their run times. For the WU in question the elapsed time was >28 hours when I stumbled upon the utility of the "leave app in memory" setting. After updating BOINC preferences with that option the WU finished in ~7 hours. Otherwise I believe that WU would never have finished, and certainly not before its deadline.
Yeah, it does use lots of memory (typical Cosmo 300MB to 700MB) but in my 2 GB RAM system I don't have any problems even when 2 Seti's (~40MB each) and 2 Cosmo's are either running or "waiting" to run. I presume, but have not tested it, that should more RAM be needed by no-BOINC processes their RAM contents would be saved in swap disk space and restored when needed.

---