I would guess it makes more sense for CPDN to abandon the old "credits per
trickle", i.e. compute all the user, host, team credits, then switch to the
"CreditNew" BOINC system when it's ready. The "credits per trickle" was good
when there were a few apps that took 4-6 months to do, but now that there's 27
CPDN climate model experiments and take within a month I think it makes more
sense to go with the new automated way. Computing credits from trickles in the
bloated database now probably takes a full day (Tolu & Milo can confirm if they
are on this list)?
I'd also like to see a way to automate "non-CPU" jobs like QCN, which grants 50
cobblestones for day "run-time" monitoring a sensor (i.e. no FLOPS involved).
I pretty much carried my old CPDN "credits per trickle" system over and even
that gets bogged down (about an hour to recompute) so it would be nice to
switch to a simpler & faster system. Could some sort of system be put in
"CreditNew" that would handle projects that grant based on "wall clock time"
run or network traffic used or disk spaced used etc? although I guess it comes
down to a project trying to mimic how much credit s...@home would have given
etc.
_______________________________________________
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.
