I am running Seti@Boinc on an older laptop Compaq Intel Mobile 233 64meg (I know small machine). The issue is this; When it starts working on a WU it goes along very fast, then it starts moving slower. Yesterday I downloaded a new WU and it took about 1.5 hours to get to 51%. In the 17 hours since then it has only progressed 20%. By the time I get done with a work unit it has taken abouit 60 hours. I have even tried re-booting to see if this helps, nothing. Keep in mind that this happens on EVERY work unit.

Any ideas why crunching is so fast then gets progessively slower?

Thank you.
>

I don't know why this happens. My AMD athlonXP took a WU to 60% in 3 minutes then slowed down to taking the full, normal 6 hours.

Hi

This is a calculation error in seti client.
It will be fixed later, because its an cosmetic issue.

greetz Mike

My understanding of the rumor control word is that part of what was done with 4.09 was intended to address this issue. Note, I did not ssay it fixed it, but it should be a little better with 4.09 (note: rumor control can get it wrong).

Just think of it as a gas gague in a car. None of them are linear. After you buy a car you have to drive it for awhile before you know if 1/4 tank is 1/4 of a tank or really 1/2 or 1/2204 left. You know the kind, when it hist 1/4 take you had better be pulling into the station for gas...
<p>
For BOINC Documentaion: Click Me!

Each loop through the seti app takes longer than the previous one. The frequency sensitivity increases each time. This is not really a bug just the way the program works.

John Keck -- BOINCing since 2002/12/08 --

The old SETI Client also had (depending on Angle Range) a similar behaviour.

e.g. on VLAR Workunits, I saw it zooming through the first ~8% at light speed, afterwards constant progress far below that.

On normal AR Workunits, first ~7.5% above average speed, ~7.5% to ~78% normal speed, and then accelerating again beyond ~78%.
(all observed on Win32 Clients)

Looking at the Graphics during the first ~60% should show exactly what it does, I reckon it's doing all the (very fast) Pulse/Triplet search, after that it switches to the (intensive and relatively slow) FFT calculations including the best Gaussian shaping.
___________________________________________
<p>Scientific Network : 36200 MHz «» 8204 MB «» 815.0 GB </p>