Folding Forum

Not giving me any WU's on one rig.......is it down too???

It's not down, but it has very few WUs to give away

& here we go again, keep getting assigned to .64 client sits idle .. sigh...

toTOW wrote:It's not down, but it has very few WUs to give away

.

Why isn't the AS connecting those without work to an alternative SMP WS ???

Idleness costs money; an idle rig still consumes a lot of Power and vents some heat in rooms that many are cooling with an AC ...

.

Try restarting your client--if you're using a 6.29 client especially with -advanced methods, there are a bunch of servers available.
We're phasing out server 171.64.65.64.

kasson wrote:Try restarting your client--if you're using a 6.29 client especially with -advanced methods, there are a bunch of servers available.
We're phasing out server 171.64.65.64.

Does not -advmethods mean even more late stage beta work units & more babysitting?
combine that with bigger uploads of these SMP2 work units I may have to stop there.
I can only get 450kb/s upload speed (MAX!) on my plan & with what 40MB or 50MB upload from Aus to LA it ties up my Internet connection for too long!
I frequently upload @ only 21kb/s (current average) so may have to rethink my contribution to the project.

For info I was bumped from .64 eventually to .140 & got work but even that server is slow to get work now.

BTW I have a 20.5MB protein uploading now to server .140, 30minutes & still counting!
Edit just finished 32mins to upload.

Teddy

-advmethods does not equal more baby sitting. That is a misconception, especially considering the late stage beta nature of all A3 SMP work units. They're all late stage beta WUs, whether coming from a work server configured with that flag or not.

There is an alternate choice. Start using the Prompt for network connection setting in the client. Then you can control when the client ties up your internet connection, or not.

Teddy wrote:..Does not -advmethods mean even more late stage beta work units & more babysitting?
combine that with bigger uploads of these SMP2 work units I may have to stop there.
I can only get 450kb/s upload speed (MAX!) on my plan & with what 40MB or 50MB upload from Aus to LA it ties up my Internet connection for too long!
I frequently upload @ only 21kb/s (current average) so may have to rethink my contribution to the project.

For info I was bumped from .64 eventually to .140 & got work but even that server is slow to get work now.

BTW I have a 20.5MB protein uploading now to server .140, 30minutes & still counting!
Edit just finished 32mins to upload.

Teddy

The WUs available are just before they go Public. I have been using the -advmethods since I started SMP2 and have finished 160+ WUs and none of them gave me problems. I don't really have to babysit the the Client, I just check every 7 hours (standard time to finish a WU) to make sure that I didn't get any errors and so far not a single one on the SMP2.
So far, these are the WU results sizes that I have come across:
~3 MB = only a handful and it takes me <15 minutes to upload.
~20 MB = more common and it takes me 15 - 45 minutes to upload.
~60 MB = only for P 6040 & P 6041 and it takes <2 hours to upload.

Yes my upload speed is ~10kbps and when the WU result is larger then 20 MB, during the upload process, I restart the Client so that I can be assigned a new WU and the finished WU will continue to upload in the background. (I hope that it isn't harmful to the Servers?)

So basically you are saying it is OK to run the -advmethods switch if so I will run that I know in the past usage of that usually brought more problems.
I don't really want bigger uploads much either & running multiple clients will just choke the connection.

Like I said I may have to reevaluate my contribution to this project &
Yes I have stuck with the project for nearly 9 years (joined the orig Folding 1.0) & over 50 million points later for Overclockers Australia folding as Teddy2(OCAU) I am not new to the project.

Teddy

Any statements made about differences with -advmethods are at least partly false. The WUs that are classified as advmethods change unpredictably so whatever was true at one time has also been false at other times.

e,g,- more babysitting? well, sometimes -- but if you happen to find one of those times and if you want to remove -admethods, go ahead. Of course if you fail to report your problem, the same Project may be released to general FAH (non-advmethods) without any changes and then you and alot of other people may find yourself running WUs from inadequately tested projects.

e.g.- ... 7 hours (standard time to finish a WU)? Nope. There is no standard time to finish a WU. Projects vary. Fast ones get fewer points than slower ones but looking at it from the other side, there's a wide variation in points per WU which must mean that there's a wide variation in hours per WU.

bruce wrote:...e.g.- ... 7 hours (standard time to finish a WU)? Nope. There is no standard time to finish a WU. Projects vary. Fast ones get fewer points than slower ones but looking at it from the other side, there's a wide variation in points per WU which must mean that there's a wide variation in hours per WU.

You are correct bruce but my point in the post was specific to me only and I guess I wasn't being specific so this is the longer version:
Only on my system, majority of WUs take 6-7 hours to finish and the only WUs that break this cycle are the P 6040, P 6041 & P 6701. Now this is all relative to the WUs and Projects being handed out. (I am sure that it will change in the future as new Projects and Cores are developed) Thus my personal "babysitting" is every 6-7 hours for ~5 minutes when I check if there are any problems by scanning the FAHLog. Personally, I wouldn't call it babysitting, just "checking-up" is more like it for me on my current set-up.