I thought since I'd set Boinc to run with the app in memory while suspended I would be ok ....
When you stop BOINC to do the switch from 6.06 to 6.07, the app is no longer in memory and the restart is bound to use the out-of-date .cpt file unless you have "refreshed" it just prior to the switch.
When you stop BOINC to do the switch from 6.06 to 6.07, the app is no longer in memory and the restart is bound to use the out-of-date .cpt file unless you have "refreshed" it just prior to the switch.
Yep, but I didn't do a switch to 6.07 since my XP isn't SSE2. The switching was between Seti and Einstein tasks. It's no big deal I'll just finish it, disgregard the results, and move on to the next crunch.
You could have avoided the loss by deleting the offending checkpoint (.cpt file in the relevant slots directory) and watching for a new one to be written. Doing the switch to 6.07 immediately after this would have avoided the loss.
Yeah, that helped immensely. Not... restarted from zero after it was at 65.5%.
Oh well, not in a hurry anyway. :-)
Follow on from slow unit, it finally finished in 7:12 about one hour slower than normal. So I assume something, but no idea what, slowed it down in the first two hour period. It's not AV scan as I do that in Seti's maint period on Tues, and I was sleeping during that period, so not using computer. Weird.
You need to remove all the wrongly included 6.06 stuff that is bloating the zip archive. The 6.07 files work fine on an SSE host so thanks for the quick turnaround.
RE: I thought since I'd set
)
When you stop BOINC to do the switch from 6.06 to 6.07, the app is no longer in memory and the restart is bound to use the out-of-date .cpt file unless you have "refreshed" it just prior to the switch.
Cheers,
Gary.
RE: When you stop BOINC to
)
Yep, but I didn't do a switch to 6.07 since my XP isn't SSE2. The switching was between Seti and Einstein tasks. It's no big deal I'll just finish it, disgregard the results, and move on to the next crunch.
RE: You could have avoided
)
Yeah, that helped immensely. Not... restarted from zero after it was at 65.5%.
Oh well, not in a hurry anyway. :-)
Follow on from slow unit, it
)
Follow on from slow unit, it finally finished in 7:12 about one hour slower than normal. So I assume something, but no idea what, slowed it down in the first two hour period. It's not AV scan as I do that in Seti's maint period on Tues, and I was sleeping during that period, so not using computer. Weird.
Next unit is doing fine 12.7% in 45 min.
RE: I'm ready to test the
)
Look here.
BM
BM
RE: RE: I'm ready to test
)
You need to remove all the wrongly included 6.06 stuff that is bloating the zip archive. The 6.07 files work fine on an SSE host so thanks for the quick turnaround.
Cheers,
Gary.
RE: Is it me or is 6.07
)
I checked with the ref WU, in all SSE versions (_0 , _1 , _2), and 6.07 has same speed than 6.06.
As expected...
Cheers,
Alex.
God created a few good looking guys.. and for the rest he put hairs on top..