Running off-line on Linux with a 5.2.14 optimized client. That computer had "gotten ahead" with its internal clock. I manually reset its clock several minutes backwards.

I was VERY surprised that my CPU monitor showed that the running BOINC application had STOPPED USING THE CPU !! After exactly that many minutes (i.e., when the internal clock had caught up to some sort of recorded time value), the BOINC application started again to use the CPU.

All I can figure out is that the client was waiting for the next successive (according to the wall clock) heartbeat.

What if I had need to set the computer's clock back by hours -- is it worth it to the BOINC logic to have the computer simply sit there idle for that much time ?
.