I guess it is all dependent on how they measure it... A user's PPD averages out over time because the running average takes points per day and averages them out over a number of days - to my knowledge the Client Stats page is only recording per day, not over a number of days, so it is quite different to average ppd...7im wrote:WUs have an internal tally of the FLOPS count and is reported with each WU. So yes, and no. Multi-day WUs would reduce the the count, if only a few WUs were running. But with thousands running, it averages out so no drop. Kind of like your PPD averages out over time.
It would be accurate if FLOPS measurement was analogous to calcuating by the number of FLOP performed per WU and then divided by the length of a day. I guess you and bruce are saying their measurement does take this into account and therefore adjusts for the relative 'size' of the WU... Which would make sense seeing as it is a pretty important to a lot of people.
If it was just the speed of the computer in FLOPS as measured by the client (which I use to see when I ran a Linux client) then my understanding would be that if a WU completed every second day it would average out, over thousands of users, at half the rate as every second day your client would report back with its FLOPS rate... Other clients would report back on your 'off day', but they also wouldn't be reporting on your 'on day'. As FLOPS is a instantaneous measurement your client would report the same number of FLOPS on a one day WU as a multi-day WU... If it is this way then any project that takes longer to return would have a marginal difference on reported TFLOPs proportional to the length taken to fold:
i.e. if WUs were smaller than a day every day you'd report 50GFLOPS day 1, 50GFLOPS day 2, 50GFLOPS day 3, 50GFLOPS day 5 => (50+50+50+50) / 4 = 50GFLOPS/Day
However, if larger and your client reported every second day it'd average out as: 50GFLOPS day 1, -- GFLOPS day 2, 50GFLOPS day 3, -- GFLOPS day 4 = > (50+ 0 + 50 + 0) / 4 = 25GFLOPS
That's ignoring how they handle multiple WU returns by individuals of course.