• 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.

Big Adv Drought?

capreppy

[H]ard|DCer of the Month - April 2009
Joined
Jul 4, 2007
Messages
3,410
Started yesterday. Dedicated i7 started getting A3 SMP WUs around 12 hours ago. My SR-2 started getting A3 SMP WUs around 5 hours ago. My Sig Rig is still crunching a Big Adv, but it takes it a while since it is also powering 3x GTX285's.

So is there a Big Adv shortage?
 
I have noticed it too...my L5640 has gotten a 6060 and a 6056 project...havent seen a bigadv unit yet....maybe it's temporary.
 
It's pretty sad watching an SR2 crunch a P670x WU. 50K PpD (thankfully it only takes 5 hours to go through it). My PpD at this exact moment is 100K less than normal due to the P670x.....Truly Sad Panda, but at least the science is getting done.
 
I should be dropping two bigadv today, I will let ya know what I pick up.
 
I just picked up a 6900 last night, so I haven't seen any lack of bigadv units. granted, i'm only running a single bigadv client which was occupied by a 2684 for the last couple days
 
I blame the influx of overclocked 2600k's..

I've just been dealt a P6063 running around 5k ppd, I feel like i've been put on the naughtly step.
 
It's pretty sad watching an SR2 crunch a P670x WU. 50K PpD (thankfully it only takes 5 hours to go through it). My PpD at this exact moment is 100K less than normal due to the P670x.....Truly Sad Panda, but at least the science is getting done.

Its sad watching anyone crunch one of them. Maybe the bigadv people are taking them away from my puny X6:D (I had six WU in a row without a 670x, until my current one right now but last week I had something like 9, 670x in a row)
 
I blame the influx of overclocked 2600k's..

I've just been dealt a P6063 running around 5k ppd, I feel like i've been put on the naughtly step.

I can see this.

We have always been told that new -bigadv are dependant on the current batch getting done. Can't make any new ones till you know what the results of the old ones where. (Hence one of the reasons for the bonus system)

If you increese demand for -bigadv all of a sudden, you can hit a shortfall.

On top of that -bigadv is a side program so to speak. We where never told -bigadv would always be there.
 
Last edited:
3 of my SR-2s processed one smp unit before picking up anothe bigadv yesterday. One was on its fourth smp in a row when I left for work this morning. The two non-SR-2 rigs finished their bigadvs and picked up new bigadvs immediately yesterday. So, it is hit and miss right now.
 
picked up a 6040 last night. it finished and now its doing..............a 6702.

seem like there might be a drought
 
Well my SR2 finished the 6701 and picked up a P2686 so I'm safe for 21 hours. My i7 should wrap up it's 4th A3 SMP WU and hopefully can pick up a P2686. I've not seen a P6900 in a day, but I'll take a P2686 over an P670x any day.
 
Without obtaining a unit not designed for the system, is it frowned upon to move a -bigadv unit from one machine to another faster machine?
EG: SR-2 gets a p6701 and i7-920 gets a p6900. Can I pause/swap the jobs? No GPU on either system.
 
for some reason this wu 6702 wu ended early like the 6 from last night. It finally picked up another big adv.
 
Without obtaining a unit not designed for the system, is it frowned upon to move a -bigadv unit from one machine to another faster machine?
EG: SR-2 gets a p6701 and i7-920 gets a p6900. Can I pause/swap the jobs? No GPU on either system.
I'm in the same situation. I'm considering trying it out. It should work with machines with same machine ID (usually the case) and same time zone.
 
I'm considering trying it out. It should work with machines with same machine ID (usually the case) and same time zone.

I know it will work, I just don't know if it is 'allowed'.
This weekend, my netbook was sitting idle due to a lack of classic client jobs, so I switched it to SMP (an Atom has two threads, right?). The netbook was not going to make the SMP deadline, so I moved the entire folder to an i7, folded it to 98% and moved it back to complete and send. It worked perfectly and is now back on the uniprocessor jobs.
 
I know it will work, I just don't know if it is 'allowed'.
There are reasons why certain WUs if not most of them should be processed to completion in the same system. Something about performance consistency that was posted recently. In certain cases (GPU), I've even seen results rejected. I think the answer would probably be no and would like further verification.
________________________________________________

With regards to the shortfall itself and the topic concerned, I think whenever this happens (and it will happen again and again so let's all of us get used to it) we should not point fingers at any hardware 'groups' within the community because all this does in the end is cause more friction than there already exists. If Sandy Bridge is responsible for the drought then so be it.
 
I blame the influx of overclocked 2600k's..

I've just been dealt a P6063 running around 5k ppd, I feel like i've been put on the naughtly step.

i hope your BigAdv rig pulls more than 5k ppd on a P6063....my Q9450 pulls a bit more D than that with that unit.....
 
Without obtaining a unit not designed for the system, is it frowned upon to move a -bigadv unit from one machine to another faster machine?
EG: SR-2 gets a p6701 and i7-920 gets a p6900. Can I pause/swap the jobs? No GPU on either system.

Sneakernetting has always been frowned upon by PG, there haven't been any threads on it in a while though, a quick search over at FF showed lots of conflicting advice.

It is possible but don't go crying if you only get base points or you trash your WU

This probably sums it up:-oops i lost my bonus points
 
Last edited:
If everyone is folding for the science and not points/monetary gains, why do you need to switch WU from machine to machine??

Just wondering??
 
Sneakernetting has always been frowned upon by PG, there haven't been any threads on it in a while though, a quick search over at FF showed lots of conflicting advice.

It is possible but don't go crying if you only get base points or you trash your WU

This probably sums it up:-oops i lost my bonus points

Yeah, I tried doing that once back in the BigAdv Drought of 2010 when we were all inundated with 6701's. It doesn't work.
 
I have taken my farm offline for some maintenence, but the last wu I pulled on the bigadv box was a 6900 and that was 3 days ago. Should be coming back online at the end of this week sometime, so hopefully there will be some more bigadv and the shortage will be short lived.
 
Thanks for the insight 404, Apollo, Nathan and Aix. I will scrap that idea.
 
If everyone is folding for the science and not points/monetary gains, why do you need to switch WU from machine to machine??

Just wondering??

KMac had a good reason initially - a machine got a WU that it could not complete in the time limit (the Atom), so he moved it to a machine that could. The alternative would have been to scrap the WU. I am not convinced that "sneakernetting" is always bad. I had a similar situation a while ago - something to do with an extended downtime for a slower machine that would have made it miss the WU deadline, so I stuck the unit on a faster machine to meet the deadline. When the alternative is to lose the unit, and you are willing to take the time to do it, I can't see it being an issue.

The problem is, that was NOT why the question was posed in this case. It was to get more points in times when bigadv WUs are in short supply. That is not a good reason to do it.
 
Just to clarify, I asked if it should be done or not because I figured it was in the darker part of the gray area.
I have never transferred a bigadv unit nor dumped a WU. My projects and times are all legit; I fold 'em as I get 'em.
HFM.JPG
 
I don't get why you guys are so against this? I did not see any post by PG condemning sneakernetting, it's the same method as running folding on a machine without internet/proxy (you do need to create a reg file).

If everyone is folding for the science and not points/monetary gains, why do you need to switch WU from machine to machine??
You actually get more performance by fully stressing the bandwidth, not just points. Also faster return rate for bigadv which are on a schedule..

I dunno... it's not worth messing around with sneakernetting 4-core i7 and hex i7, but if you know what you're doing, switching around 6701 with P6900 on sr-2 vs 4-core i7, seems logical.
 
Yeah, folding1 has been crunching nothing but 6701's since yesterday. I guess bigadv work units are in short supply again, although we shouldn't be upset since 6701's are doing some really nice science.

Do we know yet what the 6900's are doing?
 
Well this mini-drought is a big surprise to say the least. Given that the 6900 release meant there was a flood of bigadv for the last 2 months, I would have expected a backlog of other projects to have built up, given that 6900s averaged 56% of all bigadv.

I don't think this is due to Sandy Bridge, because the mix of units has changed recently, after being very consistent for a while. 6900s have dropped off, 2684s and 2692s are up.

Another thing of note is project 2692 ~quadrupling in frequency. This gem of a bigadv used to be consistently the fastest of them all, but lately has been a bit slower. It was also the rarest by a long way, (thus lowest priority?) but has been given a boost recently - of the 10 that I have folded since the 6900 came out 64 days ago, no less than 7 have been in the last 2 weeks, and 5 of those in the last week.

So my reading of the tea leaves is that we might have a bit of a drought until 2689 comes out, or one of the other projects gets a rev. Poor buggers must be swimming in a sea of 6900 data.

Last 64 days:

Unit WU
6900 126 56%
2685 28 13%
2684 31 14%
2686 27 12%
2692 12 5%

Total 224

Last 9 days:

Unit WU
6900 9 33%
2685 2 7%
2684 7 26%
2686 4 15%
2692 5 19%

Total 27
 
So I'm new to the bigadv(enture?) and just got a 6900 on my i7 860. What kind of TOF do I need to make the deadline for this unit? Under 60 min? 50 min? I trying to see if it will run bigadv at current clock (3.8 GHz). Also, does anyone know how this will compare to the worst bigadv so I can try to see if it will be able to handle those as well?
 
2684 is by far the slowest unit, and the only one you have to worry about really. If you can do that one comfortably in the deadline, you are good.

Use Musky's benchmark here
 
i hope your BigAdv rig pulls more than 5k ppd on a P6063....my Q9450 pulls a bit more D than that with that unit.....

Thanks, I thought it didn't seem right (and the last bigadv slowed to a crawl at the end). Just checked the bios and those damn power quoto's were enabled!

Turned them off (well turned them up) and it is now going 4 times faster, result! :eek:
 
So I'm new to the bigadv(enture?) and just got a 6900 on my i7 860. What kind of TOF do I need to make the deadline for this unit? Under 60 min? 50 min? I trying to see if it will run bigadv at current clock (3.8 GHz). Also, does anyone know how this will compare to the worst bigadv so I can try to see if it will be able to handle those as well?

You want to keep in mind as MIBW said, that being able to complete 2684's is your biggest concern. Depending on your internet connection, you'll also want to make sure there is enough time for it to get uploaded.

My i7 930@3.46ghz is able to do a 6900 in 35-36 minutes, and a 2684 in 51-52 minutes. This is also another good bigadv calculator you can use.

http://www.linuxforge.net/bonuscalc.php

If you can keep a 2684 at under 55-56 minutes, you should be able to just barely sneak in under the 4 day deadline.
 
Just switched over the 920 a couple days ago, in which time I've had 2x 6900 and a 2684. Once it finishes sucking on that (should be tomorrow sometime), I'll post what I get next.
 
SR-2 still has 12 hours on the P2686. My Sig Rig i7 has about a day left on its P2686. My second i7 will NOT pickup a Big Adv for the life of it :(
 
I can echo this. For the last 2 days I've went big > small > big > small. :D
(6900....6701....6900...now a 6058)
 
Well Hex is chewing on a 6701. Looks like ~7hr from start to finish, not too bad.
 
I think we are also running the "bottom of the barrel" units right now, at least for 6900s. I am seeing slower frame time on machines that have been running 6900s since they came out, I had two reboots last night from 2 machines that haven't had an issue in months, and I am running one now that every so often has a frame that take 3x longer to complete than normal. The good news is, at least they are bigadv units...
 
Back
Top