Page 1 of 1
Bunkering basics, by our friend [H]Coleslaw
Posted: Tue May 12, 2020 8:15 pm
by 10esseetony
Re: Bunkering basics, by our friend [H]Coleslaw
Posted: Wed May 13, 2020 9:41 am
by StefanR5R
It is important to know when the client reports results.
In 2007 Jorden wrote:
BOINC reports completed work at the first of:
- The next work request from a project.
- 24 hours before the deadline.
- Immediately if the work is completed later than 24 hours before the deadline.
- Connect every X days after the work is completed.
- With the next trickle (CPDN only at this point).
- When the user clicks update.
- Connect every X days before the report is due. (new with 5.4 and above)
(source:
BOINC FAQ)
To prevent results from being reported too early, obviously each one of these possibilities must be eliminated.
Furthermore, the client will report results immediately after upload
- if the project was set to "No new tasks",
- if the cc_config item report_results_immediately was enabled by the user,
- if the app_config item report_results_immediately was enabled by the user,
- if report_results_immediately was enabled for the application by the project admin.
Re: Bunkering basics, by our friend [H]Coleslaw
Posted: Wed May 13, 2020 10:01 am
by 10esseetony
Stefan is referring to the method of suspending the project, and enabling networking, then turning networking off again.
Risky business, that method.
Re: Bunkering basics, by our friend [H]Coleslaw
Posted: Wed May 13, 2020 10:46 am
by crashtech
Perhaps the risks and uncertainties inherent in the method is why I'd not heard of it before, after several years of crunching?