... and I'm arguing that they should be. For every project, in the best possible manner.
I don't have a problem with cobblestones = k * FLOPs. I have several problems with credit = k * cobblestones. .... starting with the fact that we aren't directly calculating cobblestones. So, the AUTOFLOPS script takes a set of machines, calculates what the credit SHOULD HAVE BEEN based solely on the definition (just like 1 meter is defined as as the distance travelled by light in free space in 1⁄299,792,458 of a second, a cobblestone is defined by a formula, and it is defined in terms of whetstones and dhrystones), and returns a corrected scaling factor from FLOPs to Cobblestones. Martin wrote: > Lynn W. Taylor wrote: >> Martin wrote: >> >>>>> credits = k * cobblestones >>>> ... and I believe that K is 1. >>> "k" can be anything depending on: >>> >>> what a project does that is different to s...@h; >> You're missing the one critical point. >> >> Cobblestones are *defined*. >> >> There is a *definition* that says "credit is claimed based on this >> formula...." >> >> If a cobblestone is a cobblestone, then "k" MUST BE EXACTLY 1. >> >> If a cobblestone isn't a cobblestone, then we're talking about something >> else. >> >> The Autoflops script takes something that isn't cobblestones, and >> converts it to something that is. > > > I'm arguing that the 'credits' that we actually see reported are not > really 'cobblestones'. > > What we see is some "fudge-factor * s...@h-flops-count" that variably adds > up to approximately the 'expected' cobblestones. The variable nature of > the processing for s...@h due to the AR dependence of the s...@h-wus > compounds > the inaccuracies and problem still further. > > > Regards, > Martin > _______________________________________________ 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.
