Project: 18469 will not finish within expiration date

Moderators: Site Moderators, FAHC Science Team

Post Reply
Akwan
Posts: 2
Joined: Tue Feb 21, 2023 7:42 pm

Project: 18469 will not finish within expiration date

Post by Akwan »

Hello,
I caught a WU from 18469 that will not finish on my hardware before the expiration date. Estimated time to finish is roughly 20 days, expiration date is 2nd March 2023. As I usually receive much smaller WUs I do wonder whether something could be done about assignment for this WU...

I'll purge the WU :(

I've attached parts of the log.

Code: Select all

20:52:21:WU00:FS00:0xa8:*********************** Log Started 2023-02-20T20:52:20Z ***********************
20:52:21:WU00:FS00:0xa8:************************** Gromacs Folding@home Core ***************************
20:52:21:WU00:FS00:0xa8:       Core: Gromacs
20:52:21:WU00:FS00:0xa8:       Type: 0xa8
20:52:21:WU00:FS00:0xa8:    Version: 0.0.12
20:52:21:WU00:FS00:0xa8:     Author: Joseph Coffland <joseph@cauldrondevelopment.com>
20:52:21:WU00:FS00:0xa8:  Copyright: 2020 foldingathome.org
20:52:21:WU00:FS00:0xa8:   Homepage: https://foldingathome.org/
20:52:21:WU00:FS00:0xa8:       Date: Jan 16 2021
20:52:21:WU00:FS00:0xa8:       Time: 12:29:40
20:52:21:WU00:FS00:0xa8:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
20:52:21:WU00:FS00:0xa8:     Branch: master
20:52:21:WU00:FS00:0xa8:   Compiler: Visual C++ 2019 16.7
20:52:21:WU00:FS00:0xa8:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
20:52:21:WU00:FS00:0xa8:   Platform: win32 10
20:52:21:WU00:FS00:0xa8:       Bits: 64
20:52:21:WU00:FS00:0xa8:       Mode: Release
20:52:21:WU00:FS00:0xa8:       SIMD: avx2_256
20:52:21:WU00:FS00:0xa8:     OpenMP: ON
20:52:21:WU00:FS00:0xa8:       CUDA: OFF
20:52:21:WU00:FS00:0xa8:       Args: -dir 00 -suffix 01 -version 706 -lifeline 9376 -checkpoint 30 -np 2
20:52:21:WU00:FS00:0xa8:************************************ libFAH ************************************
20:52:21:WU00:FS00:0xa8:       Date: Jan 16 2021
20:52:21:WU00:FS00:0xa8:       Time: 11:24:13
20:52:21:WU00:FS00:0xa8:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
20:52:21:WU00:FS00:0xa8:     Branch: master
20:52:21:WU00:FS00:0xa8:   Compiler: Visual C++ 2019 16.7
20:52:21:WU00:FS00:0xa8:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
20:52:21:WU00:FS00:0xa8:   Platform: win32 10
20:52:21:WU00:FS00:0xa8:       Bits: 64
20:52:21:WU00:FS00:0xa8:       Mode: Release
20:52:21:WU00:FS00:0xa8:************************************ CBang *************************************
20:52:21:WU00:FS00:0xa8:       Date: Jan 16 2021
20:52:21:WU00:FS00:0xa8:       Time: 11:23:53
20:52:21:WU00:FS00:0xa8:   Revision: c5816759c404e4b65f9f364c3d1ef554a67c4225
20:52:21:WU00:FS00:0xa8:     Branch: master
20:52:21:WU00:FS00:0xa8:   Compiler: Visual C++ 2019 16.7
20:52:21:WU00:FS00:0xa8:    Options: /TP /std:c++14 /nologo /EHa /wd4297 /wd4103 /O2 /Zc:throwingNew /MT
20:52:21:WU00:FS00:0xa8:   Platform: win32 10
20:52:21:WU00:FS00:0xa8:       Bits: 64
20:52:21:WU00:FS00:0xa8:       Mode: Release
20:52:21:WU00:FS00:0xa8:************************************ System ************************************
20:52:21:WU00:FS00:0xa8:        CPU: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz
20:52:21:WU00:FS00:0xa8:     CPU ID: GenuineIntel Family 6 Model 61 Stepping 4
20:52:21:WU00:FS00:0xa8:       CPUs: 4
20:52:21:WU00:FS00:0xa8:     Memory: 7.88GiB
20:52:21:WU00:FS00:0xa8:Free Memory: 5.07GiB
20:52:21:WU00:FS00:0xa8:    Threads: WINDOWS_THREADS
20:52:21:WU00:FS00:0xa8: OS Version: 6.2
20:52:21:WU00:FS00:0xa8:Has Battery: true
20:52:21:WU00:FS00:0xa8: On Battery: false
20:52:21:WU00:FS00:0xa8: UTC Offset: 1
20:52:21:WU00:FS00:0xa8:        PID: 8028
20:52:21:WU00:FS00:0xa8:        CWD: C:\Users\ILee\AppData\Roaming\FAHClient\work
20:52:21:WU00:FS00:0xa8:********************************************************************************
20:52:21:WU00:FS00:0xa8:Project: 18469 (Run 103, Clone 1, Gen 0)
20:52:21:WU00:FS00:0xa8:Unit: 0x00000000000000000000000000000000
20:52:21:WU00:FS00:0xa8:Reading tar file core.xml
20:52:21:WU00:FS00:0xa8:Reading tar file frame0.tpr
20:52:21:WU00:FS00:0xa8:Digital signatures verified
20:52:21:WU00:FS00:0xa8:Calling: mdrun -c frame0.gro -s frame0.tpr -x frame0.xtc -cpt 30 -nt 2 -ntmpi 1
Last edited by Joe_H on Thu Feb 23, 2023 8:42 pm, edited 2 times in total.
Reason: added code tags to log
Joe_H
Site Admin
Posts: 7922
Joined: Tue Apr 21, 2009 4:41 pm
Hardware configuration: Mac Pro 2.8 quad 12 GB smp4
MacBook Pro 2.9 i7 8 GB smp2
Location: W. MA

Re: Project: 18469 will not finish within expiration date

Post by Joe_H »

Welcome to the folding support forum.

How many percent has this WU completed? If it is less than 3-5% and your client has never processed a WU from this project, the estimates will not be accurate for ETA or PPD. Let it run for a bit and see where the estimates settle to.
Image

iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
JimboPalmer
Posts: 2522
Joined: Mon Feb 16, 2009 4:12 am
Location: Greenwood MS USA

Re: Project: 18469 will not finish within expiration date

Post by JimboPalmer »

Welcome to Folding@Home!

https://www.techpowerup.com/cpu-specs/c ... 300u.c1808
This appears to be a mobile CPU that does modern math. (AVX2-256) with only 2 cores and 4 threads. I would watch CPU temps as a laptop may have listed cooling.
Tsar of all the Rushers
I tried to remain childlike, all I achieved was childish.
A friend to those who want no friends
JimboPalmer
Posts: 2522
Joined: Mon Feb 16, 2009 4:12 am
Location: Greenwood MS USA

Re: Project: 18469 will not finish within expiration date

Post by JimboPalmer »

If you set CPUs to 2 you may get smaller projects you can finish on time
Tsar of all the Rushers
I tried to remain childlike, all I achieved was childish.
A friend to those who want no friends
redgreene
Posts: 4
Joined: Tue Feb 21, 2023 7:26 am

Re: Project: 18469 will not finish within expiration date

Post by redgreene »

I am having a similar issue. I have had a WU from Project 18469 for about 3 days now and so far it has only reached 7 percent with a consistent ETA of 30+ days. The expiration is still 7 days away. Is there value in letting it run for another week to expiration? I don't know how to dump/ditch/purge a WU to get another one.

Additional info, this is on a small laptop which has 2 cores and 4 threads from what I can tell.

I just don't want to hold the project hostage for a week only to contribute nothing to it in the end.
Akwan
Posts: 2
Joined: Tue Feb 21, 2023 7:42 pm

Re: Project: 18469 will not finish within expiration date

Post by Akwan »

Hello everyone,

sorry for the very late reply! I usually do not check this board, but again, I am very sorry.

Concering the WU, I had purged it at over 4 %, but I had consistent times of 5 hours per percent, so the estimate seemed reasonable. Especially as the laptop was not doing anything else and was not set to passive cooling (which roughly tripples the time a WU will need to finish)

I have FaH running on this machine since 2020, and yes, heat buildup can be an issue. I therfore throttle the machine to ca 85% and have the client set up to only use 2 cores.

Thank you for the warm welcome and the helpful suggestions.

Kind regards
Post Reply