Other projects that have Tasks that don't have fixed runtimes give a much better indication of a system's performance. The sooner it produces a Valid result, the more powerful it is.

Issue with 50% of all Rosetta tasks on this PC.:
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=4975041
Tasks will run for 50000 seconds yet only yield 6.5 points to 45 points. The other 50% of Rosetta tasks on this PC work as expected.
All other PCs are fine.
I have removed Rosetta from PC and run other projects, which work as expected.
Re-added Rosetta. Tasks worked well for 4 days, then reverted back to the above failure pattern.
The pc has no detected issues.
As Rosetta is working well on my other PCs, the error is obviously only shown under specific conditions.

Issue with 50% of all Rosetta tasks on this PC.:
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=4975041
Tasks will run for 50000 seconds yet only yield 6.5 points to 45 points.

There’s a problem somewhere that’s causing those tasks to get stuck without performing much useful work. The lines in the output like

BOINC:: CPU time: 50422.3s, 36000s + 14400s[2020-10- 4 18:25: 5:] :: BOINC

come from the watchdog ending the tasks 10 hours after their target 4-⁠hour run time. It’s odd that they validate as successful under those circumstances.

That machine is running the 32-⁠bit Rosetta application, which I suspect doesn’t get much testing these days. Perhaps there’s a bug in the application itself, or some compatibility issue with the OS environment, or even something strange going on with the virtualisation. Hard to say.

Issue with 50% of all Rosetta tasks on this PC.:
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=4975041
Tasks will run for 50000 seconds yet only yield 6.5 points to 45 points. The other 50% of Rosetta tasks on this PC work as expected.
All other PCs are fine.
I have removed Rosetta from PC and run other projects, which work as expected.
Re-added Rosetta. Tasks worked well for 4 days, then reverted back to the above failure pattern.
The pc has no detected issues.
As Rosetta is working well on my other PCs, the error is obviously only shown under specific conditions.

Just had a look at those WUs on my systems, and there are some WUs that pay out considerably less Credit than others, but no where near as low as what yours are doing.
And some of those with low Credit have produced many more Decoys than some of those with much higher Credit.
The only difference i can see is that i've process a lot more of them- more cores & threads in use & using the default processing time.

The benchmarks on that system are OK, and the system isn't losing time to doing non-crunching work, so i can't think of any particular reason for such a variation in Credit granted (although i do recall that someone had a host several months back that was exhibiting similar odd Credit payouts, but i can't remember the result of that particular issue)).




The amount of Credit granted depends on the amount of work done- which is the number of Models completed.
2 WUs of the same type running on the same system running for the same length of time may complete a similar number of Models, but one may produce only 1 Decoy, the other may produce hundreds. But both should get similar amounts of Credit as they did similar amounts of work (number of Models completed), even though the number of Decoys produced is different.

Processing a Task for a longer period will result in more Credit for that Task- but the Credit per hour will still be on par with processing it for a much shorter period of time. The only way to get more Credit per hour is more cores & threads, and/or higher clock speed and/or greater IPC (Instructions Per Clock).