> OK, you had a 4 core system. How much OTHER work was there. If the amount > of other work on the system makes the resource fraction for that project > 0.125, then the rr_simulator comes up with an answer of 80 hours till > completion again.
I do not at all understand bringing in "how much OTHER work was there". If you go back and re-read my original post, you will see that I said: >> So why does "scheduling" think there is a potential missed deadline? >> The only answer I can come up with is that "resource share" is being >> factored in - if this is one of five projects, then 20% (they all >> have equal shares) of 70 hours is 14 hours - not enough to do the >> estimated 40 hours of work. But this is a four-core system -- so >> 20% of (70 * 4) is 56 hours of crunching that this project is >> "entitled" to in the next three days. My understanding of the "resource fraction" is that it is dependent only on the relative "Resource Share" values for the various projects attached by that system, and __not__ on "how much other work was there". [If "resource fraction" is affected by an attached project being unable to provide work, that would not *decrease* the "resource fraction" given this project (which did send work).] Please excuse me that I did not describe everything plainly in my original post. That system actually *is* attached to five projects - for each the "Resource Share" value of 100 has been specified (they are all equal) - so the number of other projects makes the "resource fraction" of the project that went into EDF no less than 20% (not 0.125 as you speculate). I fail to see how "how much other work was there" has any bearing on the decision to run this project in EDF. As I said in my original post [derived from a calculation similar to yours - my calculation multiplied the available time by the "resource fraction", whereas your calculation divided the needed crunching time by the "resource fraction" - both methods of calculation arrive at the same ratio of (needed_crunching_calculation) versus (available_calculation)]: >> A need to do 40 hours of work in three days will potentially miss >> the target if there are actually less than 56 hours available to >> this project in that time span. But if they are not available to >> *this* project, it must be because there is an even greater need by >> another project. Yet none of the other projects are running in EDF. To repeat, >> For me, this case does not add up to a "potential missed deadline". mikus _______________________________________________ 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.
