On 25/05/10 21:44, jay wrote: > On Tuesday 25 May 2010 07:49:33 am Martin wrote: >> On 25/05/10 00:20, jay wrote: >>> On Monday 24 May 2010 03:03:17 pm David Anderson wrote: >>>> The bottom line: as long as a host is sending correct results, >>>> it shouldn't have a daily quota at all. >>> >>> Exactly. >> >> Nope! >> >> An absolute maximum daily quota is still needed to catch fault >> conditions where Boinc doesn't know or can't detect any faults. I'm sure >> we all know that Boinc is far from complete and definitely not perfect! >> >> There still needs to be a daily maximum that is set to say x10 whatever >> is conceivably possible with today's hardware, or set to whatever the >> project *servers* can withstand without suffering a effective DOS attack. >> >> A finer absolute limit could be...
> > That's called "running the world for the sake of the 1%'rs", Martin > (In this case 1/10 of 1%) > It's also why the scheduler is so frakked up in the first place. I agree if you are alluding to the addition of lots of little 'special cases' for amelioration of project specific 'quirks'. I'm a strong believer in keeping it simple and keeping to the most robust general case that is practical. The comment about using an overriding daily maximum in case *Boinc itself* fails comes more under the description of "fail safe" or programming into the system "safety-in-depth"[*]. Regards, Martin Paraphrasing Wikipedia: [*] The idea behind the safety-in-depth approach is to defend a system against any particular failure using several, varying methods. It is a layering tactic, conceived by the National Security Agency (NSA) as a comprehensive approach to information and electronic security (defence in depth). This is also espoused for safety critical systems. -- -------------------- Martin Lomas m_boincdev ml1 co uk.ddSPAM.dd -------------------- _______________________________________________ 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.
