I expected about 10 times as much credit for -
http://yafu.myfirewall.org/yafu/workunit.php?wuid=4062127
- based on other WUs on this host.

I expected about 10 times as much credit for -
http://yafu.myfirewall.org/yafu/workunit.php?wuid=4062127
- based on other WUs on this host.

252 credits for almost 3 days' crunching - is it worth it ?
http://yafu.myfirewall.org/yafu/workunit.php?wuid=4121810

Runtime was 2,5 days, but (and I don't know why) CPU time was reported only with 4 hours.

Speaking of credits, I can't get my head around how they are awarded? Take this example -
One of my 32t tasks took 175,452.00 second and I was awarded 43,056.63 credits. Another PC did an 8t in 117,073.42 seconds and I was awarded 76,227.37 credits?? Same PC did another 8t WU in 114,693.71 seconds and was awarded 7,243.33 credits??

Is there a method to the madness?

Does running one type of w/u like 8t for example provide more credits than running 32t?

https://yafu.myfirewall.org/yafu/result.php?resultid=5073073

https://yafu.myfirewall.org/yafu/result.php?resultid=5072477

---

And this -
https://yafu.myfirewall.org/yafu/result.php?resultid=5082321

131,765.90 sec runtime for 1,835.66 credits (8t) Really??

I think this credit inconsistency hurts this project when it comes to gaining people to crunch YAFU.
If there's some way to fix this or if the community asks for it, would you consider a possible alternative to the current award of credits?
I ask this because I think it will improve the project participates.

---

It seems there's totally no relation between WU CPU time and credits rewarded... looks like credits are random generated.

This project uses the standard BOINC Credit system which happens to be "Credit New". You will find most people in the community are highly against its usage and have renamed it things like "Credit Screw" and have referred to it as a random credit generator. Several have spent years trying to make it make sense. Best to just support the "science" for what it is and not get too wrapped up in the credits here.

---

Here is another example of incorrect CPU time -vs- run time:
http://yafu.myfirewall.org/yafu/result.php?resultid=5592660

The task was running on a Pentium(R) Dual-Core CPU E5300 @ 2.60GHz
Run time 16 hours 55 min 58 sec
CPU time 3 hours 6 min 56 sec

I abandoned task because it quit accruing CPU time despite the Run Time increasing every second..
I am guessing CPU Time should of actually been close to 1/2 of the Run Time or aprox 8.5 hours.

Appears somehow the BOINC wrapper that the actual science tasks runs under lost track of what the science app was doing.

---

Here is another example of incorrect CPU time -vs- run time:
http://yafu.myfirewall.org/yafu/result.php?resultid=5592660

The task was running on a Pentium(R) Dual-Core CPU E5300 @ 2.60GHz
Run time 16 hours 55 min 58 sec
CPU time 3 hours 6 min 56 sec

I abandoned task because it quit accruing CPU time despite the Run Time increasing every second..
I am guessing CPU Time should of actually been close to 1/2 of the Run Time or aprox 8.5 hours.

Appears somehow the BOINC wrapper that the actual science tasks runs under lost track of what the science app was doing.

It seems your dual core pc's only have 2GB to 3GB of ram, I wonder if the task is spinning it's wheels due to not enough ram?

Have you tried going into the Boinc Manager to see how much each task is using? Click on a running task and then to the left click on properties and near the bottom it will show something like this:
Virtual memory size 33.12 MB
Working set size 22.60 MB

That's the number for a NON Yafu task as I don't have one running on this pc right now but you get the idea.