I'm noticing an odd behavior in BOINC Manager. Perhaps this is always the case and I'm only noticing it now because the Amicable task completion times are usually less than 60 seconds, often less than 30 seconds, on my PC.

There is always another task ready to start. As soon as the running task reaches 100% the next task and its elapsed timer starts. I timed the new running task with a stopwatch. BOINC reported 38 seconds to finish. But the stopwatch timed 108 seconds!

The stopwatch time accurately reflects my task throughput over many hours.

Like I said, I haven't noticed this in any other project. Is anyone else seeing this?

Thanks

I'm noticing an odd behavior in BOINC Manager. Perhaps this is always the case and I'm only noticing it now because the Amicable task completion times are usually less than 60 seconds, often less than 30 seconds, on my PC.

There is always another task ready to start. As soon as the running task reaches 100% the next task and its elapsed timer starts. I timed the new running task with a stopwatch. BOINC reported 38 seconds to finish. But the stopwatch timed 108 seconds!

The stopwatch time accurately reflects my task throughput over many hours.

Like I said, I haven't noticed this in any other project. Is anyone else seeing this?

Thanks

Yes I see it everywhere, I THINK it's got to do with what the Project counts as cpu in use time as opposed to what goes on on our pc's, ie spin up time, crunch time, spin down time, rinse and repeat over the many tasks we run. I have never done the stopwatch thing but do run the Boinc Project http://wuprop.statseb.fr/ which counts the hours we run at each Boinc Project our pc's crunch for. Primegrid is really bad as I can run a task that runs for over 5 minutes but I only see 1.5 minutes on the valid task time at both wuprop and Primegrid.