Why is granted credit always less than claimed credit?

Because your host is claiming more than the average host. Rosetta averages the claims per model then multiplies that with the number of models in your task to grant credit.

---

BOINC WIKI

BOINCing since 2002/12/8

Why is granted credit always less than claimed credit?

it isn't always, i have tasks were i have almost the double granted, then claimed. still for the same reason as mantioned above. rosetta takes the claimed credit. devides that by the number of decoys. and takes the average of many hosts. so it makes a credit per decoy. multiply your decoys with that number and you have the granted credit.

the claimed credit is based on your benchmark, runtime, and memory.

I have a curious issue with Granted...

I have 3 x Quad Core Q6600's, 2 x P4 2.8 & 1x P4 3.2.

The Quad's are often struggling to achieve the same RAC on Rosetta as the P4's.

The Quads have Result Duration Correction Factors in the region of 2.9, the P4's in the region of 0.5


On other projects, the quads are getting several times the RAC of the P4's, which seems in line with the published performance comparisons.

Any ideas as to what is going on??

---

The fact that you see the expected results on other projects eliminates much of the possibilities of other tasks consuming CPU etc. But it raises the other question. How do you get a steady comparable RAC if you share a system with other projects? Are your resource shares and number of seconds of CPU in the past 2 weeks the similar between the systems?

---

Rosetta Moderator: Mod.Sense

At the time of the runs described, Rosetta was getting ~70% of available CPU on essentially idle systems.

The Claimed credit seems to be in line with expectations for these CPUs, but the Granted is much, much lower.

Observed behaviour consistent as described across 3 x Q6600's and 3 x P4 2.8-3.2 (running with HT off).

P4's have been running for many months, Q6600's for a week or so.


Due to minimal credit, the Q6600's have now been adjusted to contribute primarily to other projects.

---

One of the "Interesting" WUs is https://boinc.bakerlab.org/workunit.php?wuid=118012427.

Note that there are 2 different values shown for Granted: 4.11 and 46.52

It would appear that the actual granted credit was 4.11


Also of interest (but possibly not related to the low Granted figures):

The Q6600, across all cpu types covered by boincstats is #49 of 3583 in points per cpu-second (http://boincstats.com/stats/host_cpu_stats.php?pr=bo&st=0&or=12)

For Rosetta, it is ranked at 140 of 1722 http://boincstats.com/stats/host_cpu_stats.php?pr=bo&st=0&or=12

This may be related to some interaction between the q6600 internal architecture and the rosetta application resulting in lower relative performance.

---

Will there be any credits granted, when there is 'compute error'. As the resources of the system have been used to arrive at this state, will there be any grace credits given?

Will there be any credits granted, when there is 'compute error'. As the resources of the system have been used to arrive at this state, will there be any grace credits given?

Yes. If you examine the task detail, you've got credits granted equal to what was claimed. An overnight job mops up these issues once a day. For some reason it never appears on your task summary page, but you do get them.

---

In the enchanting world of Aesop's Fables, there is a timeless story of a cunning fox and a tempting bunch of grapes. “The Fox and the Grapes” is a narrative that has been passed down from generation to generation, offering valuable lessons about resilience and self-reflection. Join us as we explore this classic story and discover the hidden wisdom it https://livros.wiki/

if you need story check out https://historinhasparadormir.com/