Posts by True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
log in
1) Message boards : Number crunching : Please give more max total WU time, or avoid project auto-delays over 60-90 min. (Message 62967)
Posted 6 Jan 2015 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
Thanks for your response.

STOP running the n-body units and
I have not run them on this host in many, many months. So, that is not the issue.

As to this host, I believe I gave the relevant info in post 62963:
about this host: 1/4/2015 5:57:31 PM||Processor: 8 GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz [Intel64 Family 6 Model 58 Stepping 9] [fpu tsc pae nx sse sse2 sse3 mmx]
1/4/2015 5:57:31 PM||Memory: 7.96 GB physical, 13.81 GB virtual
1/4/2015 5:57:31 PM||Disk: 232.40 GB total, 170.18 GB free
1/5/2015 7:22:32 PM|| 3393 floating point MIPS (Whetstone) per CPU
1/5/2015 7:22:32 PM|| 4599 integer MIPS (Dhrystone) per CPU


And, again, please note that the issue is not with this, or any, host - but with the MW scheduler-server programming:
    It's MW which sets the 3 WU per CPU limit (I adjust my "Preferences for this project" MilkyWay@Home preferences to receive and 'buffer' more work, but MW over-rides this.)
    It's the MW scheduler which issues 3 1/2 to 4 hour deferrals, when the total work sent is less

2) Message boards : Number crunching : Please give more max total WU time, or avoid project auto-delays over 60-90 min. (Message 62964)
Posted 6 Jan 2015 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
PS while most WU's run about 1hr 15min (luckily these today all were), but some are only ~15 minutes long... and yet still count towards a total max # WU's per CPU of only 3.
3) Message boards : Number crunching : Please give more max total WU time, or avoid project auto-delays over 60-90 min. (Message 62963)
Posted 6 Jan 2015 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
It happened again, within TWO hours: this time down to just 30min total CPU time for all processors combined - half of them already idle.
1/5/2015 4:42:24 PM|Milkyway@Home|Scheduler RPC succeeded [server version 705] 1/5/2015 4:42:24 PM|Milkyway@Home|Message from server: No tasks sent 1/5/2015 4:42:24 PM|Milkyway@Home|Message from server: No tasks are available for MilkyWay@Home 1/5/2015 4:42:24 PM|Milkyway@Home|Message from server: No tasks are available for Milkyway@Home Separation 1/5/2015 4:42:24 PM|Milkyway@Home|Message from server: No tasks are available for Milkyway@Home Separation (Modified Fit) 1/5/2015 4:42:24 PM|Milkyway@Home|Deferring communication for 1 min 1 sec 1/5/2015 4:42:24 PM|Milkyway@Home|Reason: requested by project 1/5/2015 4:42:24 PM|Milkyway@Home|Deferring communication for 3 hr 44 min 47 sec 1/5/2015 4:42:24 PM|Milkyway@Home|Reason: no work from project 1/5/2015 4:53:24 PM|Milkyway@Home|Computation for task de_80_DR8_Rev_8_5_00004_1413455402_37423627_0 finished 1/5/2015 4:53:24 PM|Milkyway@Home|Starting de_80_DR8_Rev_8_5_00004_1413455402_37413116_1 1/5/2015 4:53:24 PM|Milkyway@Home|Starting task de_80_DR8_Rev_8_5_00004_1413455402_37413116_1 using milkyway version 100 1/5/2015 5:04:21 PM|Milkyway@Home|Computation for task de_80_DR8_Rev_8_5_00004_1413455402_37423628_0 finished 1/5/2015 5:04:21 PM|Milkyway@Home|Starting de_80_DR8_Rev_8_5_00004_1413455402_37423625_0 1/5/2015 5:04:21 PM|Milkyway@Home|Starting task de_80_DR8_Rev_8_5_00004_1413455402_37423625_0 using milkyway version 100 1/5/2015 5:07:34 PM|Milkyway@Home|Computation for task de_80_DR8_Rev_8_5_00004_1413455402_37423629_0 finished 1/5/2015 5:07:34 PM|Milkyway@Home|Starting de_80_DR8_Rev_8_5_00004_1413455402_37424263_0 1/5/2015 5:07:34 PM|Milkyway@Home|Starting task de_80_DR8_Rev_8_5_00004_1413455402_37424263_0 using milkyway version 100 1/5/2015 5:14:49 PM|Milkyway@Home|Computation for task de_80_DR8_Rev_8_5_00004_1413455402_37423630_0 finished 1/5/2015 5:14:49 PM|Milkyway@Home|Starting de_80_DR8_Rev_8_5_00004_1413455402_37424264_0 1/5/2015 5:14:49 PM|Milkyway@Home|Starting task de_80_DR8_Rev_8_5_00004_1413455402_37424264_0 using milkyway version 100 1/5/2015 5:14:57 PM|Milkyway@Home|Computation for task de_80_DR8_Rev_8_5_00004_1413455402_37423632_0 finished 1/5/2015 5:14:57 PM|Milkyway@Home|Starting de_80_DR8_Rev_8_5_00004_1413455402_37424252_0 1/5/2015 5:14:57 PM|Milkyway@Home|Starting task de_80_DR8_Rev_8_5_00004_1413455402_37424252_0 using milkyway version 100 1/5/2015 5:27:47 PM|Milkyway@Home|Computation for task de_80_DR8_Rev_8_5_00004_1413455402_37402712_2 finished 1/5/2015 5:27:47 PM|Milkyway@Home|Starting de_80_DR8_Rev_8_5_00004_1413455402_37424253_0 1/5/2015 5:27:47 PM|Milkyway@Home|Starting task de_80_DR8_Rev_8_5_00004_1413455402_37424253_0 using milkyway version 100 1/5/2015 5:33:09 PM|Milkyway@Home|Computation for task de_80_DR8_Rev_8_5_00004_1413455402_37252743_2 finished 1/5/2015 5:33:09 PM|Milkyway@Home|Starting de_80_DR8_Rev_8_5_00004_1413455402_37424254_0 1/5/2015 5:33:09 PM|Milkyway@Home|Starting task de_80_DR8_Rev_8_5_00004_1413455402_37424254_0 using milkyway version 100 1/5/2015 6:01:01 PM|Milkyway@Home|Computation for task de_80_DR8_Rev_8_5_00004_1413455402_37410808_2 finished 1/5/2015 6:01:01 PM|Milkyway@Home|Starting de_80_DR8_Rev_8_5_00004_1413455402_37425398_0 1/5/2015 6:01:01 PM|Milkyway@Home|Starting task de_80_DR8_Rev_8_5_00004_1413455402_37425398_0 using milkyway version 100 1/5/2015 6:19:37 PM|Milkyway@Home|Computation for task de_80_DR8_Rev_8_5_00004_1413455402_37413116_1 finished 1/5/2015 6:30:21 PM|Milkyway@Home|Computation for task de_80_DR8_Rev_8_5_00004_1413455402_37424263_0 finished 1/5/2015 6:32:58 PM|Milkyway@Home|Computation for task de_80_DR8_Rev_8_5_00004_1413455402_37423625_0 finished 1/5/2015 6:35:18 PM|Milkyway@Home|Computation for task de_80_DR8_Rev_8_5_00004_1413455402_37424264_0 finished 1/5/2015 6:36:04 PM|Milkyway@Home|Sending scheduler request: Requested by user 1/5/2015 6:36:04 PM|Milkyway@Home|Requesting 650879 seconds of new work, and reporting 12 completed tasks 1/5/2015 6:36:09 PM|Milkyway@Home|Scheduler request failed: HTTP file not found 1/5/2015 6:36:09 PM|Milkyway@Home|Sending scheduler request: Requested by user 1/5/2015 6:36:09 PM|Milkyway@Home|Requesting 650879 seconds of new work, and reporting 12 completed tasks 1/5/2015 6:36:14 PM|Milkyway@Home|Scheduler RPC succeeded [server version 705] 1/5/2015 6:36:14 PM|Milkyway@Home|Deferring communication for 1 min 1 sec 1/5/2015 6:36:14 PM|Milkyway@Home|Reason: requested by project 1/5/2015 6:36:16 PM|Milkyway@Home|Starting de_80_DR8_Rev_8_5_00004_1413455402_37522955_0 1/5/2015 6:36:16 PM|Milkyway@Home|Starting task de_80_DR8_Rev_8_5_00004_1413455402_37522955_0 using milkyway version 100 1/5/2015 6:36:16 PM|Milkyway@Home|Starting de_80_DR8_Rev_8_5_00004_1413455402_37522956_0 1/5/2015 6:36:16 PM|Milkyway@Home|Starting task de_80_DR8_Rev_8_5_00004_1413455402_37522956_0 using milkyway version 100 1/5/2015 6:36:16 PM|Milkyway@Home|Starting de_80_DR8_Rev_8_5_00004_1413455402_37522944_0 1/5/2015 6:36:16 PM|Milkyway@Home|Starting task de_80_DR8_Rev_8_5_00004_1413455402_37522944_0 using milkyway version 100 1/5/2015 6:36:16 PM|Milkyway@Home|Starting de_80_DR8_Rev_8_5_00004_1413455402_37522947_0 1/5/2015 6:36:16 PM|Milkyway@Home|Starting task de_80_DR8_Rev_8_5_00004_1413455402_37522947_0 using milkyway version 100

Can the scheduler be programmed to avoid such lengthy deferrals?
1/5/2015 4:42:24 PM|Milkyway@Home|Deferring communication for 3 hr 44 min 47 sec

about this host:
1/4/2015 5:57:31 PM||Processor: 8 GenuineIntel Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz [Intel64 Family 6 Model 58 Stepping 9] [fpu tsc pae nx sse sse2 sse3 mmx] 1/4/2015 5:57:31 PM||Memory: 7.96 GB physical, 13.81 GB virtual 1/4/2015 5:57:31 PM||Disk: 232.40 GB total, 170.18 GB free 1/5/2015 7:22:32 PM|| 3393 floating point MIPS (Whetstone) per CPU 1/5/2015 7:22:32 PM|| 4599 integer MIPS (Dhrystone) per CPU
4) Message boards : Number crunching : Please give more max total WU time, or avoid project auto-delays over 60-90 min. (Message 62962)
Posted 5 Jan 2015 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
I like Milkyway a lot: My Dad worked for NASA, as did I when an undergrad student. I'd be happy to devote 99% of my grid computing time to MW, but I can't afford not to run other projects as well, for this reason:

The MW project imposes a max of 3 tasks per CPU. This would be fine, I guess, except for two issues:
First, If a user has to limit internet access time to less than 24/7, even for just a few hours at a time, then cycles go unused.
Second, the current MW project scheduler uses a policy which generates delays automatically, and these delays can (and do) exceed the amount of work to be done that's left on a host:

1/5/2015 2:33:23 PM|Milkyway@Home|Computation for task de_80_DR8_Rev_8_5_00004_1413455402_37279480_0 finished 1/5/2015 2:33:23 PM|Milkyway@Home|Starting de_80_DR8_Rev_8_5_00004_1413455402_37329137_0 1/5/2015 2:33:23 PM|Milkyway@Home|Starting task de_80_DR8_Rev_8_5_00004_1413455402_37329137_0 using milkyway version 100 1/5/2015 2:42:03 PM|Milkyway@Home|Sending scheduler request: To fetch work 1/5/2015 2:42:03 PM|Milkyway@Home|Requesting 625619 seconds of new work, and reporting 11 completed tasks 1/5/2015 2:42:08 PM|Milkyway@Home|Scheduler request failed: HTTP file not found 1/5/2015 2:42:08 PM|Milkyway@Home|Sending scheduler request: To fetch work 1/5/2015 2:42:08 PM|Milkyway@Home|Requesting 625619 seconds of new work, and reporting 11 completed tasks 1/5/2015 2:42:14 PM|Milkyway@Home|Scheduler RPC succeeded [server version 705] 1/5/2015 2:42:14 PM|Milkyway@Home|Message from server: No tasks sent 1/5/2015 2:42:14 PM|Milkyway@Home|Message from server: No tasks are available for MilkyWay@Home 1/5/2015 2:42:14 PM|Milkyway@Home|Message from server: No tasks are available for Milkyway@Home Separation 1/5/2015 2:42:14 PM|Milkyway@Home|Message from server: No tasks are available for Milkyway@Home Separation (Modified Fit) 1/5/2015 2:42:14 PM|Milkyway@Home|Deferring communication for 1 min 1 sec 1/5/2015 2:42:14 PM|Milkyway@Home|Reason: requested by project 1/5/2015 2:42:14 PM|Milkyway@Home|Deferring communication for 3 hr 21 min 47 sec 1/5/2015 2:42:14 PM|Milkyway@Home|Reason: no work from project 1/5/2015 3:05:27 PM|Milkyway@Home|Sending scheduler request: Requested by user 1/5/2015 3:05:27 PM|Milkyway@Home|Requesting 637931 seconds of new work 1/5/2015 3:05:32 PM|Milkyway@Home|Scheduler request failed: HTTP file not found 1/5/2015 3:05:32 PM|Milkyway@Home|Sending scheduler request: Requested by user 1/5/2015 3:05:32 PM|Milkyway@Home|Requesting 637931 seconds of new work 1/5/2015 3:05:37 PM|Milkyway@Home|Scheduler RPC succeeded [server version 705] 1/5/2015 3:05:37 PM|Milkyway@Home|Deferring communication for 1 min 1 sec 1/5/2015 3:05:37 PM|Milkyway@Home|Reason: requested by project 1/5/2015 3:06:40 PM|Milkyway@Home|Sending scheduler request: To fetch work 1/5/2015 3:06:40 PM|Milkyway@Home|Requesting 575256 seconds of new work 1/5/2015 3:06:45 PM|Milkyway@Home|Scheduler request failed: HTTP file not found 1/5/2015 3:06:45 PM|Milkyway@Home|Sending scheduler request: To fetch work 1/5/2015 3:06:45 PM|Milkyway@Home|Requesting 575256 seconds of new work 1/5/2015 3:06:50 PM|Milkyway@Home|Scheduler RPC succeeded [server version 705] 1/5/2015 3:06:50 PM|Milkyway@Home|Deferring communication for 1 min 1 sec 1/5/2015 3:06:50 PM|Milkyway@Home|Reason: requested by project 1/5/2015 3:07:56 PM|Milkyway@Home|Sending scheduler request: To fetch work 1/5/2015 3:07:56 PM|Milkyway@Home|Requesting 547102 seconds of new work 1/5/2015 3:08:01 PM|Milkyway@Home|Scheduler request failed: HTTP file not found 1/5/2015 3:08:01 PM|Milkyway@Home|Sending scheduler request: To fetch work 1/5/2015 3:08:01 PM|Milkyway@Home|Requesting 547102 seconds of new work 1/5/2015 3:08:06 PM|Milkyway@Home|Scheduler RPC succeeded [server version 705] 1/5/2015 3:08:06 PM|Milkyway@Home|Message from server: No tasks sent 1/5/2015 3:08:06 PM|Milkyway@Home|Message from server: No tasks are available for MilkyWay@Home 1/5/2015 3:08:06 PM|Milkyway@Home|Message from server: No tasks are available for Milkyway@Home Separation 1/5/2015 3:08:06 PM|Milkyway@Home|Message from server: No tasks are available for Milkyway@Home Separation (Modified Fit) 1/5/2015 3:08:06 PM|Milkyway@Home|Message from server: This computer has reached a limit on tasks in progress

Note the nearly 3 1/2 hour deferral
l2:42:14 PM|Milkyway@Home|Deferring communication for 3 hr 21 min 47 sec
because, at that instant there was
Milkyway@Home|Reason: no work from project
Yet, within 25 min (by 3:06:50 PM) there WAS work available:
3:08:06 PM|Milkyway@Home|Message from server: This computer has reached a limit on tasks in progress
, but this host had gotten down to nearly zero WU time left to process.
In this instance - the event occurring during the day - I could manually intervene. But had I not been monitoring, there would have been a couple hours' dead time.

Thanks.
LLP, PhD PE
5) Message boards : Number crunching : adequately supply or WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings (Message 61616)
Posted 25 Apr 2014 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
With only at most +/- 3 hr of work-in-progress allowed, why dose WM do this? And, this is the routine of MW:
4/25/2014 5:00:00 AM|Milkyway@Home|Requesting 118489 seconds of new work, and reporting 6 completed tasks 4/25/2014 5:00:05 AM|Milkyway@Home|Scheduler RPC succeeded [server version 701] 4/25/2014 5:00:05 AM|Milkyway@Home|Deferring communication for 1 min 1 sec 4/25/2014 5:00:05 AM|Milkyway@Home|Reason: requested by project 4/25/2014 5:00:07 AM|Milkyway@Home|Starting de_separation_86_DR8_Rev_7_4_002_1398336302_358186_1 4/25/2014 5:00:07 AM|Milkyway@Home|Starting task de_separation_86_DR8_Rev_7_4_002_1398336302_358186_1 using milkyway version 100 4/25/2014 5:01:06 AM|Milkyway@Home|Sending scheduler request: To fetch work 4/25/2014 5:01:06 AM|Milkyway@Home|Requesting 89686 seconds of new work 4/25/2014 5:01:37 AM|Milkyway@Home|Scheduler request failed: HTTP internal server error 4/25/2014 5:01:37 AM|Milkyway@Home|Sending scheduler request: To fetch work 4/25/2014 5:01:37 AM|Milkyway@Home|Requesting 89686 seconds of new work 4/25/2014 5:01:42 AM|Milkyway@Home|Scheduler request failed: HTTP file not found 4/25/2014 5:01:42 AM|Milkyway@Home|Deferring communication for 1 min 0 sec 4/25/2014 5:01:42 AM|Milkyway@Home|Reason: scheduler request failed 4/25/2014 5:02:43 AM|Milkyway@Home|Sending scheduler request: To fetch work 4/25/2014 5:02:43 AM|Milkyway@Home|Requesting 89611 seconds of new work 4/25/2014 5:02:48 AM|Milkyway@Home|Scheduler RPC succeeded [server version 701] 4/25/2014 5:02:48 AM|Milkyway@Home|Message from server: No tasks sent 4/25/2014 5:02:48 AM|Milkyway@Home|Message from server: This computer has reached a limit on tasks in progress 4/25/2014 5:02:48 AM|Milkyway@Home|Deferring communication for 1 min 1 sec 4/25/2014 5:02:48 AM|Milkyway@Home|Reason: requested by project 4/25/2014 5:03:54 AM|Milkyway@Home|Sending scheduler request: To fetch work 4/25/2014 5:03:54 AM|Milkyway@Home|Requesting 89559 seconds of new work 4/25/2014 5:03:59 AM|Milkyway@Home|Scheduler RPC succeeded [server version 701] 4/25/2014 5:03:59 AM|Milkyway@Home|Message from server: No tasks sent 4/25/2014 5:03:59 AM|Milkyway@Home|Message from server: This computer has reached a limit on tasks in progress 4/25/2014 5:03:59 AM|Milkyway@Home|Deferring communication for 1 min 1 sec 4/25/2014 5:03:59 AM|Milkyway@Home|Reason: requested by project 4/25/2014 5:05:06 AM|Milkyway@Home|Sending scheduler request: To fetch work 4/25/2014 5:05:06 AM|Milkyway@Home|Requesting 89499 seconds of new work 4/25/2014 5:05:11 AM|Milkyway@Home|Scheduler RPC succeeded [server version 701] 4/25/2014 5:05:11 AM|Milkyway@Home|Message from server: No tasks sent 4/25/2014 5:05:11 AM|Milkyway@Home|Message from server: This computer has reached a limit on tasks in progress 4/25/2014 5:05:11 AM|Milkyway@Home|Deferring communication for 1 min 1 sec 4/25/2014 5:05:11 AM|Milkyway@Home|Reason: requested by project 4/25/2014 5:06:17 AM|Milkyway@Home|Sending scheduler request: To fetch work 4/25/2014 5:06:17 AM|Milkyway@Home|Requesting 89443 seconds of new work 4/25/2014 5:06:22 AM|Milkyway@Home|Scheduler RPC succeeded [server version 701] 4/25/2014 5:06:22 AM|Milkyway@Home|Message from server: No tasks sent 4/25/2014 5:06:22 AM|Milkyway@Home|Message from server: This computer has reached a limit on tasks in progress 4/25/2014 5:06:22 AM|Milkyway@Home|Deferring communication for 1 min 1 sec 4/25/2014 5:06:22 AM|Milkyway@Home|Reason: requested by project 4/25/2014 5:06:22 AM|Milkyway@Home|Deferring communication for 2 min 13 sec 4/25/2014 5:06:22 AM|Milkyway@Home|Reason: no work from project 4/25/2014 5:08:39 AM|Milkyway@Home|Sending scheduler request: To fetch work 4/25/2014 5:08:39 AM|Milkyway@Home|Requesting 90117 seconds of new work 4/25/2014 5:08:44 AM|Milkyway@Home|Scheduler RPC succeeded [server version 701] 4/25/2014 5:08:44 AM|Milkyway@Home|Message from server: No tasks sent 4/25/2014 5:08:44 AM|Milkyway@Home|Message from server: This computer has reached a limit on tasks in progress 4/25/2014 5:08:44 AM|Milkyway@Home|Deferring communication for 1 min 1 sec 4/25/2014 5:08:44 AM|Milkyway@Home|Reason: requested by project 4/25/2014 5:08:44 AM|Milkyway@Home|Deferring communication for 1 min 30 sec 4/25/2014 5:08:44 AM|Milkyway@Home|Reason: no work from project 4/25/2014 5:10:16 AM|Milkyway@Home|Sending scheduler request: To fetch work 4/25/2014 5:10:16 AM|Milkyway@Home|Requesting 90041 seconds of new work 4/25/2014 5:10:21 AM|Milkyway@Home|Scheduler RPC succeeded [server version 701] 4/25/2014 5:10:21 AM|Milkyway@Home|Message from server: No tasks sent 4/25/2014 5:10:21 AM|Milkyway@Home|Message from server: This computer has reached a limit on tasks in progress 4/25/2014 5:10:21 AM|Milkyway@Home|Deferring communication for 1 min 1 sec 4/25/2014 5:10:21 AM|Milkyway@Home|Reason: requested by project 4/25/2014 5:10:21 AM|Milkyway@Home|Deferring communication for 17 min 51 sec 4/25/2014 5:10:21 AM|Milkyway@Home|Reason: no work from project 4/25/2014 5:28:17 AM|Milkyway@Home|Sending scheduler request: To fetch work 4/25/2014 5:28:17 AM|Milkyway@Home|Requesting 91552 seconds of new work 4/25/2014 5:28:22 AM|Milkyway@Home|Scheduler RPC succeeded [server version 701] 4/25/2014 5:28:22 AM|Milkyway@Home|Message from server: No tasks sent 4/25/2014 5:28:22 AM|Milkyway@Home|Message from server: This computer has reached a limit on tasks in progress 4/25/2014 5:28:22 AM|Milkyway@Home|Deferring communication for 1 min 1 sec 4/25/2014 5:28:22 AM|Milkyway@Home|Reason: requested by project 4/25/2014 5:28:22 AM|Milkyway@Home|Deferring communication for 9 min 58 sec 4/25/2014 5:28:22 AM|Milkyway@Home|Reason: no work from project 4/25/2014 5:38:21 AM|Milkyway@Home|Sending scheduler request: To fetch work 4/25/2014 5:38:21 AM|Milkyway@Home|Requesting 92636 seconds of new work 4/25/2014 5:38:26 AM|Milkyway@Home|Scheduler RPC succeeded [server version 701] 4/25/2014 5:38:26 AM|Milkyway@Home|Message from server: No tasks sent 4/25/2014 5:38:26 AM|Milkyway@Home|Message from server: This computer has reached a limit on tasks in progress 4/25/2014 5:38:26 AM|Milkyway@Home|Deferring communication for 1 min 1 sec 4/25/2014 5:38:26 AM|Milkyway@Home|Reason: requested by project 4/25/2014 5:38:26 AM|Milkyway@Home|Deferring communication for 2 hr 5 min 46 sec

2 hr 5 min ???

Thank you for addressing this.
6) Message boards : Number crunching : adequately supply or WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings (Message 61613)
Posted 24 Apr 2014 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
Thanks for you reply, Link, however:

so simply let it run without clicking on any buttons

It is not I who is doing any clicking, WM on it's own issues repeated requests on its own

if you look at one of my earlier posts: (Message 61495 )
Why is that MW will repeatedly request more WU minute by minute when the limit had just recently been filled,
(emphais added here).

7) Message boards : Number crunching : adequately supply or WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings (Message 61607)
Posted 24 Apr 2014 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
PS i have been doing almost all my posting here at MW.

Is it just MW forum that is without any built in spell-checker?

Thx.
8) Message boards : Number crunching : adequately supply or WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings (Message 61606)
Posted 24 Apr 2014 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
Actually, I am getting more and more convince that this problem is not nearly so much a matter of the BOINC manager, as it having to do with some MW parameters:

4/24/2014 9:49:55 AM|Milkyway@Home|Sending scheduler request: To fetch work 4/24/2014 9:49:55 AM|Milkyway@Home|Requesting 136288 seconds of new work 4/24/2014 9:50:00 AM|Milkyway@Home|Scheduler RPC succeeded [server version 701] 4/24/2014 9:50:00 AM|Milkyway@Home|Message from server: No tasks sent 4/24/2014 9:50:00 AM|Milkyway@Home|Message from server: This computer has reached a limit on tasks in progress 4/24/2014 9:50:00 AM|Milkyway@Home|Deferring communication for 1 min 1 sec 4/24/2014 9:50:00 AM|Milkyway@Home|Reason: requested by project 4/24/2014 9:50:00 AM|Milkyway@Home|Deferring communication for 2 hr 5 min 43 sec

with WUs running ~an hour, there is somewhere between 2 and at most 3 hours of processing left.
So, why would WM defer communication for over 2 hours???
9) Message boards : Number crunching : adequately supply or WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings (Message 61597)
Posted 23 Apr 2014 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
thanks.
will try to get with this.
things getting buys just now, both at work and at home.
ttfn (to quote Tigger)
10) Message boards : Number crunching : adequately supply or WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings (Message 61591)
Posted 22 Apr 2014 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
On two machines I am pretty much constrained to run BOINC 5.8.
Is it possible to set report_results_immediately in that version?
I searched in the directory files and found no relevant hit in any of the files.
11) Message boards : Number crunching : adequately supply or WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings (Message 61590)
Posted 22 Apr 2014 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
"sigh"
Well, you can't get more than what is allowed by the project.

I am still holding out the hope that it is possible to convince MW to allow more than just 3 WU per processor... and when the WUs only run for ~an hour, this means a meager three hour limit.
I am also asking MW is to adjust the algorithm to initiate a request for a new WU whenever one completes. Other projects do this.
I fail to see how this is a matter of 'filling a cache' because that would be a matter of the amount of work requested or 'in inventory', and as MW themselves admit this is set BY MW at 3 WU per processor.

some WU requests are tagged "requested by user" (although this does not necessarily mean an explicit "update" issued):
[from event log Messages]
SZTAKI Desktop Grid Sending scheduler request: Requested by user fightmalaria@home Sending scheduler request: Requested by user boincsimap Sending scheduler request: Requested by user EDGeS@Home Sending scheduler request: Requested by user eon2 Sending scheduler request: Requested by user

some requests are tagged "requested by project"
World Community Grid Sending scheduler request: Requested by project eon2 Sending scheduler request: Requested by project


other WU requests are generated:
malariacontrol.net Sending scheduler request: To fetch work eon2 Sending scheduler request: To fetch work


and others scheduler requets are inititated to report completed tasks:
malariacontrol.net Sending scheduler request: To report completed tasks EDGeS@Home Sending scheduler request: To report completed tasks boincsimap Sending scheduler request: To report completed tasks Einstein@Home Sending scheduler request: To report completed tasks eon2 Sending scheduler request: To report completed tasks World Community Grid Sending scheduler request: To report completed tasks


it seems obvious that the difference kinds of scheduler requests issued are project-dependent.
12) Message boards : Number crunching : adequately supply or WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings (Message 61576)
Posted 21 Apr 2014 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
by 'cache' do you mean the Preference settings:
Maintain enough tasks to keep busy ...
13) Message boards : Number crunching : adequately supply or WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings (Message 61575)
Posted 21 Apr 2014 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
Thanks for your response posts.
I am inclined to agree with [TA]Assimilator1.
I have pretty much set milkyway preferences the SAME as I have for all the other projects I run, and for the other projects, the finishing of a WU automatically sends a request for more WUs
I could see your point, Link, about the BOINC manager. However, again, why do other projects send a request on a WU completion and MW does not?
Another counterpoint to this being a BOINC manager issue: I set a request for additional work on "Computing preferences" (Maintain enough tasks to keep busy for at least ... ... and up to an additional
0.5 days )
This DOES get BOINC to request more work, but 1) not more frequently and 2) the size of the request is overridden by MW.
14) Message boards : Number crunching : adequately supply or WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings (Message 61499)
Posted 10 Apr 2014 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
they should get replaced


Yes, they should.

However, sometimes WM's WU fetch algorithm takes a loooong break, and then the replacements arrive after my machine's been idle for a while.


Does MW really need to limit WU's in progress to < 2 hr 45 min??
So, what's the big deal about allowing a 5 or 6 hour 'inventory' of WU's?? This should still give turnarounds on tasks with total adequacy for MW's 'real time' task generation.

I repeat, WM is my #1 BOINC project, hands down.
But, until this 'stinginess (?)' on WU's is resolved, I have switched to my #2 project.

Hope to 'be back soon'...
15) Message boards : Number crunching : adequately supply or WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings (Message 61495)
Posted 9 Apr 2014 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
Thanks for looking into increasing the number of WUs that can be 'in progress'
For the record:
apparently a few years ago the limit was 6 per CPU:

Posted: 23 Jun 2010, 19:41:24 UTC
It is 6 tasks per cpu core.
It has been explained numerous times. This projects needs the results to make more tasks. So having a system have 3 days of work for gpus would be many thousands per system and by the time the results are in they would be "out of date" for their calculations. It would produce bad results for the project.

I am not sure if this is literally correct, or if the limit even then was really 3 per CPUC core X2 with threading.

I certainly am not asking for "3 days of work"
However, only allowing 3 WU per cpu when the WUs are only ~55 min long is ONLY allowing about 2 HOURS, 45 MINUTES of work.

Additionally, Would MW please take a good look at the scheduling&WU-requesting algorithm -- please? Why is that MW will repeatedly request more WU minute by minute when the limit had just recently been filled, and then later NOT re-schedule another request for a couple of hours

Lászlo Pallos, PhD Prof. Engr.
16) Message boards : Number crunching : adequately supply or WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings (Message 61474)
Posted 6 Apr 2014 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA
I do not see a way to edit a theme name once posted.
The theme was meant to be:
adequate supply of WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings

Thank you
17) Message boards : Number crunching : adequately supply or WUs: PLEASE: increase max_wus_in_progress or enable the Computing preference settings (Message 61473)
Posted 6 Apr 2014 by Profile True:I think, therefor I THINK I am. My thinking neither is the source of my existence, nor does it prove my existence to anyone else. Life v. lies...Dont be a DNA-denier. Abortion kills a new, unique human being, a boy or girl oPA

I like Milkyway@home as a project. Among other things, my Dad was a career NASA engineer, and I myself also worked for NASA at Cape Canaveral for a couple of years.
Thus, I like to run Mikyway as my primary BOINC project.
However, I cannot take the time to ‘babysit’ it day and nite, and make sure that there enough tasks (WUs) to keep my 4 PCs and a laptop adequately supplied with WUs

PLEASE: increase max_wus_in_progress from the current setting of 3 or enable the Computing preference settings: “Maintain enough tasks to keep busy for at least ___ days” “… and up to an additional ___ days”

L Pallos, PhD
LPallos.ie87@GTalumni.Org




Main page · Your account · Message boards


Copyright © 2017 AstroInformatics Group