amd bigadv prerequistes

[dugdiamond]

six cores

overclocked to atleast 3.8GHz or above

completion of 10 consequecutive "bonused" WUs (without fails)

(extra credit will only be given after these 10 have been done)

client GUIs (HFM and FAH Tracker) report your PPD assuming your have met the above criteria, even if you havent done the 10 yet, so patience is needed.

 

[riotcity76]

Keep in mind with all smp and bigadv WUs you need to maintain an 80% completion rate to keep getting the bonus points.

 

[kilobravo]

When i started,maybe 7-10 days before i got the bonuspoints.

 

[hmmblah]

Is 6 threads at 3.8GHz enough? Doesn't stanford recommend at least 8 threads? Correct me if I'm wrong, but the quicker you turn in a bigadv WU (so the further from its deadline) the more bonus points you will get.

 

[yuri04]

There have been many arguments on the foldingforum about this, basically Stanford only allows -bigadv to be run on 8 or more cores,

i7's work because the OS reports these as 8 cores (with hyper threading enabled of course), so there is no problem in using the -bigadv flag for the i7's even though these are just quad cores (which aren't officially allowed to run -bigadv). As these processors have no issue of making the deadlines (if overclocked) Stanford lets it slide.

However the hexcores from AMD are also capable of making the deadline(again, when overclocked), they however get reported by the OS as hexcores, so there is no support for running -bigadv. There is however a workaround for it, not sure what it is exactly but it involves running a VM using Linux.

And indeed the quicker the WU is returned the higher the Quick Return Bonus is.

 

[hmmblah]

There have been many arguments on the foldingforum about this, basically Stanford only allows -bigadv to be run on 8 or more cores,

i7's work because the OS reports these as 8 cores (with hyper threading enabled of course), so there is no problem in using the -bigadv flag for the i7's even though these are just quad cores (which aren't officially allowed to run -bigadv). As these processors have no issue of making the deadlines (if overclocked) Stanford lets it slide.

However the hexcores from AMD are also capable of making the deadline(again, when overclocked), they however get reported by the OS as hexcores, so there is no support for running -bigadv. There is however a workaround for it, not sure what it is exactly but it involves running a VM using Linux.

And indeed the quicker the WU is returned the higher the Quick Return Bonus is.

Ah, thanks for that. Any idea what kind of PPD a hexcore AMD gets? Are they comparable to i7 at all?

 

[kilobravo]

Ah, thanks for that. Any idea what kind of PPD a hexcore AMD gets? Are they comparable to i7 at all?

Yes with normal wu`s,not big-adv, they are equal`s at 4.0ghz.

My girlfriends rig runs wu6072 at 15k ppd @ 3.85ghz.But the 1090t need more finetuning in bios to run f@h oc`ed than i7-9xx.

 

[FoodStampz]

Yes with normal wu`s,not big-adv, they are equal`s at 4.0ghz.

My girlfriends rig runs wu6072 at 15k ppd @ 3.85ghz.But the 1090t need more finetuning in bios to run f@h oc`ed than i7-9xx.

Do you think the HT Link plays an important role? My mobo doesn't seem to like anything past 2200.

 

[kilobravo]

Do you think the HT Link plays an important role? My mobo doesn't seem to like anything past 2200.

Yes,the ht-link need some extra volts,and 2200 becomes easily unstable folding.

2000 on HT is stable,but then again,anything over 3.8-3.9ghz is pointless at 2000 HT. There is no gain in ppd at 4.0 and 2000 HT