Be sure to check the power management section as well as the screensaver section under system settings
Yea I checked all that it wasn't any of that. It would act like it was going to sleep - power light blinking and all - but it wouldn't wake up.
But ... now it works. Last time I tried it it wouldn't work, since then I think there's been at least one Linux kernel update. Maybe that fixed it I dunno. But now I can put it to sleep to save power and wake it up again next evening and no loss of compute time - starts with the last state in BOINC and the last % progress. Has nothing to do with checkpoints it's going to sleep baby!
Processing work units with "outdated" (according to Microsoft) Ryzen 7 1700
Be sure to check the power management section as well as the screensaver section under system settings
Yea I checked all that it wasn't any of that. It would act like it was going to sleep - power light blinking and all - but it wouldn't wake up.
But ... now it works. Last time I tried it it wouldn't work, since then I think there's been at least one Linux kernel update. Maybe that fixed it I dunno. But now I can put it to sleep to save power and wake it up again next evening and no loss of compute time - starts with the last state in BOINC and the last % progress. Has nothing to do with checkpoints it's going to sleep baby!
This is an ongoing problem, well more of an annoyance to watch out for to avoid wasting CPU time. It affects the FGRP5 CPU app. [...]
I'd like to add: the current run of O3MD1 CPU work units also has a differing number (between 32 and 64) of checkpoints. Those with only 32 checkpoints are also quite some bummers on older computers not running 24/7. It easily takes an hour between checkpoints for such work units too.
Number of checkpoints can only be found in stderr.txt logfile in WU's slot directory:
There are again a bunch of FGRP5 (CPU) tasks send out at the moment that only contain FIVE (5) skypoints, corresponding to only writing five checkpoints between 0% and 90% progress (i.e.: 18%, 36%, 54%, 72%, 90%). This can take hours on old computers.
Again they have a low number (here: 88.0 < 100) after the prefix "LATeah2009F" in the workunit name.
The only option to finish such tasks without wasting hours of computation is: don't stop them, don't shut down the computer. Instead send OS into hibernate mode (suspend to disk). Or one can carefully watch the progress meter in BOINC manager and check the task details for "CPU time since last checkpoint" before shutting down the computer shortly after one of the few checkpoints was written.
I will search for a solution
)
I will search for a solution to the sleep function again today and see what I can come up with. I will report back if I find one ...
Processing work units with "outdated" (according to Microsoft) Ryzen 7 1700
Be sure to check the power
)
Be sure to check the power management section as well as the screensaver section under system settings
mikey wrote: Be sure to
)
Yea I checked all that it wasn't any of that. It would act like it was going to sleep - power light blinking and all - but it wouldn't wake up.
But ... now it works. Last time I tried it it wouldn't work, since then I think there's been at least one Linux kernel update. Maybe that fixed it I dunno. But now I can put it to sleep to save power and wake it up again next evening and no loss of compute time - starts with the last state in BOINC and the last % progress. Has nothing to do with checkpoints it's going to sleep baby!
Processing work units with "outdated" (according to Microsoft) Ryzen 7 1700
HAL wrote: mikey wrote: Be
)
WOO HOO!!
Just means hibernate mode is
)
Just means hibernate mode is working as it should. The PC is saving its compute state to disk file and replaying it upon wakeup.
Scrooge McDuck schrieb:This
)
I'd like to add: the current run of O3MD1 CPU work units also has a differing number (between 32 and 64) of checkpoints. Those with only 32 checkpoints are also quite some bummers on older computers not running 24/7. It easily takes an hour between checkpoints for such work units too.
Number of checkpoints can only be found in stderr.txt logfile in WU's slot directory:
2023-02-13 03:52:03.6794 (8268) [normal]: Cpt:0, total:32, sky:1/1, f1dot:1/32There are again a bunch of
)
Again they have a low number (here: 88.0 < 100) after the prefix "LATeah2009F" in the workunit name.
The only option to finish such tasks without wasting hours of computation is: don't stop them, don't shut down the computer. Instead send OS into hibernate mode (suspend to disk). Or one can carefully watch the progress meter in BOINC manager and check the task details for "CPU time since last checkpoint" before shutting down the computer shortly after one of the few checkpoints was written.