Boinc has the possibility to set any number of CPU-cores.
So it is possible to run 2 or 4 or 8 or 16 WUs on one CPU-core.
The WUs end always at about 4-5h run time - no matter how much cpu time they needed.
An old 4core Athlon CPU can get more credits than an state-of-the-art 16core 5950X cpu, when setting the number of cpu cores on the Athlon to 64.

Please change this from run time to cpu time - like all other boinc projects are doing.

I cannot think of a single BOINC project where it makes sense to run more than one WU per CPU logical thread. It increases the chance of returning inaccurate results. This project doesn't even use confirmation, i.e. Quorum = 1. They would not run faster if you use <cpu_usage>0.5</cpu_usage>.
This projects awards 200 credits per completed WU regardless of how long it took to run.
Implementing credit that is proportional to CPU run time would be nice.
Even better would be to implement checkpointing.
Also nice would be badges.

---

In November a problem with the allocation of credits by the CPU time based BOINC mechanism was reported:

>18000s and 8.33 credits.
>Normally I get 90cr for 9000s.

Then I changed my credit allocation: credits per completed WU regardless of how long it took to run.

I can't understand why the basic BOINC mechanism doesn't work properly for this job .....

It seems that the 200 credit and the run time are fix - no matter which calculating power a CPU has, right?

Is it not possible to divide the CPU time by the run time and multiply this result with 200?
Then 2 WUs on one core would get only half of the credits, 4 WUs get 25% and so on.

Another good reason to use CPU-time:
If you get some WUs, start calculating and set the clock to +5hours, the calculation is immediately finished and one gets the full credits.
Using the run time is really a bad idea.

I will try to use a CPU time based mechanism

200 for 4 to 5 hours work is not too bad, I have seen far worse on some other projects.

Fixed credit is a preferred option to guard against people who see the need to cheat, might not beat them but reduces there effect on the project.

Conan

---

I will try to use a CPU time based mechanism

Has this been tried?