What causes the timered checkpoints in the 2605?

[dfonda]

I only get these in the 2605 (SMP on Linux)
[09:44:22] Completed 95000 out of 500000 steps (19 percent)
[09:59:23] Timered checkpoint triggered.
[10:02:36] Writing local files
[10:02:37] Completed 100000 out of 500000 steps (20 percent)
[10:17:37] Timered checkpoint triggered.
[10:20:51] Writing local files
[10:20:51] Completed 105000 out of 500000 steps (21 percent)


Are they caused by frame times over 15 min? (In which case I'm stuck with them)

Or by a setting that can be changed in configuration? How is that done?

Thanks

[jws2346]

I only get these in the 2605 (SMP on Linux)
Are they caused by frame times over 15 min? (In which case I'm stuck with them)
Or by a setting that can be changed in configuration? How is that done?
Thanks
I hope you get this "timered checkpoint" thing straightened out, I have always got "timered checkpoints" doing any type of WU :eh?: I thought the setting for length of time between checkpoints decided how often your machine checked (ie up to 30 mins), for WU's that take more time (ie patty melts) you set the "timered checkpoint" higher :confused: ? Would someone please explain Thank you :thup:

[Macaholic]

Use -configonly to change the advanced options settings. Default is set to save progress every 15 minutes. You can set it as low as every 3 minutes (or higher), but that makes for an awful massive log output and hard disk read/write wear and tear. ;)

[dfonda]

OFF TOPIC JWS you mentioned in another post that you have the lm sensors working on your rigs including the Asrock MOBO I have. If you get the time I wonder if you could write a how to on it. I must be galactically challenged that I haven't been able to get them to work.

[dfonda]

Use -configonly to change the advanced options settings. Default is set to save progress every 15 minutes. You can set it as low as every 3 minutes (or higher), but that makes for an awful massive log output and hard disk read/write wear and tear. ;)
How Mac? Shut it down then start it up with ./fah5 -configonly -forceasm -verbosity 9 Or just -configonly at first.

And Thanks It would be great if this would shave a minute off the frame times.

[ChasR]

On rigs that stay up 24/7 and aren't regularly rebooted on purpose or by accident, timered checkpoints should be set to 30 minutes.

Checkpoint times vary from WU to WU. The larger the upload, the longer it takes to write the checkpoint. You're looking at 1-2 seconds/checkpoint usually.

Ctrl-C in the terminal window, then ./fah5 -config -forceasm -verbosity 9

Using -config instead of -configonly will save you typing the startup string twice. The client will start on completion of -config but not -configonly.

If you happen to be using vmware you should set ignoredeadlines to yes during this config. This will keep you from losing WUs to deadline errors caused by the Linux clock going wonkers under vmware.

[dfonda]

Thanks Chasr its the 24/7 in my sig gonna change it to 30 min.right now.

Ouch 1 to 2 seconds, shoot I was hoping for 1-2 minutes. At least my raptor will work less.

EDIT -config= No more timered chckpoints.:thup: