| Author |
Message |
|---|
|
|
|
At the moment my systems as reporting results every 5 minutes. Is it possible to defer reporting 'till there are either more than a specified number to report or a specified time has passed please? I am typically reporting as below.
I tried adding <report_results_immediately>0</report_results_immediately> but this did not help.
In a tryical day I see 97 MB uplaoded and 286 MB downloaded. The amount uploaded is more than I was expecting and am wondering if reporting results every 5 minutes could be the reason it's so large.
I am using BOINC x64 V7.0.25. As I recall 6.12.34 used to do the same.
29/04/2012 17:10:46 | SETI@home | [dcf] DCF: 6.892625->6.352469, raw_ratio 1.491066, adj_ratio 0.216328
29/04/2012 17:11:26 | SETI@home | [dcf] DCF: 6.352469->5.816693, raw_ratio 0.994711, adj_ratio 0.156586
29/04/2012 17:11:44 | SETI@home | Sending scheduler request: To report completed tasks.
29/04/2012 17:11:44 | SETI@home | Reporting 2 completed tasks, not requesting new tasks
29/04/2012 17:11:52 | SETI@home | Scheduler request completed
29/04/2012 17:12:30 | SETI@home | [dcf] DCF: 5.816693->5.336605, raw_ratio 1.015813, adj_ratio 0.174638
29/04/2012 17:15:51 | SETI@home | [dcf] DCF: 5.336605->4.953697, raw_ratio 1.507521, adj_ratio 0.282487
29/04/2012 17:16:58 | SETI@home | Sending scheduler request: To report completed tasks.
29/04/2012 17:16:58 | SETI@home | Reporting 2 completed tasks, not requesting new tasks
29/04/2012 17:17:07 | SETI@home | Scheduler request completed
29/04/2012 17:19:39 | SETI@home | [dcf] DCF: 4.953697->4.592975, raw_ratio 1.346478, adj_ratio 0.271813
29/04/2012 17:22:11 | SETI@home | Sending scheduler request: To report completed tasks.
29/04/2012 17:22:11 | SETI@home | Reporting 1 completed tasks, not requesting new tasks
29/04/2012 17:22:26 | SETI@home | Scheduler request completed
29/04/2012 17:24:48 | SETI@home | [dcf] DCF: 4.592975->4.269481, raw_ratio 1.358041, adj_ratio 0.295678
29/04/2012 17:27:31 | SETI@home | Sending scheduler request: To report completed tasks.
29/04/2012 17:27:31 | SETI@home | Reporting 1 completed tasks, not requesting new tasks
29/04/2012 17:27:40 | SETI@home | Scheduler request completed
29/04/2012 17:28:35 | SETI@home | [dcf] DCF: 4.269481->3.977769, raw_ratio 1.352355, adj_ratio 0.316749
29/04/2012 17:32:45 | SETI@home | Sending scheduler request: To report completed tasks.
29/04/2012 17:32:45 | SETI@home | Reporting 1 completed tasks, not requesting new tasks
29/04/2012 17:32:57 | SETI@home | Scheduler request completed
29/04/2012 17:33:59 | SETI@home | [dcf] DCF: 3.977769->3.677284, raw_ratio 0.972925, adj_ratio 0.244591
29/04/2012 17:35:08 | SETI@home | Aborting task 04my11aa.25440.4979.3.10.166_2: exceeded elapsed time limit 3942.51 (15770.02G/4.00G)
29/04/2012 17:35:26 | SETI@home | [dcf] DCF: 3.677284->3.465713, raw_ratio 1.561574, adj_ratio 0.424654
29/04/2012 17:35:33 | SETI@home | [dcf] DCF: 3.465713->3.220422, raw_ratio 1.012795, adj_ratio 0.292233
29/04/2012 17:38:03 | SETI@home | Sending scheduler request: To report completed tasks.
29/04/2012 17:38:03 | SETI@home | Reporting 4 completed tasks, not requesting new tasks
29/04/2012 17:39:05 | SETI@home | Scheduler request completed |
|
|
|
|
29/04/2012 17:38:03 | SETI@home | Reporting 4 completed tasks, not requesting new tasks
29/04/2012 17:39:05 | SETI@home | Scheduler request completed
Since BOINC makes Scheduler requests only to Report completed tasks (and not requesting new tasks)
BOINC thinks it will not have Internet connection in the next XX days and is in a hurry to report while it can.
This depends on "Maintain enough tasks to keep busy for at least 10 days"
(if the deadline is in the next 10 days BOINC will report immediately)
So change your cache from e.g. 10+10 to 8+12 or 5+15 days.
(the values >10 for the second setting are not possible with the GUI (BOINC Manager) but it's possible to edit directly:
<work_buf_additional_days>XX.000000</work_buf_additional_days>
in global_prefs_override.xml
)
Also the setting "Switch between tasks every XYZ minutes" may affect this if set to big values (e.g. 15000 minutes)
____________
 - ALF - "Find out what you don't do well ..... then don't do it!" :)
|
|
|
|
|
29/04/2012 17:38:03 | SETI@home | Reporting 4 completed tasks, not requesting new tasks
29/04/2012 17:39:05 | SETI@home | Scheduler request completed
Since BOINC makes Scheduler requests only to Report completed tasks (and not requesting new tasks)
BOINC thinks it will not have Internet connection in the next XX days and is in a hurry to report while it can.
This depends on "Maintain enough tasks to keep busy for at least 10 days"
(if the deadline is in the next 10 days BOINC will report immediately)
So change your cache from e.g. 10+10 to 8+12 or 5+15 days.
(the values >10 for the second setting are not possible with the GUI (BOINC Manager) but it's possible to edit directly:
<work_buf_additional_days>XX.000000</work_buf_additional_days>
in global_prefs_override.xml
)
Also the setting "Switch between tasks every XYZ minutes" may affect this if set to big values (e.g. 15000 minutes)
The task switch interval is part of the computation of the computation deadline, but not part of the computation of when to actually report.
____________
BOINC WIKI |
|
|
|
|
|
Thank you Bil, I have set <work_buf_additional_days>20.000000</work_buf_additional_days> which will help getting work when the DCF is stupid.
30/04/2012 00:45:28 | SETI@home | [dcf] DCF: 2.139742->8.482084, raw_ratio 8.482084, adj_ratio 3.964069
I have connect every 8 days set to force shorties to get run as they arrive so I have enought WUs cached to keep busy when the server is down. I will see what happens if I set zero tomorrow. |
|
|
|
|
I have connect every 8 days set to force shorties to get run as they arrive so I have enought WUs cached to keep busy when the server is down. I will see what happens if I set zero tomorrow.
With BOINC 7.0.25 "zero" for the "connect every/Maintain enough tasks to keep busy" is not good, it will not ask for work at all.
(with 8+20 it will wait for the cache to be < 8 days, then will ask for 20 days)
John McLeod VII say "The task switch interval is part of the computation of the computation deadline, but not part of the computation of when to actually report."
so you can use this setting "to force shorties to get run as they arrive" instead.
Try "Switch between tasks every 14400 minutes" (which should make the shorties run at "high priority")
____________
- ALF - "Find out what you don't do well ..... then don't do it!" :)
|
|
|
|
|
|
I will try <cpu_scheduling_period_minutes>14400.000000</cpu_scheduling_period_minutes> and see what happens.
I have now set <work_buf_min_days>0.000000</work_buf_min_days> but it's still reporting results every 5 minutes. |
|
|
|
|
|
Is it possible that you have tasks that are over or very near the deadline?
(and you don't forget to "Read local prefs file" after manual edit?)
And "reporting results every 5 minutes" is not coupled with asking for tasks?
____________
- ALF - "Find out what you don't do well ..... then don't do it!" :)
|
|
|
|
|
|
Looking at http://setiathome.berkeley.edu/results.php?hostid=6379672&offset=1573&show_names=0&state=1 4 Jun 2012 | 23:53:56 UTC is the soonest. The GPUs will totally empty the cache in four days and the CPUs in similar.
Remember for my systems the 400 + 50 limits are stupidly small. |
|
|
|
|
|
I have discovered this is a "feature" from changeset [23571]. The word bug comes to mind. |
|
|
|
|
|
You may propose changes/new value (-1) for <report_results_immediately>
(I don't know how, maybe direct email to David Anderson
http://setiathome.berkeley.edu/view_profile.php?userid=432107
He posted his email here:
http://setiathome.berkeley.edu/forum_thread.php?id=61471&nowrap=true#1037452
)
As you know now it is:
<report_results_immediately>0|1</report_results_immediately>
0 == Default value/behaviour (report results on several events)
1 == Force report_results_immediately
Propose:
-1 == Force Do_NOT_report_results_immediately (report results ONLY on events, e.g. "24 hours before deadline", "On a request for new work", ...)
Will this be accepted as needed/feasible I don't know.
____________
- ALF - "Find out what you don't do well ..... then don't do it!" :)
|
|
|
