Message boards : Number crunching : Delayed reporting (BOINC issue?)
Author | Message |
---|---|
![]() ![]() Send message Joined: 15 Dec 05 Posts: 761 Credit: 285,578 RAC: 0 |
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~~ ![]() |
FluffyChicken![]() Send message Joined: 1 Nov 05 Posts: 1260 Credit: 369,635 RAC: 0 |
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 |
daniele Send message Joined: 12 Oct 06 Posts: 18 Credit: 20,328 RAC: 0 |
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. |
![]() ![]() Send message Joined: 15 Dec 05 Posts: 761 Credit: 285,578 RAC: 0 |
In my case deadlines were far, but completed WUs were delayed in reporting for hours, and I had to do it manually. 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~~ |
FluffyChicken![]() Send message Joined: 1 Nov 05 Posts: 1260 Credit: 369,635 RAC: 0 |
|
Message boards :
Number crunching :
Delayed reporting (BOINC issue?)
©2025 University of Washington
https://www.bakerlab.org