Bunkering basics, by our friend [H]Coleslaw
- 10esseetony
- TAAT Member
- Reactions:
- Posts: 473
- Joined: Sun Sep 15, 2019 7:02 pm
Re: Bunkering basics, by our friend [H]Coleslaw
It is important to know when the client reports results.
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
(source: BOINC FAQ)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)
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.
Last edited by StefanR5R on Wed May 13, 2020 10:02 am, edited 2 times in total.
Reason: more occasions added at which the client reports results
Reason: more occasions added at which the client reports results
- 10esseetony
- TAAT Member
- Reactions:
- Posts: 473
- Joined: Sun Sep 15, 2019 7:02 pm
Re: Bunkering basics, by our friend [H]Coleslaw
Stefan is referring to the method of suspending the project, and enabling networking, then turning networking off again.
Risky business, that method.
Risky business, that method.
Re: Bunkering basics, by our friend [H]Coleslaw
Perhaps the risks and uncertainties inherent in the method is why I'd not heard of it before, after several years of crunching?