You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just a suggestion, feel free to delete if this isn't inline with your thinking.
Premise:
Everybody will need to do maintenance sometime.
Nobody wants to lose the plots currently in progress.
Suggestion:
A command line option to stop creating new plots at a designated time.
MVP 1 would be just that. A command to prevent new plots from being created while letting in-progess plots continue. When sent it will stop new plots from being created. User waits until all plots are complete, can shutdown safely and resume after maintenance.
MVP 2 could take it a step further and allow scheduling for 1 time, daily, weekly (ex. chron scheme).
To hit a particular point in time it could use avg. plot time + margin of error.
EX: If avg. plot time is 5 hours and scheduled maintenance is 6pm then stop new plotting at 12:30pm for an (arbitrary) 10% margin of error. Ideally the percentage would be just enough to ensure the last plot can complete prior to scheduled time, but 99% of us would probably be happy enough just to be assured all our plots are done prior to maintenance and not worry as much about the 20-30 minutes lost.
The text was updated successfully, but these errors were encountered:
That's an excellent point. My head was more focused on the scheduling aspect of it, but I could do that now with just a chron to swap out the config file.
Just a suggestion, feel free to delete if this isn't inline with your thinking.
Premise:
Suggestion:
A command line option to stop creating new plots at a designated time.
MVP 1 would be just that. A command to prevent new plots from being created while letting in-progess plots continue. When sent it will stop new plots from being created. User waits until all plots are complete, can shutdown safely and resume after maintenance.
MVP 2 could take it a step further and allow scheduling for 1 time, daily, weekly (ex. chron scheme).
To hit a particular point in time it could use avg. plot time + margin of error.
EX: If avg. plot time is 5 hours and scheduled maintenance is 6pm then stop new plotting at 12:30pm for an (arbitrary) 10% margin of error. Ideally the percentage would be just enough to ensure the last plot can complete prior to scheduled time, but 99% of us would probably be happy enough just to be assured all our plots are done prior to maintenance and not worry as much about the 20-30 minutes lost.
The text was updated successfully, but these errors were encountered: