| Author |
Message |
|
|
|
For a while now (and since the upgarde to the latest version, but not blaming that) completed WUs are not uploading automatically. I have to go Projects, select the project (Seti@Home) and click Update.
Any help or suggestions greatfully received.
Dave. |
|
|
Volunteer tester Send message
Joined: 9 Apr 02 Posts: 11987 Credit: 18,000,496 RAC: 56,291

|
|
How long have you let BOINC go before observing this? Meaning, do you wait 8 hours? 16 hours? 36 hours? |
|
|
|
|
|
I'll get completed WUs often - probably every 10 or 15 minutes another will complete |
|
|
|
|
|
That doesn't answer OzzFan's question! How long did you wait before clicking "update"?
And for your first post, are you speaking about uploading or reporting of WUs?
Gruß,
Gundolf
____________
Computer sind nicht alles im Leben. (Kleiner Scherz)
SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours |
|
|
ExVolunteer moderator Volunteer tester
 Send message
Joined: 12 Mar 12 Posts: 2883 Credit: 1,158,539 RAC: 839

|
|
Newer Boinc versions wait longer to report units and request work.
They report work and request work in bigger batches now. I'm not sure how long you are waiting for those units to upload, but be patient...
____________
-Dave #2
3.2.0-33 |
|
|
|
|
|
Okay, thanks. I'll wait overnight (it's now 19:30)- currently there are three WUs "ready to report". |
|
|
ExVolunteer moderator Volunteer tester
 Send message
Joined: 12 Mar 12 Posts: 2883 Credit: 1,158,539 RAC: 839

|
|
I don't even run a crunching rig that does alot of work, and I've had at least thirty waiting to report in the past. I know others probably even have longer lists. I'm sure your fine.
:-)
____________
-Dave #2
3.2.0-33 |
|
|
|
|
|
You shouldn't let that queue get too long (somebody mentioned a limit of 50 tasks to report) or you risk getting server timeouts on connection attempts.
Gruß,
Gundolf |
|
|
|
|
|
At 09:05 - 10 hours later I had 60 WUs "ready to report". So I set off the process manually. Thanks for all your help. |
|
|
|
|
|
You can always use cc_config to force BOINC to report results immediately if it bothers you, however, this is not advisable as it puts extra load on the already busy seti@home servers.
Peter
____________
|
|
|
Volunteer tester Send message
Joined: 9 Apr 02 Posts: 11987 Credit: 18,000,496 RAC: 56,291

|
At 09:05 - 10 hours later I had 60 WUs "ready to report". So I set off the process manually. Thanks for all your help.
10 hours isn't the default time. 24 hours is. Try to give it more time. |
|
|
|
|
|
Completed work is reported at the first of:
1) 24 hours before deadline.
2) Connect Every X before deadline.
3) 24 hours after task completion.
4) Immediately if the upload completes later than either 1, 2, or 3 upon completion of the task.
5) On a trickle up message.
6) On a trickle down request.
7) On a server scheduled connection. Used, but I am not certain by which project.
8) On a request for new work.
9) When the user pushes the update button.
10) On a request from an account manager.
11) Report immediately every task, if "No new Task" is set.
12) Report immediately if CPU or network time-of-day override starts in the next 30 minutes. (BOINC 7.0)
13) When minimum work buffer is reached. (BOINC 7.0)
____________
Jord
- BOINC FAQ Service
- BOINC User Wiki
Real is just a matter of perception. |
|
|
Volunteer tester Send message
Joined: 9 Apr 02 Posts: 11987 Credit: 18,000,496 RAC: 56,291

|
|
^^^ There you go. I would do well to copy and paste that, but I'm lazy. |
|
|
|
|
Completed work is reported at the first of:
1) 24 hours before deadline.
2) Connect Every X before deadline.
3) 24 hours after task completion.
4) Immediately if the upload completes later than either 1, 2, or 3 upon completion of the task.
5) On a trickle up message.
6) On a trickle down request.
7) On a server scheduled connection. Used, but I am not certain by which project.
8) On a request for new work.
9) When the user pushes the update button.
10) On a request from an account manager.
11) Report immediately every task, if "No new Task" is set.
12) Report immediately if CPU or network time-of-day override starts in the next 30 minutes. (BOINC 7.0)
13) When minimum work buffer is reached. (BOINC 7.0)
#13 is a repeat of #8. This is when the work fetch will occur.
____________
BOINC WIKI |
|
|
|
|
#13 is a repeat of #8. This is when the work fetch will occur.
Well, yes and no. The list of when reports happen is one for BOINC 5, 6 and 7. In BOINC 5 and 6 work requests happen at random, it seems. So better to differentiate between just a mere work request and when minimum work is reached.
____________
Jord
- BOINC FAQ Service
- BOINC User Wiki
Real is just a matter of perception. |
|
|
|
|
#13 is a repeat of #8. This is when the work fetch will occur.
Well, yes and no. The list of when reports happen is one for BOINC 5, 6 and 7. In BOINC 5 and 6 work requests happen at random, it seems. So better to differentiate between just a mere work request and when minimum work is reached.
No it wasn't. It was when the work on hand dropped below the sum of "connect every X" and "extra work". On 7 that changes to "connect every X".
____________
BOINC WIKI |
|
|
|
|
Completed work is reported at the first of:
1) 24 hours before deadline.
2) Connect Every X before deadline.
3) 24 hours after task completion.
4) Immediately if the upload completes later than either 1, 2, or 3 upon completion of the task.
5) On a trickle up message.
6) On a trickle down request.
7) On a server scheduled connection. Used, but I am not certain by which project.
8) On a request for new work.
9) When the user pushes the update button.
10) On a request from an account manager.
11) Report immediately every task, if "No new Task" is set.
12) Report immediately if CPU or network time-of-day override starts in the next 30 minutes. (BOINC 7.0)
13) When minimum work buffer is reached. (BOINC 7.0)
I think that an other point can be as soon as a "high task priority" is uploaded.
____________
|
|
|
|
|
Completed work is reported at the first of:
1) 24 hours before deadline.
2) Connect Every X before deadline.
3) 24 hours after task completion.
4) Immediately if the upload completes later than either 1, 2, or 3 upon completion of the task.
5) On a trickle up message.
6) On a trickle down request.
7) On a server scheduled connection. Used, but I am not certain by which project.
8) On a request for new work.
9) When the user pushes the update button.
10) On a request from an account manager.
11) Report immediately every task, if "No new Task" is set.
12) Report immediately if CPU or network time-of-day override starts in the next 30 minutes. (BOINC 7.0)
13) When minimum work buffer is reached. (BOINC 7.0)
I think that an other point can be as soon as a "high task priority" is uploaded.
Not always. A low resource share task is likely to run high priority early, complete early and then sit there for a while. A task running in high priority gets the same treatment as any other task once it is done.
____________
BOINC WIKI |
|
|