18717 Is Super Slow & Low PPD

[promeneur]

18717 (36, 42, 306)
uses
1 GB ram, 12 GB swap

ETA 1.34 days
My computer has 1.80 days to complete this work unit.

[belloq]

I got another WU today which is causing the same issue: no work actually being performed. For hours and hours. It was no 18717 though. Log file looks exactly like the one I already posted. No response from the core for multiple hours after being "started."

Code: Select all

*********************** Log Started 2023-05-26T21:15:25Z ***********************
21:15:26:FS01:Initialized folding slot 01: gpu:1:0 GA107GLM [RTX A1000 Laptop GPU]
21:16:34:FS01:Unpaused
21:16:35:WU00:FS01:Connecting to assign1.foldingathome.org:80
21:16:35:WU00:FS01:Connecting to assign1.foldingathome.org:80
21:16:35:WU00:FS01:Assigned to work server 129.32.209.202
21:16:35:WU00:FS01:Requesting new work unit for slot 01: gpu:1:0 GA107GLM [RTX A1000 Laptop GPU] from 129.32.209.202
21:16:35:WU00:FS01:Connecting to 129.32.209.202:8080
21:16:36:WU00:FS01:Downloading 15.84MiB
21:16:39:WU00:FS01:Download complete
21:16:39:WU00:FS01:Received Unit: id:00 state:DOWNLOAD error:NO_ERROR project:18453 run:1 clone:17 gen:597 core:0x22 unit:0x00000011000002550000481500000001
21:16:39:WU00:FS01:Starting
21:16:39:WU00:FS01:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:\ProgramData\FAHClient\cores/cores.foldingathome.org/win/64bit/22-0.0.20/Core_22.fah/FahCore_22.exe -dir 00 -suffix 01 -version 706 -lifeline 34148 -checkpoint 15 -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu-vendor nvidia -gpu 0 -gpu-usage 100
21:16:39:WU00:FS01:Started FahCore on PID 13836
21:16:39:WU00:FS01:Core PID:33828
21:16:39:WU00:FS01:FahCore 0x22 started
21:16:40:WU00:FS01:0x22:*********************** Log Started 2023-05-26T21:16:39Z ***********************
21:16:40:WU00:FS01:0x22:*************************** Core22 Folding@home Core ***************************
21:16:40:WU00:FS01:0x22:       Core: Core22
21:16:40:WU00:FS01:0x22:       Type: 0x22
21:16:40:WU00:FS01:0x22:    Version: 0.0.20
21:16:40:WU00:FS01:0x22:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
21:16:40:WU00:FS01:0x22:  Copyright: 2020 foldingathome.org
21:16:40:WU00:FS01:0x22:   Homepage: https://foldingathome.org/
21:16:40:WU00:FS01:0x22:       Date: Jan 20 2022
21:16:40:WU00:FS01:0x22:       Time: 01:15:36
21:16:40:WU00:FS01:0x22:   Revision: 3f211b8a4346514edbff34e3cb1c0e0ec951373c
21:16:40:WU00:FS01:0x22:     Branch: HEAD
21:16:40:WU00:FS01:0x22:   Compiler: Visual C++
21:16:40:WU00:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
21:16:40:WU00:FS01:0x22:             -DOPENMM_VERSION="\"7.7.0\""
21:16:40:WU00:FS01:0x22:   Platform: win32 10
21:16:40:WU00:FS01:0x22:       Bits: 64
21:16:40:WU00:FS01:0x22:       Mode: Release
21:16:40:WU00:FS01:0x22:Maintainers: John Chodera <john.chodera@choderalab.org> and Peter Eastman
21:16:40:WU00:FS01:0x22:             <peastman@stanford.edu>
21:16:40:WU00:FS01:0x22:       Args: -dir 00 -suffix 01 -version 706 -lifeline 13836 -checkpoint 15
21:16:40:WU00:FS01:0x22:             -opencl-platform 0 -opencl-device 0 -cuda-device 0 -gpu-vendor
21:16:40:WU00:FS01:0x22:             nvidia -gpu 0 -gpu-usage 100
21:16:40:WU00:FS01:0x22:************************************ libFAH ************************************
21:16:40:WU00:FS01:0x22:       Date: Jan 20 2022
21:16:40:WU00:FS01:0x22:       Time: 01:14:17
21:16:40:WU00:FS01:0x22:   Revision: 9f4ad694e75c2350d4bb6b8b5b769ba27e483a2f
21:16:40:WU00:FS01:0x22:     Branch: HEAD
21:16:40:WU00:FS01:0x22:   Compiler: Visual C++
21:16:40:WU00:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
21:16:40:WU00:FS01:0x22:   Platform: win32 10
21:16:40:WU00:FS01:0x22:       Bits: 64
21:16:40:WU00:FS01:0x22:       Mode: Release
21:16:40:WU00:FS01:0x22:************************************ CBang *************************************
21:16:40:WU00:FS01:0x22:       Date: Jan 20 2022
21:16:40:WU00:FS01:0x22:       Time: 01:13:20
21:16:40:WU00:FS01:0x22:   Revision: ab023d155b446906d55b0f6c9a1eedeea04f7a1a
21:16:40:WU00:FS01:0x22:     Branch: HEAD
21:16:40:WU00:FS01:0x22:   Compiler: Visual C++
21:16:40:WU00:FS01:0x22:    Options: /TP /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
21:16:40:WU00:FS01:0x22:   Platform: win32 10
21:16:40:WU00:FS01:0x22:       Bits: 64
21:16:40:WU00:FS01:0x22:       Mode: Release
21:16:40:WU00:FS01:0x22:************************************ System ************************************
21:16:40:WU00:FS01:0x22:        CPU: 12th Gen Intel(R) Core(TM) i7-12800H
21:16:40:WU00:FS01:0x22:     CPU ID: GenuineIntel Family 6 Model 154 Stepping 3
21:16:40:WU00:FS01:0x22:       CPUs: 20
21:16:40:WU00:FS01:0x22:     Memory: 31.68GiB
21:16:40:WU00:FS01:0x22:Free Memory: 18.33GiB
21:16:40:WU00:FS01:0x22:    Threads: WINDOWS_THREADS
21:16:40:WU00:FS01:0x22: OS Version: 6.2
21:16:40:WU00:FS01:0x22:Has Battery: true
21:16:40:WU00:FS01:0x22: On Battery: false
21:16:40:WU00:FS01:0x22: UTC Offset: -7
21:16:40:WU00:FS01:0x22:        PID: 33828
21:16:40:WU00:FS01:0x22:        CWD: C:\ProgramData\FAHClient\work
21:16:40:WU00:FS01:0x22:************************************ OpenMM ************************************
21:16:40:WU00:FS01:0x22:    Version: 7.7.0
21:16:40:WU00:FS01:0x22:********************************************************************************

There should be more log entries right after this, but there isn't. Just nothing seems to be happening at all. I've not had this issue before.

[belloq]

I found the "fix" for the WUs which get stuck trying to start up. When a WU either restarts (after pause) or a new WU downloads and starts up, it will hang if I have a Startech USB-C multiport adapter connected to my system. As soon as I disconnect the adpater, the log file immediately resumes logging and the WU starts being processed. I can then plug it back in and use my system normally.

[toTOW]

I found the "fix" for the WUs which get stuck trying to start up. When a WU either restarts (after pause) or a new WU downloads and starts up, it will hang if I have a Startech USB-C multiport adapter connected to my system. As soon as I disconnect the adpater, the log file immediately resumes logging and the WU starts being processed. I can then plug it back in and use my system normally.

This is really strange ...

On another topic, for your information, project 18717 is now completed.