Credit differences out of range?

[Mad Matt]

Just looked into some strange credit differences on team results, these seem quite massively out of range:

1.4 credits/101.79s = 0,01375 C/s * 3600 = 49,51370 Credits/hour
61,28 c/6309,65s = 0,00971 C/s * 3600 = 34,9635875 Credits/hour

Indeed a massive difference

Code: Alles auswählen

[b]7888060 [/b]3300703 30 Sep 2010 2:40:12 UTC 1 Oct 2010 10:30:26 UTC Completed and validated 103.10 101.79 0.70 1.40 cmsearch v0.14  

[b]7472634[/b] 3291400 29 Sep 2010 4:55:54 UTC 1 Oct 2010 10:30:26 UTC Completed and validated 6,309.65 6,315.72 43.39 61.28 cmsearch v0.14  

I noted that on task 7472634 CPU time is higher than run time. Maybe checkpointing didn't work on a reboot?

Crosscheck task:

Code: Alles auswählen

[b]7472637[/b] 3291401 29 Sep 2010 4:55:54 UTC 1 Oct 2010 10:30:26 UTC Completed and validated 3,692.60 3,679.97 25.28 36.32 cmsearch v0.14  

36,32 c / 3679,97s = 0,0098696 c/s * 3600 = 35,530724 Credits/hour. So pretty much the same as above.
Any ideas?

[yoyo]

Granted credit is calculated in this way:

granted_credit= 2 * min( claimed1, claimed2)
Claimed is f(run_time, flops_of_host)

yoyo

[Mad Matt]

Granted credit is calculated in this way:
granted_credit= 2 * min( claimed1, claimed2)
Claimed is f(run_time, flops_of_host)

Cheers, Yoyo. So this means you will see different results on different hosts - again depending on your wingman's host. There is no difference between the WUs itself, if I get that right?

[yoyo]

No difference between the WUs. All are calculated in the same way.
yoyo