very low credit (4 points per task).

Hi

I've received 4 BOINC credits for the Eternity II CPU solver (pilot) v2.20 windows_x86_64 tasks

But I'm now getting 32 BOINC credits per task, for the Eternity II CPU solver (pilot) v2.28 windows_x86_64 tasks

As this is a new project, it might be that the admins will be monitoring how things are going will make adjustments accordingly.

regards
Tim

Tim is right, and thanks for answering while I was away.

The credit was raised from 4 to 32 per validated task. The 4 was a
placeholder I set when standing the project up and never revisited - that
one is on me, and pascal768 was right to flag it.

On the remaining work, in the interest of being straight with you: the
application is still marked "pilot" for a reason. Task durations currently
vary a lot - I have measured tasks finishing in about 80 seconds of CPU time
while the client was estimating over 3000 seconds for the same work. That
means credit per hour is not yet consistent between tasks, and BOINC's own
runtime estimates are not yet reliable either.

My next step is to measure the real spread of task durations and make the
work units more uniform, so that credit per hour becomes predictable. I will
post the numbers here when I have them.

If you see tasks that look badly out of line with the others, please say so
in this thread - that data is genuinely useful right now.

The tasks now take 3 to 4 times more time to complete but the credit has remained the same at 32.

pour infos concernant les crédits car bitboinc a le meme probleme.

for information regarding the credits because bitboinc has the same problem

https://bitboinc.athena.org.tr/forum_thread.php?id=4&postid=55#55

---

Guests cannot read the link/forum.
In this case the project has given too much credits and lowered but still too high as discussed in chat.

rechercher "too much credits" sur le forum de bitboinc et vous verrez.Cela peut servir de point de départ correct.

Search for "too much credits" on the bitboinc forum and you’ll see. This can serve as a good starting point.

---

Thanks for flagging this, and pascal768 for the pointer. You were right that the reward had fallen behind: once the work units got longer, 32 credits was far below what other projects pay for the same CPU time. Work units created since this morning carry 150 credits, and we're sizing them to about 30 minutes each. Tasks already validated keep their original credit.

As an example, rebirther adjusts the credit at the SRBase project when new bases are loaded that require more/less computation requirements. If needed, run new work on a standard PC and adjust credit to a given credit/hr so that no matter the run time of new work the credit is normalized.

Agreed, and that's the approach we've taken. Credit is now tied to a target rate per hour of CPU on a standard machine, and new work is sized to about 30 minutes each at 150 credits. When the workload changes, we'll adjust the size of the work units to keep that hourly rate, rather than letting credit drift. Thanks to you and rebirther for the SRBase example; it was a helpful reference.

7 Oct 2026, 10:37:42 UTC 7 Oct 2026, 11:32:11 UTC Completed and validated 3,235.38 3,232.30 300.00 Eternity II CPU solver (pilot) v2.35 x86_64-pc-linux-gnu

300 credits with the 2.35 version. 3235sec (54 min) on my old boinc rig (Xeon CPU E5-2699A v4 @ 2.40GHz). I don't know what is concidered a 'standard pc' today when setting how much credit it should be.

AVX had no advantage, a standard PC is based on an i7.