Questions and Answers :
Windows :
BOINC Not uploading/reporting
Message board moderation
Author | Message |
---|---|
JRH Send message Joined: 28 Apr 13 Posts: 2 Credit: 10,445 RAC: 0 |
Hi Guys, Sorry for the noise, but I'm a n00b to BOINC!. I've been using BOINC for SETI@home for the last couple of days, I'm over the usual problems such as setting CPU usage limits to avoid thermal overload etc, and have managed to upload 2x SETI tasks & 1x Enigma so far, confirmed in "My Account", and credit awarded etc. All of today's jobs so far are showing a status of "Ready To Report", and are not showing as validated etc on either account. I have BOINC set to "Network Activity Always Available" as I'm on a LAN connection. Am I doing something wrong? or is there a backlog? I did notice the project homepage was down for maintenance earlier this afternoon (UK Time). Thanks in advance, James (FNG) |
JRH Send message Joined: 28 Apr 13 Posts: 2 Credit: 10,445 RAC: 0 |
Ah... I had to manually update the relevant projects! Any ideas as to why? I thought it would report the moment a task is complete? I'm pretty sure it did with the first two? J |
rob smith Send message Joined: 7 Mar 03 Posts: 22204 Credit: 416,307,556 RAC: 380 |
The default setting for BOINC to connect to the project servers is once every 24 hours. If you set the "max additional work buffer" to a small fraction of a day BOINC will connect more often - more or less at the interval you set (or at least should, it doesn't always work as advertised) Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
BOINC will automatically report the to be reported tasks, but it does only do so at least 24 hours after the first task was ready to report. Why not do so immediately? Because it adds to the server overhead. Reporting 1 task takes as much overhead (database reading and writing, memory usage, CPU usage) as does reporting 10 or 20 tasks. So it's more efficient to report multiple tasks. So, then, 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) |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.