Event Log Analys

Message boards : Number crunching : Event Log Analys
Message board moderation

To post messages, you must log in.

AuthorMessage
Sirius B Project Donor
Volunteer tester
Avatar

Send message
Joined: 26 Dec 00
Posts: 24879
Credit: 3,081,182
RAC: 7
Ireland
Message 1962124 - Posted: 27 Oct 2018, 13:20:46 UTC

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
ID: 1962124 · Report as offensive
Profile Brent Norman Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester

Send message
Joined: 1 Dec 99
Posts: 2786
Credit: 685,657,289
RAC: 835
Canada
Message 1962132 - Posted: 27 Oct 2018, 14:18:06 UTC - in response to Message 1962124.  

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.
ID: 1962132 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14650
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1962138 - Posted: 27 Oct 2018, 15:06:17 UTC

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 request
27/10/2018 15:47:53 | SETI@home | Sending scheduler request: Requested by user.
27/10/2018 15:47:53 | SETI@home | Reporting 3 completed tasks
27/10/2018 15:47:53 | SETI@home | Requesting new tasks for NVIDIA GPU
27/10/2018 15:47:53 | SETI@home | [sched_op] CPU work request: 0.00 seconds; 0.00 devices
27/10/2018 15:47:53 | SETI@home | [sched_op] NVIDIA GPU work request: 4183.13 seconds; 0.00 devices
27/10/2018 15:47:53 | SETI@home | [sched_op] Intel GPU work request: 0.00 seconds; 0.00 devices
27/10/2018 15:47:56 | SETI@home | Scheduler request completed: got 4 new tasks
27/10/2018 15:47:56 | SETI@home | [sched_op] Server version 709
27/10/2018 15:47:56 | SETI@home | Project requested delay of 303 seconds
27/10/2018 15:47:56 | SETI@home | [sched_op] estimated total CPU task duration: 0 seconds
27/10/2018 15:47:56 | SETI@home | [sched_op] estimated total NVIDIA GPU task duration: 4278 seconds
27/10/2018 15:47:56 | SETI@home | [sched_op] estimated total Intel GPU task duration: 0 seconds
27/10/2018 15:47:56 | SETI@home | [sched_op] handle_scheduler_reply(): got ack for task blc23_2bit_guppi_58340_58652_HIP25191_0088.15654.409.19.28.218.vlar_0
27/10/2018 15:47:56 | SETI@home | [sched_op] handle_scheduler_reply(): got ack for task blc23_2bit_guppi_58340_57306_HIP25121_0084.19648.0.20.29.102.vlar_0
27/10/2018 15:47:56 | SETI@home | [sched_op] handle_scheduler_reply(): got ack for task blc23_2bit_guppi_58340_57645_HIP25878_0085.15643.409.20.29.246.vlar_1
27/10/2018 15:47:56 | SETI@home | [sched_op] Deferring communication for 00:05:03
27/10/2018 15:47:56 | SETI@home | [sched_op] Reason: requested by project
Yours 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 -------
27/10/2018 15:47:43 | | [work_fetch] target work buffer: 21600.00 + 4320.00 sec
27/10/2018 15:47:43 | | [work_fetch] --- project states ---
27/10/2018 15:47:43 | SETI@home | [work_fetch] REC 390160.784 prio -2.997 can request work
27/10/2018 15:47:43 | | [work_fetch] --- state for CPU ---
27/10/2018 15:47:43 | | [work_fetch] shortfall 3638.14 nidle 0.00 saturated 22281.86 busy 0.00
27/10/2018 15:47:43 | SETI@home | [work_fetch] share 0.000 blocked by project preferences
27/10/2018 15:47:43 | | [work_fetch] --- state for NVIDIA GPU ---
27/10/2018 15:47:43 | | [work_fetch] shortfall 4165.41 nidle 0.00 saturated 23566.45 busy 0.00
27/10/2018 15:47:43 | SETI@home | [work_fetch] share 1.000
27/10/2018 15:47:43 | | [work_fetch] --- state for Intel GPU ---
27/10/2018 15:47:43 | | [work_fetch] shortfall 2703.35 nidle 0.00 saturated 23216.65 busy 0.00
27/10/2018 15:47:43 | SETI@home | [work_fetch] share 0.000 blocked by project preferences
27/10/2018 15:47:43 | | [work_fetch] ------- end 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.
ID: 1962138 · Report as offensive
Sirius B Project Donor
Volunteer tester
Avatar

Send message
Joined: 26 Dec 00
Posts: 24879
Credit: 3,081,182
RAC: 7
Ireland
Message 1962142 - Posted: 27 Oct 2018, 16:01:47 UTC - in response to Message 1962138.  

Resources set to 100%. Do not do gpu crunching.
ID: 1962142 · Report as offensive
Richard Haselgrove Project Donor
Volunteer tester

Send message
Joined: 4 Jul 99
Posts: 14650
Credit: 200,643,578
RAC: 874
United Kingdom
Message 1962153 - Posted: 27 Oct 2018, 17:02:08 UTC - in response to Message 1962142.  

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.
ID: 1962153 · Report as offensive
Grant (SSSF)
Volunteer tester

Send message
Joined: 19 Aug 99
Posts: 13736
Credit: 208,696,464
RAC: 304
Australia
Message 1962172 - Posted: 27 Oct 2018, 21:35:10 UTC

Keep in mind the amount of Beta work on that system- almost 20 days worth.
Grant
Darwin NT
ID: 1962172 · Report as offensive

Message boards : Number crunching : Event Log Analys


 
©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.