Frequency of Update of Results
log in |
Message boards : Science : Frequency of Update of Results
Previous · 1 · 2
Author | Message |
---|---|
I guess you already saw it in the meantime also... ;-) | |
ID: 702 · Rating: 0 · rate: / Reply Quote | |
I guess you already saw it in the meantime also... ;-) It was never a problem, when a WUProp@Home WU was reported immediately after upload, the problem occurs when other projects do that, because than WUProp@Home don't get the runtime of the task (if it's only checking the client_state.xml every 5 minutes). ____________ . | |
ID: 703 · Rating: 0 · rate: / Reply Quote | |
Ahh... - O.K. I released a new application for Windows, Linux and Mac Intel: I understand it like every 60 seconds data are collected with this new app. Currently I use a BOINC Manager mod, which report every 10 minutes the uploaded results of all projects. So this would mean the WUProp@Home work units/results of my machine are currently unusable/worthless? ____________ | |
ID: 704 · Rating: 0 · rate: / Reply Quote | |
Currently I use a BOINC Manager mod, which report every 10 minutes the uploaded results of all projects. That's still quite a lot of time for WUProp to get the runtime. Real issues I see for example in case of Milkyway WUs on GPU (actually also CPU, they have quite low limits for tasks in process, so BOINC is usually asking for a new WU as soon as one is finished), since they are reported as soon as they are finished, there's even nothing to upload first, the result is in the stderr output. So this would mean the WUProp@Home work units/results of my machine are currently unusable/worthless? No, all other data except for the runtime is still collected, as stated in message 451. ____________ . | |
ID: 705 · Rating: 0 · rate: / Reply Quote | |
Message boards :
Science :
Frequency of Update of Results