Skip to content
This repository has been archived by the owner on Jul 13, 2024. It is now read-only.

Sluggish experience when not paused and Wasted processing data when paused #1710

Open
jeffreymiller25 opened this issue Aug 14, 2023 · 0 comments

Comments

@jeffreymiller25
Copy link

jeffreymiller25 commented Aug 14, 2023

Your issue may already be reported!
Please search on the issue tracker before creating one.

Is your feature request related to a problem?

The problem is a few things.

  1. When I'm folding and using my computer at the same time, everything is noticeably sluggish, and video playback is like 10 FPS. It is frustrating to use, but I live with it as best I can, because I believe in the cause, and want to help.
  2. After pausing folding, to allow computer to function normally, and resuming folding, it throws away up to 2% of the work it had already done, as if it's not saving as it goes, except in 2% increments.
  3. The work units given to my machine take about 24-48 hours to complete, which exacerbates issue 2, because it throws out upwards of 30 minutes worth of work. (Now we're just wasting my money on electricity)
  4. Due to the poor user experience while it folds, I'm inclined to pause it, and since it throws chunks of work away, it doesn't do me any good to pause it briefly and re-enable it, so I'm inclined to leave it off for long/longer periods. Unfortunately, I only get about 3-4 days in which to process 24-48 hours of work, and if I pause it to long, (or forget to unpause it), I run the risk of not completing the work unit, and then all of the work is discarded and was a waste.

Describe the Feature

My suggestions are...

  1. Make the FAH processing automatically take a back seat or stop completely while the computer is being used for other things, without making someone "pause"/"unpause". If it doesn't interfere with my use, I'll leave it running all the time, which is what we want.
  2. Make it save data more frequently, so it doesn't throw out 2% of work when it is paused. Like 0.1% is the most it should ever be allowed to lose. Ideally, it wouldn't lose anything.
  3. Make the work units significantly smaller, so that each one is only 2-4 hours of work, so that if one isn't completed in time, and has to be discarded, that we don't throw out tens of hours of processing time.

Context

These features will allow me to continue using FAH. I'm trying to make it so people will want to leave it on their computers, doing what it's made to do. Right now, I'm about ready to uninstall it again due to the poor user experience and wasted computing time. I'll check back in next year, and see if it's gotten better.
I really do want your project to succeed, and I hope you can make the suggested improvements.
Sincerely trying to help

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant