The benchmarks test the speed of your CPU. The result is used in calculating th e(approximate) time remaining for processing a Result and for calculationg the credit the Client claims (roughly CPU_time * benchmark_value).
> So can credit be swindled by running benchmarks at full speed then throttling
> the processor to lowest?
Not really, for several reasons.
1. The benchmarks are automatically redone from time to time.
2. It would take you a lot longer to finish the work to get the extra pending credit.
3. Your pending credit would be excessive compared with the others in the quorum.
The final effect of all this would be that you would be truncated back to a normal score in most cases (the score that the other users achieved) and would be getting less work done so your score would be increasing more slowly than if you left everything alone and played fair.
Even more of a disincentive would be the fact that you would trigger the "cheater detection" routine buried deep in the code that picks up "unusual" pending credit claims and does nasty things to your reputation with the user community ;) :).
Then of course if you get caught multiple times, you trigger the "three strikes and you're out" policy, and that has such dire consequences (excruciating withdrawal symptoms) that you'd need an extended stay in the "clinic" under the sternly severe and watchful eye of Nurse EinsteinOlga ;) :).
To get back on topic and make a suggestion to elfowl03, this particular board is for reporting bugs and problems with the code directly to the developers. If you would like them to be able to spend their time most effectively in fixing bugs and writing code, please ask "getting help" or "getting started" type questions in the appropriate forum where you will find a large number of helpful people who will do their best to point you in the right direction. That way you are not distracting the developers unduly. Please don't take this in any way as a criticism as it is simply intended to be a helpful suggestion.
Can someone explain what Bench mark does please
)
Benchmark are used to:
1. estimate the time of processing a WU and by this estimate the number of WU's to send to your PC.
2. calculate the so called credit.
Greetings from Belgium
Thierry
The benchmarks test the speed
)
The benchmarks test the speed of your CPU. The result is used in calculating th e(approximate) time remaining for processing a Result and for calculationg the credit the Client claims (roughly CPU_time * benchmark_value).
BM
BM
> The benchmarks test the
)
> The benchmarks test the speed of your CPU.
Thank you to you both. My guess was correct then.
:-)>
>
So can credit be swindled by
)
So can credit be swindled by running benchmarks at full speed then throttling the processor to lowest?
"My other computer is a virus farm."
> So can credit be swindled
)
> So can credit be swindled by running benchmarks at full speed then throttling
> the processor to lowest?
Not really, for several reasons.
1. The benchmarks are automatically redone from time to time.
2. It would take you a lot longer to finish the work to get the extra pending credit.
3. Your pending credit would be excessive compared with the others in the quorum.
The final effect of all this would be that you would be truncated back to a normal score in most cases (the score that the other users achieved) and would be getting less work done so your score would be increasing more slowly than if you left everything alone and played fair.
Even more of a disincentive would be the fact that you would trigger the "cheater detection" routine buried deep in the code that picks up "unusual" pending credit claims and does nasty things to your reputation with the user community ;) :).
Then of course if you get caught multiple times, you trigger the "three strikes and you're out" policy, and that has such dire consequences (excruciating withdrawal symptoms) that you'd need an extended stay in the "clinic" under the sternly severe and watchful eye of Nurse EinsteinOlga ;) :).
To get back on topic and make a suggestion to elfowl03, this particular board is for reporting bugs and problems with the code directly to the developers. If you would like them to be able to spend their time most effectively in fixing bugs and writing code, please ask "getting help" or "getting started" type questions in the appropriate forum where you will find a large number of helpful people who will do their best to point you in the right direction. That way you are not distracting the developers unduly. Please don't take this in any way as a criticism as it is simply intended to be a helpful suggestion.
Cheers,
Gary.