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

Into the gap

Folding OS


  • Total voters
    42
2x Opteron 4122 Socket C32 Quad Core @ 2.2ghz. These are the slowest/cheapest of the C32 chips. HFM.net is saying 36:10 TPF for 28315.5PPD. There is a lot of crap running in the bg with Ubuntu, so theres probably some room for improvement.
 
2x Opteron 4122 Socket C32 Quad Core @ 2.2ghz. These are the slowest/cheapest of the C32 chips. HFM.net is saying 36:10 TPF for 28315.5PPD. There is a lot of crap running in the bg with Ubuntu, so theres probably some room for improvement.

given muskies erratic ppd on ubunutu I would say definitely...
 
given muskies erratic ppd on ubunutu I would say definitely...

He is already doing better than I was with Desktop - I always had one core unloaded, even back when I was running I7 920s and version 9.10. That is why I used 9.04 Desktop exclusively on my dedicated folders when the A2 cores was around. It would load all cores on each machine, would install from a USB stick (Server won't), and was easy to set up well enought to fold and monitor.
 
He is already doing better than I was with Desktop - I always had one core unloaded, even back when I was running I7 920s and version 9.10. That is why I used 9.04 Desktop exclusively on my dedicated folders when the A2 cores was around. It would load all cores on each machine, would install from a USB stick (Server won't), and was easy to set up well enought to fold and monitor.

wow... so even when you were getting same frame time as windows you were having one core unloaded?
 
wow... so even when you were getting same frame time as windows you were having one core unloaded?

Yep. top bounces around 2300% on a 24 core machine. When it was just short of 2400%, I was seeing a minute and a half lower frame times. The one machine I have left on Linux is back to dropping a core and folding slower than Windows.
 
I am back to one box running Linux - switched the second one back to Windows this morning after a failed 6901 and three straight painfully slow regular A3 units.

Sorry to go OT - but am I right in saying the A5 core is being fed either 6901's or SMP - but not 2684/2685/2686/2692/6900s.

Wondering if the old projects will all get new numbers...
 
Sorry to go OT - but am I right in saying the A5 core is being fed either 6901's or SMP - but not 2684/2685/2686/2692/6900s.

Wondering if the old projects will all get new numbers...

I don't think we have any SMP units that use the A5 core. The 6.34 client can and does run the A3 core for older bigadv units and all regular SMP units from what i have seen.
 
Sorry to go OT - but am I right in saying the A5 core is being fed either 6901's or SMP - but not 2684/2685/2686/2692/6900s.

Wondering if the old projects will all get new numbers...
Projects aren't directly moved from one core to another. All of the projects using the A5 core are new, and all of the old A3 projects will continue to run on the A3 core until they are discontinued.
 
Projects aren't directly moved from one core to another. All of the projects using the A5 core are new, and all of the old A3 projects will continue to run on the A3 core until they are discontinued.

6901 is the same as 6900... sorry but the first unit is a test unit...
 
6901 is the same as 6900... sorry but the first unit is a test unit...
Yes, it's the same, but the project number is different to signify the fact that it runs on a different core. We will never see P2684 or 2685 running on the A5 core. If they do port over those projects, they will be given new numbers as well.
 
Yes, it's the same, but the project number is different to signify the fact that it runs on a different core. We will never see P2684 or 2685 running on the A5 core. If they do port over those projects, they will be given new numbers as well.

and hopefully corrected ppd lol
 
Doubt that will happen unfortunately.

well... I will be sure offer input on that note...

supposedly thats one job of the beta team... to give suggestions on what credit a poor performing wu should be
 
Running Linux RHEL and it is loading 6300% but showing a load of 64.

top - 09:35:39 up 12 days, 4 min, 2 users, load average: 64.09, 64.02, 64.01
Tasks: 797 total, 1 running, 796 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0%us, 25.5%sy, 74.4%ni, 0.1%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 65993276k total, 18030224k used, 47963052k free, 359476k buffers
Swap: 8377856k total, 0k used, 8377856k free, 14392284k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
22208 root 34 19 5594m 2.4g 5640 S 6387.9 3.9 21163:39 FahCore_a5.exe
2.6.18-238.1.1.el5 #1 SMP Tue Jan 4 13:32:19 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 5.6 (Tikanga)

[16:43:38] Completed 87500 out of 250000 steps (35%)
[16:51:36] Completed 90000 out of 250000 steps (36%)
[16:59:21] Completed 92500 out of 250000 steps (37%)
[17:07:21] Completed 95000 out of 250000 steps (38%)
[17:15:32] Completed 97500 out of 250000 steps (39%)
 
Last edited:
Running Linux RHEL and it is loading 6300% but showing a load of 64.

top - 09:35:39 up 12 days, 4 min, 2 users, load average: 64.09, 64.02, 64.01
Tasks: 797 total, 1 running, 796 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0%us, 25.5%sy, 74.4%ni, 0.1%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 65993276k total, 18030224k used, 47963052k free, 359476k buffers
Swap: 8377856k total, 0k used, 8377856k free, 14392284k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
22208 root 34 19 5594m 2.4g 5640 S 6387.9 3.9 21163:39 FahCore_a5.exe
2.6.18-238.1.1.el5 #1 SMP Tue Jan 4 13:32:19 EST 2011 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 5.6 (Tikanga)

[16:43:38] Completed 87500 out of 250000 steps (35%)
[16:51:36] Completed 90000 out of 250000 steps (36%)
[16:59:21] Completed 92500 out of 250000 steps (37%)
[17:07:21] Completed 95000 out of 250000 steps (38%)
[17:15:32] Completed 97500 out of 250000 steps (39%)

and you're using the -smp -bigadv flag?

You may have to specify -smp xx -bigadv where xx = number of threads you want to load. For example on my dual quad w/HT thats 16 threads so that would be -smp 16 -bigadv -verbosity 9 &
 
I didn't tell it -smp 64 just -smp and it loads 64 threads.

I went ahead and specified it and fired it back up.
./fah6 -smp 64 -bigadv -forceasm

[17:58:46] - Calling './FahCore_a5.exe -dir work/ -nice 19 -suffix 06 -np 64 -checkpoint 15 -forceasm -verbose -lifeline 23313 -version 634'

That seems to have helped. It is running about the same between 6291 and 6400. On this box it doesn't really matter.
 
on a top session (if you have a large enough window) you can hit the number 1 and it'll give you the exact idle/busy state of each core/thread.

You should show up as all threads active when forcing it that way
 
I need a bigger monitor. :)

Only 56 lines in my terminal at full screen.

Ok zoomed out and got the following
So at that moment CPU3 was idle. It does jump around.

top - 11:11:51 up 12 days, 1:40, 2 users, load average: 64.00, 64.00, 63.91
Tasks: 797 total, 1 running, 796 sleeping, 0 stopped, 0 zombie
Cpu0 : 0.0%us, 25.1%sy, 74.9%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu1 : 0.0%us, 25.5%sy, 74.5%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu2 : 0.0%us, 26.4%sy, 73.6%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu3 : 0.3%us, 1.0%sy, 0.0%ni, 98.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu4 : 0.0%us, 24.8%sy, 75.2%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu5 : 0.0%us, 27.8%sy, 72.2%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu6 : 0.0%us, 39.7%sy, 60.3%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu7 : 0.0%us, 27.6%sy, 72.4%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu8 : 0.0%us, 27.5%sy, 72.5%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu9 : 0.0%us, 26.8%sy, 73.2%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu10 : 0.0%us, 26.8%sy, 73.2%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu11 : 0.0%us, 25.7%sy, 74.3%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu12 : 0.0%us, 40.1%sy, 59.9%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu13 : 0.0%us, 28.4%sy, 71.6%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu14 : 0.0%us, 27.5%sy, 72.5%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu15 : 0.0%us, 27.5%sy, 72.5%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu16 : 0.0%us, 27.5%sy, 72.5%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu17 : 0.0%us, 25.9%sy, 74.1%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu18 : 0.0%us, 26.8%sy, 73.2%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu19 : 0.0%us, 28.5%sy, 71.5%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu20 : 0.0%us, 4.6%sy, 95.4%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu21 : 0.0%us, 27.1%sy, 72.9%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu22 : 0.0%us, 38.6%sy, 61.4%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu23 : 0.0%us, 26.7%sy, 73.3%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu24 : 0.0%us, 39.9%sy, 60.1%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu25 : 0.0%us, 27.2%sy, 72.8%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu26 : 0.0%us, 26.8%sy, 73.2%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu27 : 0.0%us, 28.1%sy, 71.9%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu28 : 0.0%us, 28.1%sy, 71.9%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu29 : 0.0%us, 26.2%sy, 73.8%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu30 : 0.0%us, 26.2%sy, 73.8%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu31 : 0.0%us, 26.8%sy, 73.2%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu32 : 0.0%us, 21.1%sy, 78.9%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu33 : 0.0%us, 32.5%sy, 67.5%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu34 : 0.0%us, 39.7%sy, 60.3%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu35 : 0.0%us, 38.3%sy, 60.7%ni, 1.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu36 : 0.0%us, 27.7%sy, 72.3%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu37 : 0.0%us, 27.8%sy, 72.2%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu38 : 0.0%us, 26.7%sy, 73.3%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu39 : 0.0%us, 26.5%sy, 73.5%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu40 : 0.0%us, 27.4%sy, 72.6%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu41 : 0.0%us, 28.2%sy, 71.8%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu42 : 0.0%us, 25.7%sy, 74.3%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu43 : 0.0%us, 40.1%sy, 59.9%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu44 : 0.0%us, 26.2%sy, 73.8%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu45 : 0.0%us, 24.8%sy, 75.2%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu46 : 0.0%us, 26.2%sy, 73.8%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu47 : 0.0%us, 28.1%sy, 71.9%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu48 : 0.0%us, 23.9%sy, 76.1%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu49 : 0.0%us, 27.2%sy, 72.8%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu50 : 0.0%us, 27.7%sy, 71.9%ni, 0.3%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu51 : 0.0%us, 38.7%sy, 61.3%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu52 : 0.0%us, 26.7%sy, 73.3%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu53 : 0.0%us, 27.8%sy, 72.2%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu54 : 0.0%us, 24.4%sy, 75.2%ni, 0.3%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu55 : 0.0%us, 27.8%sy, 72.2%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu56 : 0.0%us, 27.8%sy, 72.2%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu57 : 0.0%us, 27.8%sy, 72.2%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu58 : 0.0%us, 27.4%sy, 72.6%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu59 : 0.0%us, 27.7%sy, 72.3%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu60 : 0.0%us, 26.7%sy, 73.3%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu61 : 0.0%us, 25.1%sy, 74.9%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu62 : 0.0%us, 26.5%sy, 73.5%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
Cpu63 : 0.0%us, 25.1%sy, 74.9%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
 
how much ram do you have.... you may not have enough to keep 64 threads busy...

check foldingforum for >32 thread issues and workarounds...
 
I'm definitely interested in seeing more data regarding bigadv on linux. If we see an increase in ppd, I could see realistically switching all my bigadv boxens over to linux.
 
well... I will see about making some data points on thursday for different distros...

I was not expecting a5 to get kicked out the door so fast... and had to work at getting all of my boxes switched over...

for the other part... I am less the 2.8ghz xeon i7 and one 1155 D0 mystery chip in need of a decode...
 
Back
Top