F@H bigadv on windows down

Man of Honour
Joined
30 Oct 2002
Posts
15,849
Location
Surrey
Looks like it only affect windows machines, my linux vmware image seems to have got one no problem.

Re: Updates thread

Postby kasson » Tue May 31, 2011 5:10 pm
bigadv server 130.237.232.141 is going into accept-only mode for a few days. We're getting ready to upgrade the server software there, and we can't have any outstanding jobs when we do that.

More information here:
1) Server Software being upgraded (Post)
2) Additional bigadv Projects entering Beta Testing soon (Thread)
 
Last edited:
My linux bigadv machine ran dry last night, it was idle for about 40 mins. I switched it to normal smp, after it did one WU I switched back, it then picked up a bigadv ok.
 
Same here I had no work on linux last night for a couple of hours then it was fine.

Interesting about the new work units, 2G RAM, 12 cores required - looks like only a few people on the team will be able to try them.
 
I ran dry on Hydra last night at about 1.30 still no work:mad:

For some reason they're not falling back to standard smps, I had to remove the -bigadv flag to get any work. Do you know what ppd you get from standard WU on Hydra? awesome machine BTW.
 
Looks like it only affect windows machines, my linux vmware image seems to have got one no problem.

2) Additional bigadv Projects entering Beta Testing soon (Thread)

Does this mean we have to run -bigbeta rather than -bigadv to snag one?
 
Not had time to drop Hydra onto smp been away from my rigs all weekend and when i got back the garden had gone mad, been fighting with that all day and back to work now:rolleyes:
 
I've dropped everything to -advmethods except my VMware machine which is still eating its way through a bigadv
SR-2 is doing well with 82K PPD on 24 threads, but its nothing compared to the 145K it should be doing.
 
You all might want to try jumping back in, both my Linux and Win box picked up 6901s this morning.
 
Its random apparently, there is a massive shortage of work. For me I don't babysit my rigs enough to manually switch them over and they aren't automatically switching over either so there is a high likelyhood that they will just sit there idle for hours if they can't get a bigadv WU.
 
I've been quite lucky so far, both my rigs have since picked up bigadvs again, no delay, though one is a 2684.
 
Does this mean we have to run -bigbeta rather than -bigadv to snag one?

To answer my own question, it's -bigbeta, and they are being dished out now, major points increase apparently going by comments in other forums. Myself, I stopped my linux p6901 @ 61% and swapped to bigbeta, restarted and it went back to 0% yippee!! :mad: I'd liked to say live and learn but I knew how flaky linux is, should've backed up, my fault, but baba and biffa and anyone else running linux with 12 cores or more, switch to -bigbeta, love to see what ppd you get, especially baba's.
 
Back
Top Bottom