Updates

[B^S] madmac
[B^S] madmac
Joined: 19 Jul 05
Posts: 32
Credit: 759460
RAC: 0
Topic 190157

I am using Boinc 5.2.6 and my latest WU has just uploaded, I know I will have to wait until the update manager seeks new work. As this an old machine 856 MHz and I am running three different projects it can be at least four days before the machine seeks out new work. Is there anyway around this? I do not want to hit the update button because if I did what was the point in updating Boinc. Can anyone help me please?

Stick
Stick
Joined: 24 Feb 05
Posts: 790
Credit: 33130322
RAC: 1161

Updates

Quote:
I am using Boinc 5.2.6 and my latest WU has just uploaded, I know I will have to wait until the update manager seeks new work. As this an old machine 856 MHz and I am running three different projects it can be at least four days before the machine seeks out new work. Is there anyway around this? I do not want to hit the update button because if I did what was the point in updating Boinc. Can anyone help me please?

Madmac,

"Getting new work" contacts is only one of the ways that "result reporting" might occur. There are other possibilities as well. And, it shouldn't take any longer than 24 hours after the WU finishes. Take a look at the response I got from Walt Gribben (below) when I raised a similar question.

Stick

Quote:

Stick,

Sending the results is a two step process. First the result data is uploaded to the upload server, and while thats happening you'll see it in the transfer tab. Afterwords the result will be "waiting to report", which it'll do the next time BOINC contacts the scheduler. Reporting is where it sends the administrative details about the result - exit status, CPU time, error messages, things like that.

Some earlier versions of BOINC had a bug where it reported results right after uploading. That was fixed in 5.2. Now it'll contact the scheduler to report if it reaches the deadline or 24 hours after the workunit finishes. If BOINC contacts the scheduler for some other reason, it'll report the results then. Like if you manually "update" the project or BOINC requests more work.

Idea is to reduce the times BOINC contacts the scheduler to report work or request it, and this way it combines several requests into one contacts. With a short "connect every" interval it'll report the previous result when it requests a new workunit. With a longer interval it can report several workunits either after 24 hours have passed or when it requests more work.

And even though a result gets uploaded, the server won't show it as complete until its reported. And it'll use that as the "completion" time, even though the result had already been uploaded.

Walt


John McLeod VII
John McLeod VII
Moderator
Joined: 10 Nov 04
Posts: 547
Credit: 632255
RAC: 0

Work is reported t the

Work is reported t the earliest of:

1) A work request.
2) 24 hours before deadline.
3) Immediately if the result is finished later than 24 hours before deadline.'
4) X days after the result is complete from Connect every X days.
5) Manual update.
6) (under development) immediately if the internet connection is intermittent.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.