Message boards :
Number crunching :
Event Log Analys
Message board moderation
Author | Message |
---|---|
Sirius B Send message Joined: 26 Dec 00 Posts: 24879 Credit: 3,081,182 RAC: 7 |
1962113 Done as Richard suggested. 27/10/2018 14:12:15 | SETI@home | [sched_op] Server version 709 27/10/2018 14:12:15 | SETI@home | Project requested delay of 303 seconds 27/10/2018 14:12:15 | SETI@home | [sched_op] estimated total CPU task duration: 39985 seconds 27/10/2018 14:12:15 | SETI@home | [sched_op] estimated total NVIDIA GPU task duration: 0 seconds 27/10/2018 14:12:15 | SETI@home | [sched_op] Deferring communication for 00:05:03 27/10/2018 14:12:15 | SETI@home | [sched_op] Reason: requested by project 27/10/2018 14:12:15 | | [work_fetch] Request work fetch: RPC complete 27/10/2018 14:12:17 | SETI@home | Started download of blc23_2bit_guppi_58340_60032_HIP25577_0092.17505.821.19.28.50.vlar 27/10/2018 14:12:20 | | [work_fetch] ------- start work fetch state ------- 27/10/2018 14:12:20 | | [work_fetch] target work buffer: 864000.00 + 17280.00 sec 27/10/2018 14:13:21 | SETI@home | [work_fetch] REC 264.682 prio -0.084 can't request work: scheduler RPC backoff (237.49 sec) 27/10/2018 14:13:21 | SETI@home | [work_fetch] share 0.000 blocked by project preferences |
Brent Norman Send message Joined: 1 Dec 99 Posts: 2786 Credit: 685,657,289 RAC: 835 |
27/10/2018 14:13:21 | SETI@home | [work_fetch] share 0.000 blocked by project preferences Do you have your S@H Share set to Zero??? That would cause 1 WU download at a time. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
You really need to consider the whole block of information from each of the two Event Log options. Here are a pair of mine: 27/10/2018 15:47:53 | SETI@home | [sched_op] Starting scheduler requestYours shows that you received CPU work, but nothing about whether NVidia work was requested, or why if not. And the work fetch just before that sched_op - I've thrown away the data on about a dozen other projects, most of which are inactive. 27/10/2018 15:47:43 | | [work_fetch] ------- start work fetch state -------Again, you can see I have a work fetch share of 1.000 for NVidia (only): the other two resources are blocked by preferences. I was low on work (shortfall 4165 seconds), but it wasn't quite ready to fetch by itself (I was within the 4320 seconds 'additional work' I'd allowed). You'd need to show the separate states and reasoning for CPU and NVidia, and tell us what your intended balance between projects is. |
Sirius B Send message Joined: 26 Dec 00 Posts: 24879 Credit: 3,081,182 RAC: 7 |
Resources set to 100%. Do not do gpu crunching. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14650 Credit: 200,643,578 RAC: 874 |
Resources set to 100%. Do not do gpu crunching.OK, we need to see target work buffer (second line of work fetch) and saturated for CPU. |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13736 Credit: 208,696,464 RAC: 304 |
Keep in mind the amount of Beta work on that system- almost 20 days worth. Grant Darwin NT |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.