About the Reporting and Fetching work I would like to suggest an improvement on the client's internal scheduling.

When I was processing a dozen or more GC units per day I could frequently notice a "stupid" behavior: BOINC sending a "report and fetch" a few seconds before the end of the job in process. With 5.10.7 and the big 3-day queue I had built at the end of GC I could even see BOINC sending a "Report and Fetch" while it was uploading results from the just-finished job!

If the scheduling routine delayed any "Report" or 'Report and Fetch" request between "estimated_end_of_job minus 5 or 10 minutes" and "end_of_upload" the validation process could be accelerated for the benefit of everybody, the host side which would see a faster turnaround of completed WUs, and the impatient end users waiting for points to be given. Still with the same number of database accesses, or even less if other ready-to-report units were already waiting (happened quite often with GC and large queues).

Is what I am thinking of clear enough? Cheers. Jean.

To get it right: The "Ready To Report" combined with Fetch requests are interspersed with large sets of 'Result File' uploads causing portions of the 'Ready to Report' to stay behind and when then reported, fetch more work?

Whether delaying that 'Ready to Report' reduces scheduler accesses, not sure as BOINC can handle up/download simultaneous. On an aside, you can even set the number of transfers it can handle simultaneous.

WCG presently puts 10 minutes in between sets of 10 max for a number of reasons, one being that the estimated flops in the files get translated to Time To Complete. After the 10, the client side scheduler determines if it needs more. Believe Fetch and 'Ready to Report' access same scheduler, thus at any rate reporting more than 10 results would always lead to at least 2 sets of downloads.

Anyway, there are special schedule 'beings' that have concocted this and see some reverse engineered logic.... but mine is not necessarily those of others.

Oops, the 'ambiguous' was already identified. A later 5.10 will phrase it so it means to indicate additional contact times and work block times. To work/network or not per schedule is set via the Activity menu, but are you looking for a box to enable / disable the extras?

OK, let's make it simpler for explaining, and only consider the general "everyday between hour of" line.

What I am thinking of is adding before "everyday between hour of", say, a popup showing "work" or "don't work". Giving a clear (and up to the user) result of

work everyday between hour of 09:00 and 18:00
or
don't work everyday between hour of 09:00 and 18:00

Am I improving a little?

And apply the same reasoning to each individual line of the daily schedule section below it.

Cheers. Jean.

okay suggestion: Get the throttle as smooth as the WCGCPUthrottle of Threadmaster. The Berkeley forum admin was not interested in TM incorporation as it only runs Windows.... but it has it figured out even of C2D Laptop and never does the fan kick in at 75%, in this heat.

Oh and lose the never right hours mins secs to go on a work unit


pointless and confusing