new VJ blog post: about -bigadv16

So I just blew 2 years of farming money on a 4P rig that could take a nearly 70% reduction in output? If they want these units back so quickly, and they expect people to spend thousands of dollars to do that for them (lets face it, a 4p is no 8800GT) to get them these units rather than any normal unit that any normal folder can do, why would they piss in our faces, cuz this is a bit beyond just spitting

Now I hope it's just late at night and I'm reading something wrong here, but I can put out more WU's while getting more points if I fold standard SMP, but I'll put out less WU's and get less points if I fold Stanford's magical units? Wasnt the whole point of bigadv to make people want to spend thousands in order to get these units back fast? Maybe its just me but Stanford seems to have taken the want out of it.

I know it's all for science, and at the end of the day my 4P is still going to run hard for this team and for a cure, but I hope I'm missing something cuz right now I'm actually pretty pissed off, not just annoyed.
 
Vaulter98c said:
So I just blew 2 years of farming money on a 4P rig that could take a nearly 70% reduction in output? If they want these units back so quickly, and they expect people to spend thousands of dollars to do that for them (lets face it, a 4p is no 8800GT) to get them these units rather than any normal unit that any normal folder can do, why would they piss in our faces, cuz this is a bit beyond just spitting

Now I hope it's just late at night and I'm reading something wrong here, but I can put out more WU's while getting more points if I fold standard SMP, but I'll put out less WU's and get less points if I fold Stanford's magical units? Wasnt the whole point of bigadv to make people want to spend thousands in order to get these units back fast? Maybe its just me but Stanford seems to have taken the want out of it.

I know it's all for science, and at the end of the day my 4P is still going to run hard for this team and for a cure, but I hope I'm missing something cuz right now I'm actually pretty pissed off, not just annoyed.
Click to expand...

-bigbeta bro, just run -bigadv any you wont get them. The 8P had run 2 clone 0 gen 0, so the pojects are brand spanking new. They are not meant for normal consumption yet, hence bigbeta (BETA). The points reflect very little performance data that PG has on these units.

They are a bit faster than 6903.
 
To prevent a serious screw job once again to cpu folders are they going to raise the QRB points at the same time they reduce the deadline? Seems this would be a good way to do things if they want people to continue to invest large sums of money in 4p systems that can meet their deadlines.
 
DooKey said:
To prevent a serious screw job once again to cpu folders are they going to raise the QRB points at the same time they reduce the deadline? Seems this would be a good way to do things if they want people to continue to invest large sums of money in 4p systems that can meet their deadlines.
Click to expand...

Just as much has been said in the beta forums and I am also talking about it in the DAB.

It is a brand new unit and they are still trying to figure out how to hash out the QRB.

They are getting the data points they need from us (oddly most everyone I've seen post about it is a member of [H] or is a familiar face here :D)
 
That's because beta testing is [H]ard :D
 
They are aware of the problem and we should know what they plan to do before too long.
 
Grandpa_01 said:
They are aware of the problem and we should know what they plan to do before too long.
Click to expand...

Hopefully that includes upgrading the benchmark machine to something that can actually run a -bigadv WU without the core hack:rolleyes:
 
Ah, beta. See, it was too late and I missed 4 simple letters. Feel much better now lol, although I do hope that they don't let this go through without change, but atleast we know we got K fighting for us with them. I mean hell, if anything they should score a tad higher than current units since they are now going out to much fewer people

Thanks for clearing that up!
 
The WU is pretty damn close to 6903 (a bit faster) so modeling the points after it would be good.
Approximately 2.6% faster on my 8P, and 1.7% on my 2P. If the points and curve were adjusted similar to the 6903, my 2P would get 105K PPD with 8101 TPF (103K with 6903 TPF), and the 8P would get 534K PPD 8101 TPF (514K PPD 6903 TPF) utilizing the same bonus points and curve.

This would give incentive for people to test and run these units, and after a month or so they could do like the last -bigbeta introduction and they could adjust it back a bit to be in line with the previous points reward for -bigbigadv.

However the 2P 8C 16T @ 3.2Ghz WILL NOT MAKE DEADLINES, it misses the prefered deadline by 15.47% not factoring upload time. I would say a good 20-25% peformance increase over this would be the minimum to comfortably make deadlines depending on upload and other factors. So most likely a 3Ghz sandy octacore will not be making deadlines on this new unit as well. These units have appropriate deadlines to prevent almost any single CPU from running them. Mission accomplished PG!

Edit: Therefore these units will have a minumum hardware of an SR2 with dual quads @ 4.0Ghz, or about 2.67Ghz hexes. I think pande group got the deadline right.
 
Last edited:
Untitledone said:
-bigbeta bro, just run -bigadv any you wont get them. The 8P had run 2 clone 0 gen 0, so the pojects are brand spanking new. They are not meant for normal consumption yet, hence bigbeta (BETA). The points reflect very little performance data that PG has on these units.

They are a bit faster than 6903.
Click to expand...

FYI: i tried -bigadv - smp 16 and still got p8101
 
Untitledone said:
However the 2P 8C 16T @ 3.2Ghz WILL NOT MAKE DEADLINES, it misses the prefered deadline by 15.47% not factoring upload time. I would say a good 20-25% peformance increase over this would be the minimum to comfortably make deadlines depending on upload and other factors. So most likely a 3Ghz sandy octacore will not be making deadlines on this new unit as well. These units have appropriate deadlines to prevent almost any single CPU from running them. Mission accomplished PG!

Edit: Therefore these units will have a minumum hardware of an SR2 with dual quads @ 4.0Ghz, or about 2.67Ghz hexes. I think pande group got the deadline right.
Click to expand...

My L5640 rig finishes its current WU in 18 hours, i'll let it run one and see how I get on and let you all know.
 
I have two of the new 8101's pulling a 21:03 tpf on the dual dodeca at 3ghz and 23:44 on the dual hex sr-2 at 3.6ghz. However, HFM doesn't give me ppd and downloading project lists doesn't correct. I'm assuming there is a server change I need to make in the HFM config?
 
no, psummary has not been updated with the unit

25:20 avg TPF on SR2 with 2x hex @ 3.33 GHz
 
My 32 core 2ghz is getting 72k ppd, 22min per frame on a P8101 R1C5G0, a P7138 gets 99k ppd on this rig.
 
R-Type said:
I have two of the new 8101's pulling a 21:03 tpf on the dual dodeca at 3ghz and 23:44 on the dual hex sr-2 at 3.6ghz. However, HFM doesn't give me ppd and downloading project lists doesn't correct. I'm assuming there is a server change I need to make in the HFM config?
Click to expand...

in the HFM config, where it asks you for the project summary address, change the part that says psummary.html to psummaryC.html and you should be OK
 
Nathan_P said:
in the HFM config, where it asks you for the project summary address, change the part that says psummary.html to psummaryC.html and you should be OK
Click to expand...

They weren't on psummaryC last night or this morning. Are they now?
 
These new P8101 are a joke . Twice less points than standard bigadv. :eek:

Hope that they will change this as soon as possible .:(
 
More than twice, it's a frigging slaughter house for anyone who trys to be the worlds greatest. But, to be fair, they have pointed it out that it's still in beta, just barely at that. Hopefully our team reps and the other leading teams reps can get some justice for us. Those reps are from the best teams in the world, and they represent a majority of the highest spenders, they realize how an incentive program like bigadv is supposed to work, they realize the thousands of dollars we've put into these rigs, they realize what will happen if things don't change.

That being said, it's still in beta, and we've got the best of the best going to bat for us with Stanford, so I think it's only fair to give them a chance and not jump all over this quite yet. We can talk about how it's ppd sucks but we have to realize that it's still ONLY a beta. Save the serious talk until it gets more permanent.
 
Jeanjean said:
These new P8101 are a joke . Twice less points than standard bigadv. :eek:

Hope that they will change this as soon as possible .:(
Click to expand...

Yuck. Looks like the sadistic bastard who designed the 2684's is still on the team. :p
 
Vaulter98c said:
That being said, it's still in beta, and we've got the best of the best going to bat for us with Stanford, so I think it's only fair to give them a chance and not jump all over this quite yet. We can talk about how it's ppd sucks but we have to realize that it's still ONLY a beta. Save the serious talk until it gets more permanent.
Click to expand...

Right....it wasn't even a close to accurate... lol... it might help if they benchmark on the class of machine they want these units to run on.

That said... it is in beta....and serves as a reminder that those not in beta should not run the beta... and if they do they cant complain about the ppd, there is a nice disclaimer apon entering beta about that.
 
Patriot said:
Right....it wasn't even a close to accurate... lol... it might help if they benchmark on the class of machine they want these units to run on.

That said... it is in beta....and serves as a reminder that those not in beta should not run the beta... and if they do they cant complain about the ppd, there is a nice disclaimer apon entering beta about that.
Click to expand...

I had never changed flags from the original ba-12 debut, fixing now...

Heh, I'm getting higher ppd from my main box running SMP in Windows than the two dedicated boxen running 8101 in Linux. :eek:
 
Last edited:
Kasson has made or been involved in all of them as far as I can tell. At least he has been the contact on all of the bigadv WU's and he is the one that wrote the papers from there results.
 
Yeh, they are not fun..... and it seems if you have the -bigadv flag, you will get them.
 
jebo_4jc said:
I just got two of these bastards in a row
Click to expand...

Switched both dedicateds over to the -bigadv flag to keep the beta units at bay for the time being, hopefully they sort the points out before they go mainstream.
 
Grandpa_01 said:
Kasson has made or been involved in all of them as far as I can tell. At least he has been the contact on all of the bigadv WU's and he is the one that wrote the papers from there results.
Click to expand...

He is good on the research but hasn't a clue on the hardware... or atleast has not shown it.

Data points gents.... your not supposed to be getting them under bigadv but if you are let me know and also your tpf.

They want data points lets fill up the threads...
 
2P – 24 cores @ 3.0 ghz (magny cours), 2.2ghz northbridge
8101 20:35 = 79,766 ppd
6901 9:35 = 165,867 ppd
6903 23:17 = 235,738 ppd
6904 29:30 = 270,909 ppd

2P – 12 cores (24 logical) @ 3.6 ghz (westmere)
8101 23:41 = 65,427 ppd
6901 11:24 = 128,002 ppd
6903 26:01 = 199,791 ppd
6904 37:24 = 189,779 ppd

This is another area where the benchmark based unit allocation system would be a net benefit to the project. By stratifying work units into performance brackets, the guidelines for relative point expections becomes much simpler.
 
Last edited:
THIS IS FOR PATRIOT TO PRESENT TO THE BETA TEAM FOR HIS CONVENIENCE!!!

2P X5570 8C 16T @ 3.2Ghz
Project TPF PPD
P7146 01:50 46K
P6901 18:17 63K
P8101 39:50 23K
P6903 40:28 103K
P6904 59:51 93K

8P 8431 48C 48T 2.4Ghz
Project TPF PPD
P7148 00:42 196K
P6901 06:13 317K
P8101 13:30 117K
P6903 13:51 514K
P6904 18:37 540K
 
Last edited:
Untitledone said:
THIS IS FOR PATRIOT TO PRESENT TO THE BETA TEAM FOR HIS CONVENIENCE!!!

2P X5570 8C 16T @ 3.2Ghz
Project TPF
P7146 01:50
P6901 18:17
P8101 39:50
P6903 40:28
P6904 59:51

8P 8431 48C 48T 2.4Ghz
Project TPF
P7148 00:42
P6901 06:13
P6903 13:51
P6904 18:37
Click to expand...

AbP1c.png
 
R-Type said:
AbP1c.png
Click to expand...

Untitledone said:
THIS IS FOR PATRIOT TO PRESENT TO THE BETA TEAM FOR HIS CONVENIENCE!!!

2P X5570 8C 16T @ 3.2Ghz
Project TPF PPD
P7146 01:50 46K
P6901 18:17 63K
P8101 39:50 23K
P6903 40:28 103K
P6904 59:51 93K

8P 8431 48C 48T 2.4Ghz
Project TPF PPD
P7148 00:42 196K
P6901 06:13 317K
P8101 13:30 117K
P6903 13:51 514K
P6904 18:37 540K
Click to expand...

You happy now?
 
Last edited:
2P 6176SE P8101 R8 C0 G0 TPF 23:22

Ignore the bonus points on the P6903 R3 C14 G58, that was due to a power failure and the system being off for 12 hours.

Server5-SMP_20120209.png
 
2P L5640 @ 2.4Ghz inc Turbo.

P8101 R9 C0 G1. TPF 36.45
P6903 TPF 38:46
P6901 TPF 16:59

All under Linux, with BFS and the Kraken

For reference my windows box does P7141 in TPF 01:46.

Quick maths shows that you need a maximum TPF of 33:30 in order to allow enough time for upload @384kbps.

Anything less that 2.66Ghz on Westmere CPU's will not cut it and I suspect that even 2.66 (x5650) will be close
 
Nathan_P said:
2P L5640 @ 2.4Ghz inc Turbo.

P8101 R9 C0 G1. TPF 36.45
P6903 TPF 38:46
P6901 TPF 16:59

All under Linux, with BFS and the Kraken

For reference my windows box does P7141 in TPF 01:46.

Quick maths shows that you need a maximum TPF of 33:30 in order to allow enough time for upload @384kbps.

Anything less that 2.66Ghz on Westmere CPU's will not cut it and I suspect that even 2.66 (x5650) will be close
Click to expand...
Correct sir dual 2.53ghz hex barely miss the deadline...
 
You must log in or register to reply here.
Back
Top