Delayed reporting (BOINC issue?)

Message boards : Number crunching : Delayed reporting (BOINC issue?)

To post messages, you must log in.

AuthorMessage
Profile River~~
Avatar

Send message
Joined: 15 Dec 05
Posts: 761
Credit: 285,578
RAC: 0
Message 29736 - Posted: 21 Oct 2006, 8:06:21 UTC

I have just seen a return of a BOINC issue that I thought had been resolved in a much earlier release of the client.

This result was due around 1100 on 20th, UTC, but due to other work on my box did not complete till around 2300 on 20th, ie already 12hrs late.

Next morning, around 0800, it still had not reported, and the message tab shows no attempt to do so.

I thought that the client was supposed to report work immediately if it was close to or over the deadline.

No harm done really as on Rosetta we still get credit for late results, but on other projects it could make the difference between another result being sent out, or not; and it could make the difference between getting late credit or not.

OS = Linux, client = 5.4.9

Comments anyone?
River~~
ID: 29736 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
FluffyChicken
Avatar

Send message
Joined: 1 Nov 05
Posts: 1260
Credit: 369,635
RAC: 0
Message 29739 - Posted: 21 Oct 2006, 8:57:02 UTC

I don't remember talk about this getting altered. There was talk about this sort of thing during 5.6.x series but I still don't think anything got implemented. I think it was talked about during adding the ability to purge results from the queue, soemthing like that.


Team mauisun.org
ID: 29739 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
daniele

Send message
Joined: 12 Oct 06
Posts: 18
Credit: 20,328
RAC: 0
Message 29746 - Posted: 21 Oct 2006, 12:19:36 UTC
Last modified: 21 Oct 2006, 12:23:11 UTC

I had the same problem in the last days, client 5.4.9 on linux, with some WU (I can't say, at this moment, if the problem is only with rosetta).
In my case deadlines were far, but completed WUs were delayed in reporting for hours, and I had to do it manually.

I have to investigate, but it could be a simple "problem" in the client using the general settings. River's problem seems to be different.
ID: 29746 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile River~~
Avatar

Send message
Joined: 15 Dec 05
Posts: 761
Credit: 285,578
RAC: 0
Message 29752 - Posted: 21 Oct 2006, 13:16:31 UTC - in response to Message 29746.  
Last modified: 21 Oct 2006, 13:18:11 UTC

In my case deadlines were far, but completed WUs were delayed in reporting for hours, and I had to do it manually.

I have to investigate, but it could be a simple "problem" in the client using the general settings. River's problem seems to be different.


When the deadlines are far off (compared to the "connect every X days setting") the client is supposed to defer reporting. This is in the hope that two or more WU can be sent back together, saving database logins at the server end. Database connections are a bottleneck on several projects, the most extreme example being on Einstein but I do know it is a minor issue here.

But I understood that when the deadline is close or overdue the client is supposed to report more or less as soon as upload is complete. I remember this being discussed around Xmas 2005 (anyone know what BOINC version we were on then?) perhaps on these boards or perhaps on Einstein or LHC.

JM7 would know - are you here John?

R~~
ID: 29752 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
FluffyChicken
Avatar

Send message
Joined: 1 Nov 05
Posts: 1260
Credit: 369,635
RAC: 0
Message 29762 - Posted: 21 Oct 2006, 14:39:23 UTC - in response to Message 29752.  

... Xmas 2005 (anyone know what BOINC version we were on then?) ...


5.2.13/14


Team mauisun.org
ID: 29762 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Message boards : Number crunching : Delayed reporting (BOINC issue?)



©2025 University of Washington
https://www.bakerlab.org