Folding Forum

In a nutshell the pattern is that the computer can sit for hours and hours not doing any WU's but if I reboot the computer it instantly loads up a WU to get crunching on and will do several WU's in a row. At first I put this down to F@H still not having enough work for all of the people who recently came onboard, but after seeing this behavior a few times I realized a pattern.

Questions, thoughts, suggestions?

Probably because it's resetting the next attempt timer for contacting the server again. You can achieve the same effect by pausing and resuming the slot.

Frogging101 wrote:Probably because it's resetting the next attempt timer for contacting the server again. You can achieve the same effect by pausing and resuming the slot.

Yes I've noticed that contact duration grows longer and longer when it doesn't get a WU to do but something seems obviously amiss here if I repeatedly end up getting work the moment the computer is restarted. It seems to me that if work is available to be assigned then there is a delay in getting it done if user systems are sitting idle.

It's either that or perhaps my client is getting work and not starting them until the reboot occurs (also I'm not seeing the work in waiting on the control panel). I hope there is an explanation for this behavior.

I doubt that. Find a segment of FAH's log where a new WU is downloaded and post the segment up to the point that it actually starts folding. (There will be lots of information between those events but probably not much elapsed time.)

bruce wrote:I doubt that. Find a segment of FAH's log where a new WU is downloaded and post the segment up to the point that it actually starts folding. (There will be lots of information between those events but probably not much elapsed time.)

The log appears to refresh for every session (uptime) but today after I restarted the computer the folding hasn't stopped. I did follow the log yesterday and was looking at it to see that it had been checking with the servers at ever increasing time intervals for a job. Keep in mind that this box can only do CPU based work (I have a new RTX GPU coming Wednesday) but even so that doesn't explain why three times now when the box was restarted that it got a WU to crunch on instantly.

One or two times I could see it as a coincidence but after three times I don't accept that is the case without some explanation. I'm honestly not trying to be difficult, this looks like a bug to me. That is what I'm concerned about.

Okay so I rebooted the computer again but before that I captured the log. However this time the client did not immediately get work, it took about ten minutes instead. So now I'm not sure what to think.

The log in its entirety is too big to post. I'll see if I can find a host for a compressed file or I can pare it down by cutting off the first half or something if you would like to examine it.
"Your message contains 92217 characters. The maximum number of allowed characters is 60000."