• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

FAH: Why such long delays between WUs??

mgpaulus

Golden Member
Hey,

I just joined FAH, and I have a few machines folding. But, my main problem is I have this XP 1800 that is hungry, hungry, hungry. And it pains me to see 30 minutes or more of idle time between protein downloads. Is the problem my connection (Which I have been having some problems with lately), or is the problem somewhere off in stanford land?? (And where is that doggone foldqueue anyway???)

 
I'm gonna go with your connection being the problem. In looking at my stats, it shows start time and end times, there is never more that 30 seconds between the end of one and the beginning of the next.
 
I would also say it probably your connection.. I have not had any delays on getting WU's to work on. I have been folding for over a month now.....
 
You can run more than one client at a time if you are using thee 2.19 console version. Just put the console in another folder and rename it with a different name than the other one and drag a new shortcut to desktop. Running two clients does not do more work, they each do half as much, which ends up being the same output as one. The advantage is that if one is waiting for work, the other one is running at 100%.
By doing this you should never run out of work especially if you stagger them so that one is half done when you start the other. If they get too close together, shut one down till the other gets ahead. 🙂
 
It'll depend on which server you are hitting. Some of them are slow slow and if you get a WU from a particular server, you have to return the result back to that same server, whether it's working okay or not. Agree about running 2 instances in case that happens. It may appear that you get slowed down production-wise, but then at least you won't be sitting idle if you can't connect to a particular server. 🙂
 
Well, I have some more info. When I run fah2console with verbosity 9, it tells me the following:

+ Attempting to get work packet
- Connecting to assignment server
Initial: 40AB - Successful: assigned to (171.64.122.117).
+ News From Folding@Home: Welcome to 2.0
- Connecting to server (171.64.122.117) on port 8080
+ Requesting work
Network send failure: status = 0
- Error: Getwork #1 failed, and no other work to do. Waiting before retry

I'm leaving for 3 days of vacation this morning, so I guess it'll have to sort it's self out over the long run.....
 
It may depend on the protein you're folding, when you finish one, the next one that's sent to you is based on the one that you just finished. Sounds like Stanford's comp is looking at your data to decide which one to send next...

*edit* good point about have 2 folders and running both at the same time, I've just done it. It's gonna slow me down a little at first, then should pick back up 🙂
 
Back
Top