Real world, C's STD does not go to MAX_STD, it stays near 0.
The behavior of letting the STDs float is going to be extremely hard to
predict because of the clipping at the high and low ends. I regularly have
projects that are pegged at MAX_STD because on a multi CPU machine their
resource share sufficient to do so if they only have one task available.
This may tend to have all other projects have the same STD.
Long Term Debt floats toward a max of 0 instead of snapping directly to 0.
Perhaps STD should do the same with a min of 0. I have to think about what
that does to the debts.
jm7
David Anderson
<[email protected]
ey.edu> To
Sent by: [email protected]
<boinc_dev-bounce cc
[email protected] [email protected]
u> Subject
Re: [boinc_dev] Short Term Debt.
12/07/2009 01:53
PM
Actually, looking at the code, we're already doing this.
The needed change is to not set the STD of non-runnable projects to zero;
instead, let them float around with the others.
-- David
David Anderson wrote:
...
>
> An alternative: add the normalizing offset to non-runnable projects.
> In the above case, C's STD would go to MAX_STD,
> and it would start off on equal footing with B,
> which is the correct behavior.
_______________________________________________
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.
