• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Not getting Bigadv

D

dmaine

Weaksauce
Joined
Oct 4, 2010
Messages
77
I stopped foldng for a little while to help out the DC Commandos in April and May. My 2600k had been reliably getting bigadv before i switched. Now that i am back, i havent recieved one. I'm still using GPU tracker to run SMP and GPU as previous. Any ideas? Tired of getting these little 69xx and 71xx .

Launch directory: E:\FAH GPU Tracker V2\SMP
Executable: E:\FAH GPU Tracker V2\FAH.exe
Arguments: -oneunit -forceasm -smp 8 -bigadv -verbosity 9

[12:05:39] - Ask before connecting: No
[12:05:39] - User name: dmaine (Team 33)
[12:05:39] - User ID: XXXXXXXXXXXXXXXXXXXXXX
[12:05:39] - Machine ID: 2
[12:05:39]
[12:05:39] Work directory not found. Creating...
[12:05:39] Could not open work queue, generating new queue...
[12:05:39] - Preparing to get new work unit...
[12:05:39] - Autosending finished units... [May 31 12:05:39 UTC]
[12:05:39] Cleaning up work directory
[12:05:39] Trying to send all finished work units
[12:05:39] + Attempting to get work packet
[12:05:39] + No unsent completed units remaining.
[12:05:39] Passkey found
[12:05:39] - Autosend completed
[12:05:39] - Will indicate memory of 8175 MB
[12:05:39] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 10, Stepping: 7
 
i know which are the big adv, there are a set of newer wu's , standard smp that start with 697x and so on. they are better than 6701's but want to get this 2600k back to big adv again.
 
Make sure the client is set to take big WU from normal if your using comand line.
 
Your FAH GPU Tracker settings are correct for a 2600K. See what project you pull when the current unit completes.

Arguments: -oneunit -forceasm -smp 12 -bigadv -verbosity 9

[22:09:28] - Ask before connecting: No
[22:09:28] - User name: KMac (Team 33)

Edit
I just fired up another Bigadv box to see what unit I was assigned. There seems to be an issue on Stanford's assignment server.
Check your log beginning with the line just after what you posted.


[15:31:39] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 10, Stepping: 5
[15:31:39] - Connecting to assignment server
[15:31:39] Connecting to http://assign.stanford.edu:8080/
[15:31:39] Posted data.
[15:31:39] Initial: ED82; - Successful: assigned to (130.237.232.237).
[15:31:39] + News From Folding@Home: Welcome to Folding@Home
[15:31:39] Loaded queue successfully.
[15:31:39] Sent data
[15:31:39] Connecting to http://130.237.232.237:8080/
[15:31:40] Posted data.
[15:31:40] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[15:31:40] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.

...

[15:32:50] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[15:33:33] + Attempting to get work packet
[15:33:33] Passkey found
[15:33:33] - Will indicate memory of 6135 MB
[15:33:33] - Connecting to assignment server
[15:33:33] Connecting to http://assign.stanford.edu:8080/
[15:33:43] Posted data.
[15:33:43] Initial: ED82; - Successful: assigned to (130.237.232.237).
[15:33:43] + News From Folding@Home: Welcome to Folding@Home
[15:33:43] Loaded queue successfully.
[15:33:43] Sent data
[15:33:43] Connecting to http://130.237.232.237:8080/
[15:33:45] Posted data.
[15:33:45] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[15:33:45] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
 
Last edited:
just pulled another 6978
here is the log from the newest one. Im going to let this one go and fire up the new client to see how that goes.
Launch directory: E:\FAH GPU Tracker V2\SMP
Executable: E:\FAH GPU Tracker V2\FAH.exe
Arguments: -oneunit -forceasm -smp 8 -bigadv -verbosity 9

[16:49:13] - Ask before connecting: No
[16:49:13] - User name: dmaine (Team 33)
[16:49:13] - User ID:
[16:49:13] - Machine ID: 2
[16:49:13]
[16:49:13] Work directory not found. Creating...
[16:49:13] Could not open work queue, generating new queue...
[16:49:13] - Preparing to get new work unit...
[16:49:13] - Autosending finished units... [May 31 16:49:13 UTC]
[16:49:13] Cleaning up work directory
[16:49:13] Trying to send all finished work units
[16:49:13] + Attempting to get work packet
[16:49:13] + No unsent completed units remaining.
[16:49:13] Passkey found
[16:49:13] - Autosend completed
[16:49:13] - Will indicate memory of 8175 MB
[16:49:13] - Detect CPU. Vendor: GenuineIntel, Family: 6, Model: 10, Stepping: 7
[16:49:13] - Connecting to assignment server
[16:49:13] Connecting to http://assign.stanford.edu:8080/
[16:49:14] Posted data.
[16:49:14] Initial: 8F80; - Successful: assigned to (128.143.199.96).
[16:49:14] + News From Folding@Home: Welcome to Folding@Home
[16:49:14] Loaded queue successfully.
[16:49:14] Sent data
[16:49:14] Connecting to http://128.143.199.96:8080/
[16:49:15] Posted data.
[16:49:15] Initial: 0000; - Receiving payload (expected size: 1769160)
[16:49:16] - Downloaded at ~1727 kB/s
[16:49:16] - Averaged speed for that direction ~1727 kB/s
[16:49:16] + Received work.
[16:49:16] + Closed connections
[16:49:16]
[16:49:16] + Processing work unit
[16:49:16] Core required: FahCore_a3.exe
[16:49:16] Core found.
[16:49:16] Working on queue slot 01 [May 31 16:49:16 UTC]
[16:49:16] + Working ...
[16:49:16] - Calling '.\FahCore_a3.exe -dir work/ -nice 19 -suffix 01 -np 8 -nocpulock -checkpoint 3 -forceasm -verbose -lifeline 3336 -version 630'

[16:49:16]
[16:49:16] *------------------------------*
[16:49:16] Folding@Home Gromacs SMP Core
[16:49:16] Version 2.27 (Dec. 15, 2010)
[16:49:16]
[16:49:16] Preparing to commence simulation
[16:49:16] - Assembly optimizations manually forced on.
[16:49:16] - Not checking prior termination.
[16:49:17] - Expanded 1768648 -> 1957708 (decompressed 110.6 percent)
[16:49:17] Called DecompressByteArray: compressed_data_size=1768648 data_size=1957708, decompressed_data_size=1957708 diff=0
[16:49:17] - Digital signature verified
[16:49:17]
[16:49:17] Project: 6978 (Run 0, Clone 55, Gen 90)
[16:49:17]
[16:49:17] Assembly optimizations on if available.
[16:49:17] Entering M.D.
[16:49:23] Mapping NT from 8 to 8
[16:49:23] Completed 0 out of 500000 steps (0%)
 
not really a new 2600k, just switching back to folding from Boinc and DC

2:20 tpf? must be a nice machine, my OC of 4.4ghz only gets me a 2:42 tpf, good for 23-25k ppd. good enough for now but i like the 40k+ from bigadv.
just got the other 2 rigs in my basement running f@h also, with the ac on, the basement office gets really cold, and need the extra heat output
 
dmaine said:
not really a new 2600k, just switching back to folding from Boinc and DC

2:20 tpf? must be a nice machine, my OC of 4.4ghz only gets me a 2:42 tpf, good for 23-25k ppd. good enough for now but i like the 40k+ from bigadv.
just got the other 2 rigs in my basement running f@h also, with the ac on, the basement office gets really cold, and need the extra heat output
Click to expand...

are you folding on linux@64 ?
 
nah, i still have too many things that need windows, i might try it on my other machines but need the 2600k on windows for now.
 
dmaine said:
2:20 tpf? must be a nice machine, my OC of 4.4ghz only gets me a 2:42 tpf, good for 23-25k ppd. good enough for now but i like the 40k+ from bigadv.
Click to expand...

my 2600k @ 4.5 is pulling 2:22 tpf on p6946 in linux. My ppd dropped from 49k on p6901 to 30k on p6946.
 
Apparently, the -bigadv switch is not falling back to regular smp work any longer. All 5 of my machines are idle now, I guess I will just let then idle while we wait for more work or a fix to the fallback.
 
I just picked up a 6901, so it looks like the blip is over.

Lost a few hours folding before I woke up, switched it to vanilla smp and now it's picked up a biggy. I agree they have to sort their allocation servers out (with a fallback).
 
musky said:
Apparently, the -bigadv switch is not falling back to regular smp work any longer. All 5 of my machines are idle now, I guess I will just let then idle while we wait for more work or a fix to the fallback.
Click to expand...

I changed over two, the rest will have idle time/ time for me to play around with fans and stuff.

Also on the -smp for the i7-2600K it doesn't seem like much there, but it is over 100K ppd per machine going from -bigadv to -smp on beefier machines.
 
Wiseguy2001 said:
I just picked up a 6901, so it looks like the blip is over.

Lost a few hours folding before I woke up, switched it to vanilla smp and now it's picked up a biggy. I agree they have to sort their allocation servers out (with a fallback).
Click to expand...

I think it's still hit and miss. I had a machine just finish a bigadv, but failed to pick another one up. This particular machine is running Windows.
 
shutted down my sr-2, been running idle for 12 hours, the rig is spoiled and doesn't want regular smp :-/ especially since it heard about extra large bigadv, no way you can feed it vanilla smp anymore...
 
what could possibly be the excuse for failing to drop down to normal smp?

switched three rigs over to smp. not looking forward to switching back
 
If there was an easy way to do that, I would.
 
I am not an expert, but isnt the client limited to 16 instances on one OS? So to run more than 16 you would need VM's right? Sounds like a pain in the ass, but may be worth it in the long run to stabilize production.
 
All back up - my 3 rigs running windows just picked up 3 6901s over the last few hours. One six hours ago, and the other two in the last hour.

So it was about 16 hours down or so.

Actually the most recent is taking over 12 minutes to download, which is odd... (normally - 2-3 mins)
 
I switched my three rigs back to bigadv on the way out the door. I hope they don't spend the rest of the day idle after they finish their current smp WU.
 
still not geting bigadv

rig 1:
Code: 
[15:23:59] - Preparing to get new work unit...
[15:23:59] Cleaning up work directory
[15:24:01] + Attempting to get work packet
[15:24:01] Passkey found
[15:24:01] - Connecting to assignment server
[15:24:02] - Successful: assigned to (130.237.232.237).
[15:24:02] + News From Folding@Home: Welcome to Folding@Home
[15:24:02] Loaded queue successfully.
[15:24:02] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[15:24:08] + Attempting to get work packet
[15:24:08] Passkey found
[15:24:08] - Connecting to assignment server
[15:24:09] - Successful: assigned to (130.237.232.237).
[15:24:09] + News From Folding@Home: Welcome to Folding@Home
[15:24:09] Loaded queue successfully.
[15:24:10] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[15:24:27] + Attempting to get work packet
[15:24:27] Passkey found
[15:24:27] - Connecting to assignment server
[15:24:28] - Successful: assigned to (130.237.232.237).
[15:24:28] + News From Folding@Home: Welcome to Folding@Home
[15:24:28] Loaded queue successfully.
[15:24:29] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[15:24:52] + Attempting to get work packet
[15:24:52] Passkey found
[15:24:52] - Connecting to assignment server
[15:24:52] - Successful: assigned to (130.237.232.237).
[15:24:52] + News From Folding@Home: Welcome to Folding@Home
[15:24:52] Loaded queue successfully.
[15:24:53] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[15:25:36] + Attempting to get work packet
[15:25:36] Passkey found
[15:25:36] - Connecting to assignment server
[15:25:36] - Successful: assigned to (130.237.232.237).
[15:25:36] + News From Folding@Home: Welcome to Folding@Home
[15:25:37] Loaded queue successfully.
[15:25:37] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[15:27:05] + Attempting to get work packet
[15:27:05] Passkey found
[15:27:05] - Connecting to assignment server
[15:27:05] - Successful: assigned to (130.237.232.237).
[15:27:05] + News From Folding@Home: Welcome to Folding@Home
[15:27:05] Loaded queue successfully.
[15:27:06] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[15:29:52] + Attempting to get work packet
[15:29:52] Passkey found
[15:29:52] - Connecting to assignment server
[15:29:53] - Successful: assigned to (130.237.232.237).
[15:29:53] + News From Folding@Home: Welcome to Folding@Home
[15:29:53] Loaded queue successfully.
[15:29:54] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[15:35:14] + Attempting to get work packet
[15:35:14] Passkey found
[15:35:14] - Connecting to assignment server
[15:35:15] - Successful: assigned to (130.237.232.237).
[15:35:15] + News From Folding@Home: Welcome to Folding@Home
[15:35:15] Loaded queue successfully.
[15:35:16] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.

rig 2:

Code: 
[14:59:06] - Preparing to get new work unit...
[14:59:06] Cleaning up work directory
[14:59:07] + Attempting to get work packet
[14:59:07] Passkey found
[14:59:07] - Connecting to assignment server
[14:59:07] - Successful: assigned to (130.237.232.237).
[14:59:07] + News From Folding@Home: Welcome to Folding@Home
[14:59:08] Loaded queue successfully.
[14:59:08] - Attempt #1 to get work failed, and no other work to do.
Waiting before retry.
[14:59:13] + Attempting to get work packet
[14:59:13] Passkey found
[14:59:13] - Connecting to assignment server
[14:59:14] - Successful: assigned to (130.237.232.237).
[14:59:14] + News From Folding@Home: Welcome to Folding@Home
[14:59:14] Loaded queue successfully.
[14:59:14] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[14:59:32] + Attempting to get work packet
[14:59:32] Passkey found
[14:59:32] - Connecting to assignment server
[14:59:32] - Successful: assigned to (130.237.232.237).
[14:59:32] + News From Folding@Home: Welcome to Folding@Home
[14:59:33] Loaded queue successfully.
[14:59:33] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[14:59:53] + Attempting to get work packet
[14:59:53] Passkey found
[14:59:53] - Connecting to assignment server
[14:59:54] - Successful: assigned to (130.237.232.237).
[14:59:54] + News From Folding@Home: Welcome to Folding@Home
[14:59:54] Loaded queue successfully.
[14:59:54] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[15:00:38] + Attempting to get work packet
[15:00:38] Passkey found
[15:00:38] - Connecting to assignment server
[15:00:38] - Successful: assigned to (130.237.232.237).
[15:00:38] + News From Folding@Home: Welcome to Folding@Home
[15:00:38] Loaded queue successfully.
[15:00:39] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.
[15:02:03] + Attempting to get work packet
[15:02:03] Passkey found
[15:02:03] - Connecting to assignment server
[15:02:04] - Successful: assigned to (130.237.232.237).
[15:02:04] + News From Folding@Home: Welcome to Folding@Home
[15:02:04] Loaded queue successfully.
[15:02:04] - Attempt #6 to get work failed, and no other work to do.
Waiting before retry.
[15:04:49] + Attempting to get work packet
[15:04:49] Passkey found
[15:04:49] - Connecting to assignment server
[15:04:49] - Successful: assigned to (130.237.232.237).
[15:04:49] + News From Folding@Home: Welcome to Folding@Home
[15:04:49] Loaded queue successfully.
[15:04:50] - Attempt #7 to get work failed, and no other work to do.
Waiting before retry.
[15:10:25] + Attempting to get work packet
[15:10:25] Passkey found
[15:10:25] - Connecting to assignment server
[15:10:25] - Successful: assigned to (130.237.232.237).
[15:10:25] + News From Folding@Home: Welcome to Folding@Home
[15:10:25] Loaded queue successfully.
[15:10:26] - Attempt #8 to get work failed, and no other work to do.
Waiting before retry.
[15:21:12] + Attempting to get work packet
[15:21:12] Passkey found
[15:21:12] - Connecting to assignment server
[15:21:12] - Successful: assigned to (130.237.232.237).
[15:21:12] + News From Folding@Home: Welcome to Folding@Home
[15:21:12] Loaded queue successfully.
[15:21:13] - Attempt #9 to get work failed, and no other work to do.
Waiting before retry.
[15:42:45] + Attempting to get work packet
[15:42:45] Passkey found
[15:42:45] - Connecting to assignment server
[15:42:45] - Successful: assigned to (130.237.232.237).
[15:42:45] + News From Folding@Home: Welcome to Folding@Home
[15:42:45] Loaded queue successfully.
[15:42:46] - Attempt #10 to get work failed, and no other work to do.
Waiting before retry.

glad I only switched two of my rigs back this morning

lack of dropping down to smp is a facepalm full of fail :rolleyes:
 
I have a 6901 that will be finishing up in a few hours.. I hope there's more to be had, though, about 2 hours ago there were none for the 3x i7-2600 boxes I was having setup..
 
I am thinking this might be a wind down of the current -bigadv

With new ones on the way.... why keep 2 types of -bigadv?
 
Kendrak said:
With new ones on the way.... why keep 2 types of -bigadv?
Click to expand...

So those with quad I7 Intel systems can run bigadv unit and get bigadv bonuses. There is bound to be a higher logical core count requirement for the larger units, which will leave the single proc quad (and maybe even hex) Intel people outraged if they are no longer able to run bigadv. Look how ticked off people are now just because the supply of bigadv is low. I can only imagine how badly it would hurt the project if all the 8-12 logical core guys (probably the majority of the bigadv folders) can no longer run bigadv at all and take a ~40% ppd drop.
 
musky said:
So those with quad I7 Intel systems can run bigadv unit and get bigadv bonuses. There is bound to be a higher logical core count requirement for the larger units, which will leave the single proc quad (and maybe even hex) Intel people outraged if they are no longer able to run bigadv. Look how ticked off people are now just because the supply of bigadv is low. I can only imagine how badly it would hurt the project if all the 8-12 logical core guys (probably the majority of the bigadv folders) can no longer run bigadv at all and take a ~40% ppd drop.
Click to expand...

I would think that they wouldn't respond with "Well this was a trial anyways" because people will be very peeved.

Hopefully there will be a creative solution for this. Maybe some bigger SMP units with 6-thread requirements to "fill the void".

I realize research doesn't work this way (ie. the hardware doesn't define the research) but that would cause big trouble amongst the folding denizens.
 
Wost case senario is they have to adjust points to make people happy. Sounds like an easy way to make the donors happy, and the science will get done with the usual zeal that hardcore folders have.
 
musky said:
So those with quad I7 Intel systems can run bigadv unit and get bigadv bonuses. There is bound to be a higher logical core count requirement for the larger units, which will leave the single proc quad (and maybe even hex) Intel people outraged if they are no longer able to run bigadv. Look how ticked off people are now just because the supply of bigadv is low. I can only imagine how badly it would hurt the project if all the 8-12 logical core guys (probably the majority of the bigadv folders) can no longer run bigadv at all and take a ~40% ppd drop.
Click to expand...

I see that as point, as do you.... but not sure PG see it that way.
 
I had one box that got one over night last night and one that didn't. It is all sorts of random and it is a screw up on their end because the server is sending us over there when they don't have anything to hand out. It should just send us some where else.
 
You must log in or register to reply here.
Back
Top