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.
10e, I have to say that this rig fascinates me to the point of shopping for MC 12 cores...
Can you elaborate on what is not working properly on the benchmark utility?
This *should* be fixed with the next update of the core especially considering more people are starting to fold on rigs with more than 32 cores.It turns out the normal "-smp" switch in the SMP client defaults to maximum 32 cores if you don't set a number after it. This was indicated in Alpha754293's thread at www.foldingforum.org when he first tried out the 48 core 6174 box he has at work.
If I run the benchmark utility "stock" ie. using only the instructions provided and without any changes, it works fine but apparently only loads up the CPUs at 67%.
It turns out the normal "-smp" switch in the SMP client defaults to maximum 32 cores if you don't set a number after it. This was indicated in Alpha754293's thread at www.foldingforum.org when he first tried out the 48 core 6174 box he has at work.
So then I copy over a Folding@home-Win32-x86.exe binary from an SMP directory and run -configonly to change the client.cfg to -smp 48, and re-run, but then it gives strange stats.
A 2686 took either 27:40 to finish a frame, or finished 4 frames in 10:23, so something is strange.
I think in this scenario somehow it seems to run the "wrong unit" if that is possible. Ie. run a 6061 or 6701 instead of the chosen 2686 unit.
My next step is to try and just copy my client.cfg file from my regular folding client into the "data" directory and try using that.
If that works then I can print some solid numbers. I really wanna see what a 2684 does. If I get a TPF of 14:00 or lower I will be on cloud 9, as this means it really can finish any BigAdv work unit in a day or less.
If that works then I can print some solid numbers. I really wanna see what a 2684 does. If I get a TPF of 14:00 or lower I will be on cloud 9, as this means it really can finish any BigAdv work unit in a day or less.
Start over. After you unzip it, open the client.cfg file in Notepad. Somewhere in the cryptic string you will see "extra_parms=-smp". Change that to "extra_parms=-smp 48" and you should be set. If you want, I'll send you a new client.cfg file.
That was my hope as well, but of course I fell short with 26hrs on a 2684. But of course, your average will be well under 24hrs, given the prevalence of units since the 6900 release 3.5 weeks ago:
Unit WU
6900 53 56%
2685 19 20%
2684 10 11%
2686 10 11%
2692 2 2%
Total 94
I should not have asked you to prioritise the 2686, had I thought it through I should have said 6900, 2685, 2684 were the priorities. Sorry bout that chief.
Still thrilled someone has made a 2684 killer rig. We need to stop work on the benchmark immediately and write automated software to sneakernet all our 2684s to 10e for maximum team efficiency.
Ahhh time for beddy byes, that glass of red went straight to my head.![]()
This is the fun here, not the e-peen![]()
I often wonder if I had just settled for quick and dirty 4.0Ghz on all and left them in a room folding what my score would be by now.
Nothing better than groupthink optimisation.![]()
Excuse my trip down memory lane:-
It's funny. The last time a saw a computer with 48 processors (2x Sun e6800's in an active/ active failover pair), it took up two racks (not rack units, racks!). This is within the last decade, it's amazing how times have changed.
RIP Sun.
10e, what were your temps before the noctuas?
TPFs on P6900 R24, C15, G8 are down to 10:44 for 174K PPD.
Holy crap.