Ready to report task
26 Feb 2013 19:54:15 UTC
Topic 196826
(moderation:
Ok kinda a long story but will make it short as I can. You know we download task. The computer works on task and when the task is done it uploads the results. It keeps the task listed as ready to report. When you change to not take on new task it uploads the results and then reports. Why not have it set that way all the time. It does not have to download new task just because it is reporting. I know it may put a strain on the servers but not really sure though as it uploads the results anyways why not go ahead and do the report and clear it out of Boinc?
PC setup MSI-970A-G46 AMD FX-8350 8 core OC'd 4.45GHz 16GB ram PC3-10700 Geforce GTX 650Ti Windows 7 x64 Einstein@Home
Ready to report task
)
1
???
RE: 1
)
C:\ProgramData\BOINC ?? Is this where it needs to be. Windows 7 x64
don't seem to have it so is that all I need. I have never been big on changing program files but I can/will give it a shot.
Edit:
Ok I did it and seems to work...
Thanks microchip
PC setup MSI-970A-G46 AMD FX-8350 8 core OC'd 4.45GHz 16GB ram PC3-10700 Geforce GTX 650Ti Windows 7 x64 Einstein@Home
Because uploading is a simple
)
Because uploading is a simple file transfer from your computer to the hard drive on the server, not much strain on the server there.
When you report a task a connection to the database of the project is opened and a few queries are run to get among other things what user and what computer and what task is in question. Then a few new queries to update all the info that needs to be updated. If you report more than one task at a time some of these queries only have to be run once for the whole report instead of once per reported task. If you take into account all the computers connected to the project and if they where to report every task one by one the load on the server would probably be way more than can be handled and the project would come to a grinding halt.
Users are generally discouraged to use because of the above and that if the upload server is stressed enough the file transfer might not have registered completely when the database is updated and the validator tries to validate the task, this means you might get a validate error on the task.