Could the client save the work on a pause or shutdown?
Moderators: Site Moderators, FAHC Science Team
Could the client save the work on a pause or shutdown?
I frequently have to pause F@H to do other GPU-intensive tasks; unfortunately if I don't time this well I can lose a percent or two or work (since GPU units seem to revert to the last finished integer percent when I pause). Would it be possible to have the data automatically saved when the client is paused or is shut down?
-
- Site Admin
- Posts: 7937
- 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: Could the client save the work on a pause or shutdown?
The simple answer is no.
There are complications in stopping the processing of the WU data and having it in a consistent state usable for restarting after a pause or stop. One aspect is what data is on the GPU itself, and whether it has been replaced by other video data instead. The checkpoints are one point in time where the WU data is consistent, and verified by a sanity check run on the data in progress.
There are complications in stopping the processing of the WU data and having it in a consistent state usable for restarting after a pause or stop. One aspect is what data is on the GPU itself, and whether it has been replaced by other video data instead. The checkpoints are one point in time where the WU data is consistent, and verified by a sanity check run on the data in progress.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Re: Could the client save the work on a pause or shutdown?
Joe,
Is it possible to implement a feat, to pause at the next feasible state for pausing the client?
When my system is doing upgrades, or I need to reboot the system, I'm ok to press pause and have the client run a few more seconds to a minute to finish the WU to the first available savestate.
It's not imperative to have the client pause the WU right away, but neither do I want to wait until the WU finishes, or each WU reaches a savestate.
Since save states on WUs (I presume) are different on each graphics card, it would mean I could reboot my system when one card just passed it's save state, and lose almost no data, I might on my other cards.
It would be beneficial to have such a feat.
Especially for the windows client, that sometimes force closes FAH for updates.
Is it possible to implement a feat, to pause at the next feasible state for pausing the client?
When my system is doing upgrades, or I need to reboot the system, I'm ok to press pause and have the client run a few more seconds to a minute to finish the WU to the first available savestate.
It's not imperative to have the client pause the WU right away, but neither do I want to wait until the WU finishes, or each WU reaches a savestate.
Since save states on WUs (I presume) are different on each graphics card, it would mean I could reboot my system when one card just passed it's save state, and lose almost no data, I might on my other cards.
It would be beneficial to have such a feat.
Especially for the windows client, that sometimes force closes FAH for updates.
-
- Posts: 2040
- Joined: Sat Dec 01, 2012 3:43 pm
- Hardware configuration: Folding@Home Client 7.6.13 (1 GPU slots)
Windows 7 64bit
Intel Core i5 2500k@4Ghz
Nvidia gtx 1080ti driver 441
Re: Could the client save the work on a pause or shutdown?
It would be something like the Finish button but "finish at next checkpoint".
Re: Could the client save the work on a pause or shutdown?
I would love something like that too. Even the "finish at next checkpoint" would work much better than what we have currently.
Check out best weight loss shakes here.
-
- Site Admin
- Posts: 7937
- 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: Could the client save the work on a pause or shutdown?
Something like this has been proposed several times, there may even be an open ticket for it. But a brief look did not turn up one for me.
In the case of the CPU folding core A7 this has been done. On pausing the A7 core will attempt to write out a checkpoint before exiting, from what I have seen this works about 2/3 of the time. This is possible because the A7 core is based on a different processing method than GPU folding.
Now what you are looking for is this:
In the case of the CPU folding core A7 this has been done. On pausing the A7 core will attempt to write out a checkpoint before exiting, from what I have seen this works about 2/3 of the time. This is possible because the A7 core is based on a different processing method than GPU folding.
Now what you are looking for is this:
However due to the way the GPU core is coded, it often will not just be a short period of a few seconds to a minute, but 15 minutes or more before the next time for a checkpoint can be made.MeeLee wrote:When my system is doing upgrades, or I need to reboot the system, I'm ok to press pause and have the client run a few more seconds to a minute to finish the WU to the first available savestate.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Re: Could the client save the work on a pause or shutdown?
I, too, have wished we had such an option.
Pause at the next checkpoint could be created in either CPU or GPU versions but the complexity of the code changes would be different.
Pause at the next checkpoint could be created in either CPU or GPU versions but the complexity of the code changes would be different.
Posting FAH's log:
How to provide enough info to get helpful support.
How to provide enough info to get helpful support.