>It is when you consider that this is now an explicit policy and that >the latest versions are getting worse and worse at it ... to the point >where as I have pointed out that if you try to run Collatz and MW GPU >applications you will have dominance by Collatz regardless of >settings ... I have not yet tried a "sharing" by three projects >because of how BAD BOINC is proving with even only two ... and add on >top of that it is demonstrable that the debt numbers are not properly >maintained ... Seen something similar for CPU only apps too. BOINC doesn't honor project shares by downloading full cache of Einstein tasks (used as backup project on my hosts) then immediately going into high priority mode and crunch them all.
>. with HT >machines coming back as a big technology this is a very bad choice as >we proved years ago when HT first hit ... a good mix of projects makes >HT work far more efficiently and effectively. "Project/app pairing" proposal, was twice closed already... http://boinc.berkeley.edu/trac/ticket/843 _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
