No, Dagorath, you possibly misunderstood, what they said.

Me and my 1 track mind. It's like a wheel in a wagon rut sometimes. Keck set me straight once but I slipped back. I'm OK now :)

And any idle core will be immediately supplied with work. (Except that you (well, mitrichr) have revealed a bug in the client.)

Peter

Yes, seems like a bug but there may be some other explanation. I'll see if I can reproduce it here.

@mitrichr: On which version of BOINC did you see this apparent bug?

5.10.45

---

http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

That much I understood. And I understand the safety margin in the above formula is 24 hours, yes?

It depends on the version of your client, some it is the connect setting, some it is 24 hours. There is also an 80% fudge factor in some of the calculations.

If the task if finished before the report deadline, but after the last connection before the report deadline, it is going to be late anyway.

Maybe I don't understand this last sentence but that doesn't sound very user friendly... to have a finished task sitting there, the result presumably uploaded, needing only to be reported, and BOINC just sits there and allows the deadline to expire without reporting the task. I mean if the connect every X does not restrict the number or frequency of connections BOINC can make then why would BOINC not send the report before the deadline? Have I misunderstood what you're saying in that last sentence?

Remember the assumption with the connect setting is that the client will go at least this long between connections. So it will not be able to report in this case because there will not be a connection in time.

Actually, in the formula quoted, the safety margin is either 24 hours (older version) or 0 (newer version). There was a completely different formula for even older versions (which I hope that nobody is asking about as I believe the switchover was pre 5.0.

---

BOINC WIKI

No, Dagorath, you possibly misunderstood, what they said.

Me and my 1 track mind. It's like a wheel in a wagon rut sometimes. Keck set me straight once but I slipped back. I'm OK now :)

And any idle core will be immediately supplied with work. (Except that you (well, mitrichr) have revealed a bug in the client.)

Peter

Yes, seems like a bug but there may be some other explanation. I'll see if I can reproduce it here.

@mitrichr: On which version of BOINC did you see this apparent bug?

The rules of reporting are not quite that simple.

While BOINC assumes that it may not have a connection for "Connect every X" it will use a connection that it has available as "NOW" might be the last time the computer is connected for a while.

BOINC reports work at the first of:

24 hours before due.
Connect every X before due.
Immediately if it is later than the above 2 entries.
24 hours after completion.
On a work request.
On a trickle up (CPDN and associated projects only so far, but I believe that QCN may use this feature).
On a trickle down request (no uses yet).
On a timed request (a new project wants a contact ever X period - not in general circulation yet).
On a manual connect.

---

BOINC WIKI

And any idle core will be immediately supplied with work. (Except that you (well, mitrichr) have revealed a bug in the client.)

Yes, seems like a bug but there may be some other explanation. I'll see if I can reproduce it here.

The rules of reporting are not quite that simple...

I assume they are much simpler regarding feeding idle cores with fresh work? ;-)
(OK, I've torn your words from the context, my apology.)

Peter