Elapsed time in BOINC: 6:12:45 ---> 22,365sec

Task Page says: 20,045sec

Why the difference?


Claimed: 124.74 Granted: 213.76
Corrrection Factor: 1.7761
124.14 * 1.7761 = 220.49

Does the correction factor adjust the points? I thought points were points, regardless if it took 1 hour or 24 hours to do one task. I was just wondering, because 213 is really close to 220.

I guess my main question is why the two different times that are 2320 seconds apart? That's 00:38:40 difference. I'm confused...

One may be CPU/GPU time, the other wall time.
There is often a difference between requested and received rocks, esp. when using a GPU. On Collatz, for instance, my received rocks are consistently ~200x my requested. I like to think of it, however incorrectly, as a bonus for quick turnaround of WUs.

---

Cheers,

PeterV

.

That makes sense. I'm running GPUGRID at the same time and that steals some CPU time, which would make the MilkWay wall time a bit longer I suppose. Reversing the logic, if MilkWay used some GPU time and included it with CPU time, the wall time would be shorter?

I suppose as long as I'm getting bonuses... I should try to figure out how to get more bonuses!

Thanks for the reply!

I suppose as long as I'm getting bonuses... I should try to figure out how to get more bonuses!

You aren't really getting a bonus. You are getting precisely what you should be getting. The project server sets the amount of credit and everyone would get exactly the same credit for that task, irrespective of what was claimed. Your client will make a 'claim' which is based on your machine's benchmarks and the amount of time taken to do the crunching (amongst other things) and in the old days projects used to grant credit based on what was claimed. These days sensible projects don't do that anymore - everyone gets the same for the same work.

With respect to your question about 'correction factor', this is nothing to do with a correction to the credit claim. It's to do with a correction to the estimate of the time that a task should take to crunch on your machine. As an example, imagine that the server had estimated that your task should have taken around 11,286 secs to crunch. If it actually took 20,045 secs, the duration correction factor (DCF) would be 20,045 / 11,286 = 1.7761. BOINC uses the duration correction factor to refine the estimate provided by the server so that it can keep a proper cache of work on your host. In other words BOINC always adjusts the estimate provided by the server to make the local value displayed in BOINC Manager as accurate as possible. BOINC is continually refining the DCF as things change.

---

Cheers,
Gary.