@runs2far, mow all you want. Not gonna hurt my feels
I barely out produce you when running bigadv, but it will be interesting/fun to catch you after one or two weeks of sub 100k ppd on my account.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
@runs2far, mow all you want. Not gonna hurt my feels
Upcoming changes to bigadv threshold
by kasson » Tue Dec 17, 2013 8:43 am
We have a policy of periodically re-evaluating the bigadv program, including the threshold required to run bigadv projects.
It is the intent of bigadv to match large and resource-intensive work units with some of the most powerful machines used by FAH donors. This "most powerful" line naturally advances with computing power. To date, bigadv has been a CPU-based program, and with increasing numbers of CPU cores and power of those cores, we have decided to lay out a roadmap of bigadv threshold changes for the next several months.
Feb 17 (two months from today): bigadv threshold will become 24 cores
Apr 17 (four months from today): bigadv threshold will become 32 cores
We want to give advance notice of these changes, and we recognize that change is not always welcome or comfortable. We should also emphasize that the science performed by donor machines is valuable in all parts of the FAH project, and part of the change in bigadv threshold is because we would like to encourage moderately powerful machines to help boost the capabilities of non-bigadv SMP projects where we do a lot of this science.
We also recognize that core count is not the most robust metric of machine capability, but given our current infrastructure it is the most straightforward surrogate to evaluate.
We have a policy of periodically re-evaluating the bigadv program, including the threshold required to run bigadv projects.
It is the intent of bigadv to match large and resource-intensive work units with some of the most powerful machines used by FAH donors. This "most powerful" line naturally advances with computing power. To date, bigadv has been a CPU-based program, and with increasing numbers of CPU cores and power of those cores, we have decided to lay out a roadmap of bigadv threshold changes for the next several months.
Feb 17 (two months from today): bigadv threshold will become 24 cores
Apr 17 (four months from today): bigadv threshold will become 32 cores
We want to give advance notice of these changes, and we recognize that change is not always welcome or comfortable. We should also emphasize that the science performed by donor machines is valuable in all parts of the FAH project, and part of the change in bigadv threshold is because we would like to encourage moderately powerful machines to help boost the capabilities of non-bigadv SMP projects where we do a lot of this science.
. And lets face it Bigadv was and is designed for the most powerful machines and unfortunately most of the 2P rigs do not fall into that class.
Just curious, what would you consider to be a "powerful" 2p machine?
Just curious, what would you consider to be a "powerful" 2p machine?
one with two additional processors...
One with 2 E5-2695v2 in it?
Nathion_P, I myself find many 1P machines powerful, what I believe is a powerful machine does not matter, what Stanford determines is a powerful machine does matter. And in reality they have not made that determination yet since they have not given a completion time deadline . I do know that if was myself building right now I would not be building a 2P just from what they have said about the core count.
You under spec'd your machine - 2697v2
I blame the sales people.
It appears to me many are reading more into this than is intended, at least that is the way it seems to me and many have gone way out of line in providing answers to something that was never asked for by Stanford. What is happening is nothing more than human emotional reaction generated from an incomplete statement. I do not see anywhere that it says there is a huge backlog or that they want bigadv capable rigs to switch to smp at this time.
We have a policy of periodically re-evaluating the bigadv program, including the threshold required to run bigadv projects.
It is the intent of bigadv to match large and resource-intensive work units with some of the most powerful machines used by FAH donors. This "most powerful" line naturally advances with computing power. To date, bigadv has been a CPU-based program, and with increasing numbers of CPU cores and power of those cores, we have decided to lay out a roadmap of bigadv threshold changes for the next several months.
Ummm by using only a part of the statement made by Kasson a person can manipulate it to mean anything they want to the very first part of the statement is very important also especially knowing the history of the bigadv program
Nathan_P They would be better off making a simple statement such as:-
From such and such a date BA machines will need to be 4p 2011, 1567 or G34
After this announcement I have turned off my SR-2 rig. Why? Yes because PG has made it into scrap, as they did with my 6 x 2600K rigs, my 2 x 980x rigs, and it is under two years ago. And they certainly will do the same with my 5 x 4P rig sometime in the near future. I therefore think it is direct rudely by Bruce to ask me to give up BA and folding standard SMP for an indefinite period of time, without doing anything about the bonus system for SMP. One can not avoid the fact that the most important for us (me and my team) is still to get the most of PPD for my electricity bill.Upcoming changes to bigadv threshold
by kasson » Tue Dec 17, 2013 8:43 am
We have a policy of periodically re-evaluating the bigadv program, including the threshold required to run bigadv projects.
It is the intent of bigadv to match large and resource-intensive work units with some of the most powerful machines used by FAH donors. This "most powerful" line naturally advances with computing power. To date, bigadv has been a CPU-based program, and with increasing numbers of CPU cores and power of those cores, we have decided to lay out a roadmap of bigadv threshold changes for the next several months.
Feb 17 (two months from today): bigadv threshold will become 24 cores
Apr 17 (four months from today): bigadv threshold will become 32 cores
After this announcement I have turned off my SR-2 rig. Why? Yes because PG has made it into scrap, as they did with my 6 x 2600K rigs, my 2 x 980x rigs, and it is under two years ago. And they certainly will do the same with my 5 x 4P rig sometime in the near future. I therefore think it is direct rudely by Bruce to ask me to give up BA and folding standard SMP for an indefinite period of time, without doing anything about the bonus system for SMP. One can not avoid the fact that the most important for us (me and my team) is still to get the most of PPD for my electricity bill.
I also wondered about if bruce and 7im folds themselves, and I find that both of them have been or is very close to the zero PPD line in the stats.
For some time now I have pondered whether I should have my servers doing anything other than work for f@h, but I have not decided yet! Well, now I can sleep good to night.
And from my past experience of asking questions to PG you won't either. The only answers that you'll get will be from the usual group (apologist) for PG and the FF and most of that will be in the form of berating.I asked right up front @FF for an answer from PG
OK we are parsing words here.
Can someone from PG define what boost the capabilities means exactly Please?
And make clear, once and for all, is there a need for more CPUs, to be directed at getting SMP WUs done, because of some "perceived" backlog that may or may not exist?
I have yet to receive an answer.
I believe Grandpa's point was not that demand was not indicated but that there was no request to switchshrae said:rationale for arbitrary core restriction on BA is to get more SMP work done
That's what I practically asked for (to provide new preferred deadlines) -- didn't get very practicalThey would be better off making a simple statement such as:-
From such and such a date BA machines will need to be 4p 2011, 1567 or G34
Based on the stats from EOC with that UserID, then Bruce has not Folded a single WU in over 3yrs. If that is accurate, I'd question why he is so active in the FF. Seems odd for someone that has that kind of activity talking to Folders would at least be Folding something in 3yrs time wouldn't it? Maybe he has moved on and has another Folding ID?bruce may not be a big folder like some. he folds for The Genome Collective which is one of the earliest teams in Folding. He folds as b.borden.
Or it's just a typo and he fold under Borden.b; same group as mentioned above and a pure guess from my side.Based on the stats from EOC with that UserID, then Bruce has not Folded a single WU in over 3yrs. If that is accurate, I'd question why he is so active in the FF. Seems odd for someone that has that kind of activity talking to Folders would at least be Folding something in 3yrs time wouldn't it? Maybe he has moved on and has another Folding ID?
Or it's just a typo and he fold under Borden.b; same group as mentioned above and a pure guess from my side.
What sends me spinning, is that second increase in BA cores required (and deadlines according to Kasson), in April. Just two months after the first increase!
No need to do that Adak 7im wrote a letter with good solutions to all the problems.
They do not need a letter. All they have to do is read that thread, plus all the other threads in the teams forums.
You can be sure they do read them. They post on them so I am sure they have a good idea how people fee
Happy new year everyone.l.
No need to do that Adak 7im wrote a letter with good solutions to all the problems.
They do not need a letter. All they have to do is read that thread, plus all the other threads in the teams forums.
You can be sure they do read them. They post on them so I am sure they have a good idea how people fee
Happy new year everyone.l.