I just thought of another problem that should be easy to overcome.
Currently the runtime for each task is wall time. We will need to split
CPU from the conversion factors to generate wall time again. I know that
sometimes my machines do real work that takes a significant portion of the
CPU, reducing that available to BOINC projects. I do not believe that we
want wall time incorporated into the credits calculations, but rather the
actual CPU time.
jm7
David Anderson
<[email protected]
ey.edu> To
Sent by: [email protected]
boinc_dev-bounces cc
@ssl.berkeley.edu BOINC Developers Mailing List
<[email protected]>
Subject
08/31/2009 11:45 Re: [boinc_dev] [boinc_alpha] Card
AM Gflops in BOINC 6.10
There are big advantages to granting constant credit per app;
it eliminates the incentive for credit cheating,
and the need to check for it.
It should be possible to prevent cherry-picking,
e.g. by resending aborted jobs.
-- DPA
[email protected] wrote:
> This does allow cherry picking. A custom client could reject all tasks
> that were going to take longer than average if that was known, as in High
> versus Low angle ranges on SETI. It would also grant full credit for
noisy
> SETI tasks (15 seconds and quit).
>
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
