Guide For Running bigadv On Windows Natively (A3 Core)

The most demanding Projects are only available to a small percentage of very high-end servers.

Moderators: Site Moderators, PandeGroup

Guide For Running bigadv On Windows Natively (A3 Core)

Postby PantherX » Tue Jun 29, 2010 5:29 pm

UPDATE: Please note that from 16 January 2012, this Guide is no longer useful for folding bigadv WUs since the minimum CPU requirement has been increased from 8 CPUs to 16 CPUs.

  • Introduction:
Finally after a long wait, bigadv/extra-large WUs are now available on Windows Natively: (compiled from different posts in this forum)
kasson wrote:We've turned off bigadv on linux for the time being. We're switching bigadv over to A3, but as you may have noticed there's a bug in the linux A3 core that affects bigadv stability. We've been working on the bug, but it's still in hiding at this time. If you're running VM's under windows, I'd suggest trying the native windows client, which is still enabled for bigadv. OS/X is also still enabled. Run with the -bigadv command line option. Depending on the work unit availability, machines requesting bigadv may roll over to normal -advmethods.

More info here. Please note that it hasn't been updated for Windows yet, but it can give you a general idea about the bigadv WUs. An interesting update is:
Kasson wrote:Q: I'd like to try running these units to burn in our new ultra-secret 80-core chip at work - with permission, of course. Is there any upper limit to the bonus points you will award?
A: At current time, the maximum bonus factor is 10x (completion of a 2681 work unit in 1/50th the deadline = approx 2 hrs 50 min). If you're in a position to exceed that, talk to us.
The maximum bonus factor of 10x has been removed: <Click>

  • Running bigadv WUs:
1) A system with 8 or more Physical Cores. (MUST READ NOTE #1 & #2)

2) Download the latest F@H SMP2 BETA Client (v6.30): <Click>

3) Install the F@H SMP2 Client by following this guide: <Click>

4) If you want to take advantage of the Bonus Points (highly recommended), make sure that your Passkey/Username is already qualified.

5) Run the F@H SMP2 Client with these flags before it downloads the WU:
    -verbosity 9 -bigadv -smp
6) Windows OS 32/64 bit.


1) Those of you running Intel Core i7-800 Series CPU or Intel Core i7-900 Series CPU will notice that in the Task Manager and Device Manager, 8/12 CPUs will be shown and may assume that your system is capable of running bigadv. This isn't the case. The fact of the matter is that these CPUs are Quad/Hexa Cores with HT (Hyper-Threading) thus you have 4/6 Physical Cores with 8/12 Threads while Standford recommends at least 8 Physical Cores. The only reason you can obtain these bigadv WUs is because of a loophole(confirm?) in the detection mechanism of the Client which reports 8/12 Cores to the Servers. HOWEVER, if you have an Intel Core i7 system that is Overclocked and STABLE (Read Troubleshooting below), you can try running the bigadv WUs and see if your system can fold within the Preferred Deadline (Read Minimum CPU Speed For Each CPU Model below).

2) The minimum amount of RAM is 0.50 GB/Core which turns out to be 4 GB. The recommended is 0.75 GB/Core which equates to 6 GB. The more-than-enough is 1 GB/Core which results in 8 GB. Note that 32-bit OS can't use RAM sizes above 4 GB. (This is the Official requirement for Linux and OSX. There isn't any Official word for Windows yet but RAM Usage for F@H Client is generally <2 GB)

3) A report has been made that a fast CPU with slow RAM can be overall slower then a slow CPU with fast RAM. This may be due to the fact that the FahCore_a3 uses more RAM to process the bigadv WU then the standard WU. (Further testing is required before it can be confirmed so please experiment with it and report your findings here.)

4) If you are already running the latest F@H SMP2 Client and have been qualified for the Bonus Points, use the -oneunit flag. After the F@H SMP2 Client exits, replace -advemthods flag (if you have it) with -bigadv flag. Do not use both as -advmethods may override -bigadv.

5) If you forget to use the -smp flag, your F@H SMP2 Client will download a Classic WU which will use only one core/thread regardless of how many you have.

6) If you forget to use the -bigadv flag but are using the -smp flag, your F@H SMP2 Client will download a normal a3 WU.

7) If you are using -smp X instead of -smp then it is recommended that you use a non-prime number for the X value as there is a known issue with scaling when using prime numbers. PG is aware of it and will hopefully provide a fix.

8) New users should first obtain the passkey so that they can take advantage of the Bonus Points. I recommend that they qualify for the Bonus Points by first folding normal a3 WUs and once you become eligible for the Bonus Points, you can try folding bigadv WUs.

9) Donors with slow internet connection should take the upload time of the WU Result (~100 MB) into consideration when estimating Bonus Points. If you fail to upload the WU Result before the Preferred Deadline, you will not get Bonus Points even if you have finished processing the WU before the Preferred Deadline. Availability of Standford Servers isn't guaranteed thus any delay will have a negative impact on your Bonus Points and Pande Group isn't responsible.

  • Preliminary Results:
Please use this format to submit the data:

    Project #:
    Average TPF:
    CPU Model:
    CPU Speed:
    # of CPU sockets:
    # of cores/threads available:
    # of threads used by fahCore_a3:
    RAM installed:
    RAM used (F@H):
or this one:

    Project #---CPU Model---CPU Speed---RAM Used (F@H)---SMP X---TPF---OS---32/64---Dedicated---Username

Explanation Of The Terms:

    Project #: -> The Project # available to Windows Users. So far there are Projects 2684 & 2685
    Average TPF: -> The Average Time Per Frame for this Project. You can use HFM.NET to get this data.
    CPU Model: -> What is the Processor's Model that you are using?
    CPU Speed: -> What speed is your Processor running at?
    # of CPU sockets: -> Most motherboards have 1 CPU Socket. The exceptions are server motherboards and EVGA SR-2.
    # of cores/threads available: -> The number of Physical Cores followed by the number of Threads available.
    # of threads used by fahCore_a3: -> How many cores/threads have you dedicated to F@H SMP2 Client?
    RAM installed: -> How much RAM is installed in your system?
    RAM used (F@H): -> How much RAM F@H SMP2 Client is using when folding. Memory value of FahCore_a3.exe can be found in the Task Manager under the Processes Tab.
    OS: -> What version of Windows are you using and is it 32 or 64 bit?
    Dedicated: -> Is you system folding 24/7 or do you use it for other purposes?
    Username: -> In case you need to be contacted about your submitted data.

Collected Data:

Project #---CPU Model---CPU Speed---RAM Used (F@H)---SMP X---TPF---OS---32/64---Dedicated---Username
Code: Select all
2684---4 X Opteron 8356---2.30---1.24---16---37:37---Win Server 2008 R2---64---Yes---thegrub
2685---2 X Opteron 6168---1.90---1.50---24---23:23---Win 7---64---Yes---10e
2684---4 X Xeon E7450---2.40---1.46---24---24:54---Win Server 2008 R2---64---Yes---ParrLeyne
2684---2 X Xeon E5440---2.83---1.16/0.84---8---52:31---Win 7---64---Yes---haitch
2684---2 X Xeon E5520---2.27---1.23---16---40:05---Win 7---64---Yes---Borgis
2685---2 X Xeon E5520---2.27---1.38---16---30:02---Win 7---64---Yes---Borgis
2684---2 x Xeon X5670---4.03---1.45---24---17:27---Win 7---64---Yes---brentpresley
2684---2 X Xeon X5670---2.93---1.35---20---25:17---Win 2008R2---64---No---ParrLeyne
2684---2 x Xeon X5650---2.66---1.45---24---25:15---Win 7---64---Unknown---ahu
2684---2 X Xeon X5650---4.07---1.40---24---17:03---Win 7---64---Yes---Parja
2684---2 X Xeon X5450---3.20---1.04---8---43:58---Win 7---64---Yes---Senture
2684---Xeon L5640---3.79---1.20---12---34:41---Win 7---64---Unknown---brentpresley
2684---Xeon W3540---4.20---1.00---8---41:11---Win 7---64---Yes---DonMarkoni
2684---Xeon W3520---4.00---1.00---8---44:20---Win 7---64---Yes---filu
2684---i7 980X---4.40---1.13---12---30:05/30:23---Win 7---64---No---Kougar
2684---i7 980X---4.35---1.25---12---28:09---Win XP---64---Yes---pholcman
2685---i7 980X---4.20---1.20---12---23:06---Win 7---64---Yes---Mr.Nosmo
2685---i7 980X---4.10---Unknown---11---25:09---Win 7---64---Unknown---RU_Hil
2684---i7 980X---3.86---Unknown---12---32:16---Unknown---Unknown---Unknown---fiCaks
2684---i7 980X---3.78---Unknown---12---35:03---Win 7---64---Yes---Mactin
2684---i7 980X---3.74---0.84---12---38:01---Win 7---64---No---pfv_i7980x
2685---i7 975E---4.05---1.06---8---34:04---Win 7---64---Yes---Mlitz
2684---i7 950---3.77---Unknown---8---52:17---Unknown---Unknown---No---rickoic
2684---i7 930---4.00---1.00---8---45:15---Win Vista---32---No---stevehat1
2684---i7 930---4.00---Unknown---8---43:57/45:27---Win 7---64---No---uncle fuzzy
2684---i7 930---4.00---1.50---8---45:44---Win 7---64---Yes---B2K24
2684---i7 930---3.80---1.00---8---45:00/44:28---Win 7---64---No---Zagen30
2684---i7 930---3.52---1.00---8---51:28---Win 7---64---No---cordis
2684---i7 920---4.10---Unknown---8---43.23---Win 7---64---No---Spongebob25
2684---i7 920---4.00---1.00---8---48:31---Win 7---64---No---leexgx
2684---i7 920---3.90---1.00---8---47:00---Win 7---64---No---the animal
2685---i7 920---3.90---1.00---8---38:00---Win 7---64---No---the animal
2684---i7 920---3.88---Unknown---8---51:50---Unknown---Unknown---Yes---rickoic
2684---i7 920---3.80---1.01---8---45:45---Unknown--Unknown---Unknown---10e
2684---i7 920---3.80---1.00---8---46:42---Win 7---64---Yes---filu
2684---i7 920---2.22/3.70---Unknown---8---56:25---Unknown---Unknown---Yes---rickoic
2684---I7 875K---4.00---1.02---8---47:12---Win XP---64---No---10eeee
2684---I7 860---3.80---Unknown---8---50:00---Win 7---64---Yes---Alpineb1
2684---i7 860---3.80---0.96---7---53:00/51:00---Win 7---64---No---PantherX
2685---i7 860---3.80---1.00---7---39:48/41:00---Win 7---64---No---PantherX
2684---I7 860---3.78---Unknown---8---53:16---Win 7---64---No---Alpineb1
2684---i7 860---3.36---1.00---8---56:49---Win XP---32---No---cordis

Minimum CPU Speed For Each CPU Model:

Please note that this is obtained from the above data and isn't a complete or official list. I will be only using values from Project 2684 instead of Project 2685 and the reason is that the TPF of Project 2685 is lesser than that of Project 2684. If a CPU at a particular speed barely makes the Preferred Deadline for Project 2685, it won't be able to make it for Project 2684 as its TPF is significantly more. However, if a CPU at a particular speed will make the Preferred Deadline for Project 2684, it can easily make it for Project 2685. For future Projects, I will be using the one with the Maximum TPF to ensure that a system can finish all bigadv WUs and not only WUs from a particular bigadv Project.

    Core i7-860 - 3.36 @ -smp 8 OR 3.80 @ -smp 7
    Core i7-860S -
    Core i7-870 -
    Core i7-875K - 4.00 @ -smp 8
    Core i7-880 -
    Core i7-920 - 3.80 @ -smp 8
    Core i7-930 - 3.52 @ -smp 8
    Core i7-940 -
    Core i7-950 - 3.77 @ -smp 8
    Core i7-960 -
    Core i7-965 Extreme Edition -
    Core i7-975 Extreme Edition -
    Core i7-980X - 3.78 @ -smp 12 OR 3.34 @ -smp 8

  • Observations:
1) Please remember that all these values are calculated from Project 2684 & 2685. Future Projects may decrease/increase these requirements.

2) The current Projects 2684, 2685, 2686, 2692 (modified Project 2682 as it caused problems) have a Preferred Deadline of 4 days which would mean that if you want to get Bonus Points, your TPF should be less than 57:36 otherwise you will exceed the Preferred Deadline and will only get Base Credits which is 8955.

3) This category of WUs is still classified as trial: <Click>

4) Due to donor requests, normal SMP2 WUs (Project 6701 & 6702 plus future ones) will have a new method for calculating their Preferred Deadline and Final Deadline. HOWEVER, this method doesn't apply to bigadv WUs so if you can't meet the Preferred Deadline, please switch over to normal SMP2 WUs. (Details)

5) When reading the above table, you may notice that some machine are not dedicated. I would like to clarify that these machines do run the F@H SMP2 Client 24/7 but are also used for personal usage in such a manner that it doesn't have a significant negative impact on the F@H SMP2 Client and are able to return the WU Result before the Preferred Deadline.

7) Users with Unknown fields, please post the missing data so that I can update your record(s).

8) Links to interesting Threads in this Forum:
A) Hardware Tweaks For Running bigadv WUs: <Click>
B) Frame Times on BigAdv A3 Projects: <Click>
C) Project 2692 Feedback: <Click>

  • Troubleshooting The F@H SMP2 Client: (bigadv Only)
If for some reason, you can't run bigadv WUs on a system that is capable of running it, you may want to read this:

1) To ensure system stability, F@H developers have their own stress tool called Stress CPU which is highly recommended to run on an Overclocked system to ensure that they are F@H Stable. Personally, I find that Prime95 is less stressful then Stress CPU while IntelBurnTest configured for Maximum with 5/10 iterations is more stressful then Stress CPU. I would recommend that first time users for IntelBurnTest start with Standard Mode and select the appropriate number of threads and set the iterations to no less than 5 and no higher than 20. Start the application. During this burn-in period, you should monitor the temperatures of the CPU (if the temperature rises above your comfort level, you can abort the test). Once it completes this run successfully, select the Higher Mode and repeat. You can also select the Maximum Mode once the Higher mode has finished a successful run. Do note that each time you select a different Mode, the time taken to complete the test will vary. If any errors are found, you may want to reduce the Overclock and try again.Remember that Overclocking may damage your hardware and will void your warranty. Do it at your own risk and no-one other than you is responsible for any damage that may occur when using any stress software or when Overclocking your system.

2) If you want to experiment with your Overclock, you can "capture a WU" and let your system fold it. Do remember that you will not get any points for it. You can capture a WU by copying the entire SMP2 directory while the WU is being folded. You will have to reconfigure the Client and set this option (in advance configuration):
Ignore any deadline information (mainly useful if
system clock frequently has errors) (no/yes) [no]?
Set it to "Yes". You can then hold this WU indefinitely and use it to test your system. In the Work folder, you can keep only wudata_0X.dat and wuinfo_0X.dat files and delete the rest so it will fold from the start. (This may vary from version to version and I tested it with v6.30). I also choose to block the Client from internet connection to ensure that it won't connect to the Servers.

3) If you TPF is more than 57:36 and your system isn't dedicated, you may want to use -smp N before switching over to normal WUs. The way I test what value of N in -smp N is better for my system is like this:
Step 1: I first run the SMP2 Client only with -smp flag
Step 2: I note the TPF for the WU to fold from 0% -> 1% by looking in the Console Window (Value 1)
Step 3: Terminate the SMP2 Client and delete all the files in the Work folder except the wudata_0X.dat and wuinfo_0X.dat files so that I have "reset" my WU to start from 0%
Step 4: Run the GPU Client(s) and the SMP2 Client with -smp flag
Step 5: I again note the TPF from 0% to 1% (Value 2)
Step 6: I compare Value 2 to Value 1. If there is a significant difference, then I lower the N value by 1 in -smp N (i.e in your case, it will be -smp 11) and redo from Step 3 -> Step 5 until I get a Value 2 that is close to Value 1.

If I have made a mistake, please tell me so that I can correct it.

Thanks to:
DonMarkoni = Suggested that I elaborate on Intel Core i7 Series which will help new users and who also found an interesting relationship between slow RAM on fast CPUs and fast RAM on slow CPUs.
7im = How to "capture a WU" and keep it indefinitely.
Plus anyone else that I may have forgotten.
Last edited by PantherX on Fri Aug 27, 2010 4:40 am, edited 43 times in total.
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time

Welcome To The F@H Support Forum Ӂ Chrome Folding App (Beta) Ӂ Troubleshooting "Bad WUs" Ӂ Troubleshooting Server Connectivity Issues
User avatar
Posts: 6614
Joined: Wed Dec 23, 2009 9:33 am

Re: Project 2684 A3 Core + Windows (Native)

Postby Zagen30 » Tue Jun 29, 2010 5:31 pm

I've got my WinSMP client set to grab them when it finishes its current WU. Which, since it's working on a 6701 that started only a few hours ago, won't be done until sometime tonight.
Posts: 1814
Joined: Tue Mar 25, 2008 12:45 am

Re: Project 2684 A3 Core + Windows (Native)

Postby PantherX » Tue Jun 29, 2010 5:38 pm

In roughly 3 hours, my P 6014 WU will finish then I will reconfigure the Client. If I had read the post 5 minutes earlier, I could have reconfigured the Client and avoided getting the P 6014 WU. Anyways, this is still better than P 6701 WU as it takes much longer on my system.
User avatar
Posts: 6614
Joined: Wed Dec 23, 2009 9:33 am

Re: Project 2684 A3 Core + Windows (Native)

Postby 10e » Tue Jun 29, 2010 5:53 pm

I've had my WinSMP clients with the -bigadv switch and 3072MB RAM allocated ever since the Linux A3 units came out, and I have one.

Performance is on par with Linux A3, but hopefully no crashing. I don't mind losing PPD, but I really hate units that die after 30 hours of wasted energy and hardware "wear", and I've had a number die at 22% and more with the Linux in a VM clients.

Right now TPF on 2684 R3, C9, G4 is at 45:45 on this box listed second last in my 2684 frame times post > i7 920 @3.8Ghz, with the 45:38 average frame time. BUT, the big advantage is that it is only using 1011MB according to Win Task Manager with -smp 8.

Posts: 83
Joined: Thu Mar 05, 2009 12:36 pm
Location: Toronto, Ontario, CANADA

Re: Project 2684 A3 Core + Windows (Native)

Postby brentpresley » Tue Jun 29, 2010 5:59 pm

Here's my performance data.

Project #: 2684
Average time/frame: 34:41 mins
CPU: Gulftown Xeon L5640 Overclocked to 3.79GHz
# of CPU sockets: 1
# of cores: 6
# of fahCore_A3 processes running: 12

RAM installed: 12 GB
RAM used by FAH: 1.2 GB <-- HECK YEAH!!!
OS: Windows 7 Enterprise x64
Posts: 248
Joined: Sun Jun 15, 2008 12:05 am
Location: Dallas, TX

Re: Project 2684 A3 Core + Windows (Native)

Postby ahu » Tue Jun 29, 2010 6:48 pm

Done three frames here. Even with -smp 24, the RAM usage is only 1.45 GB.

Project #: 2684
Average time/frame: 25:15 mins
CPU: 2 x Xeon X5650 @ 2.66 GHz
# of CPU sockets: 2
# of cores: 6
# of fahCore_A3 processes running: 24

RAM installed: 24 GB
RAM used by FAH: 1.45 GB
OS: Windows 7 x64
Posts: 61
Joined: Sat Jul 19, 2008 7:07 pm
Location: Finland

Re: Project 2684 A3 Core + Windows (Native)

Postby Kougar » Tue Jun 29, 2010 8:41 pm

Just to point out first, I have no idea how much of this improvement was due to the "optimizations" made to the 2864 projects between my last 2864 WU and this one.

Linux VM TPF ~34:03
Win 7 64 Native TPF ~30:05 (so far)

Due to the high Kfactor this bump in performance is giving me PPD equivalent/slightly better to what I had under A2 Bigadv folding in Linux. And with 1.13GB needed :shock:

Project #: 2684
Average time/frame: 30:05 to 30:23 (Still in progress, not a dedicated machine, F@H GPU2 running, etc etc)
CPU: Gulftown 980X @ 4.40GHz
# of CPU sockets: 1
# of cores: 6
# of fahCore_A3 processes running: 12

RAM installed: 12 GB
RAM used by FAH: 1.13 GB
OS: Windows 7 64bit
User avatar
Posts: 191
Joined: Fri Apr 11, 2008 2:39 am
Location: Texas

Re: Project 2684 A3 Core + Windows (Native)

Postby PantherX » Tue Jun 29, 2010 10:51 pm

Well, I did manage to get the bigadv WU but I highly doubt that I can complete it within the Preferred Deadline. My system is non-dedicated, running with -smp 7

Project #: 2684
Average time/frame: 00:56:46 (HFM.NET after 1%)
CPU: Intel Core i7-860 @ 3.6
# of CPU sockets: 1
# of cores: 4
# of fahCore_A3 processes running: 7

RAM installed: 4 GB
RAM used by FAH: 0.95 GB
OS: Windows 7 x64

It looks like that I may not be able to complete it within the deadline. Any suggestion on what should be the recommend CPU Speed so that I can finish it before the Preferred Deadline.


Some of my observations:
1) CPU temp has dropped by 5C
2) The Kernel Times are very low when compared to normal a3 WUs
3) My PPD has taken a 4K jump
User avatar
Posts: 6614
Joined: Wed Dec 23, 2009 9:33 am

Re: Project 2684 A3 Core + Windows (Native)

Postby bruce » Tue Jun 29, 2010 11:29 pm

Scaling between -smp 6 and -smp 8 is pretty much what one would predict. Scaling at -smp 7 can be inconsistent compared to numbers which can be factored. What happens if you shut everything else down when you go to bed and restart with -smp (8)? Does -smp 6 run better or worse that -smp 7?

I think the latest Windows FahCore_a3 can shut down/ restart reasonably safely and you can change the number of cores to suit the current utilization patterns. A3 tends to run at the speed of the slowest core so when there's contention, it can kill performance. There's no way to know if all your other applications can be processed by a single core, leaving 7 of them always available.
Site Admin
Posts: 20998
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Project 2684 A3 Core + Windows (Native)

Postby uncle fuzzy » Tue Jun 29, 2010 11:44 pm

PantherX wrote:It looks like that I may not be able to complete it within the deadline. Any suggestion on what should be the recommend CPU Speed so that I can finish it before the Preferred Deadline.

I have a little leeway with 2684 on an i7-930@4.0.

W7 Ult x64
12GB triple @ 1200
-smp 8

with single nVidia GPU client- 45:27
running solo- 43:57
Proud to crash my machines as a Beta Tester!

User avatar
uncle fuzzy
Posts: 1192
Joined: Sun Dec 02, 2007 10:15 pm
Location: Michigan

Re: Project 2684 A3 Core + Windows (Native)

Postby Grandpa_01 » Wed Jun 30, 2010 12:55 am

I think you are going to need to run -smp 8 I think 3.6 should be enough to complete it on time. The testing that I have done shows that -smp 7 causes about a 20% hit in performance with the A3 core on an I7 920 @ 4.2Ghz.
2 - SM H8QGi-F AMD 6xxx=112 cores @ 3.2 & 3.9Ghz
5 - SM X9QRI-f+ Intel 4650 = 320 cores @ 3.15Ghz
2 - I7 980X 4.4Ghz 2-GTX680
1 - 2700k 4.4Ghz GTX680
Total = 464 cores folding
User avatar
Posts: 1873
Joined: Wed Mar 04, 2009 7:36 am

Re: Project 2684 A3 Core + Windows (Native)

Postby rickoic » Wed Jun 30, 2010 1:17 am

Ok, made sure I had the latest so d/l'd FAH6.29beta-win32-SMP-mpich and installed it.
Got it up and running with 'BIG' wu's, -bigadv -smp 8 but when it got a work unit it picked up a p10040 Standard wu.

Did I do something wrong?

Fold on
Duel 2.8 3 250's Quad 2.4 285. 260, Quad 2.4 3 250 , i7 2.27 2 250 GPU's, i7 2.24 2 250 GPU's, i7 3.06 bigadv, duel Xeon 2.27 bigadv, AMD Phenom ][ 3 250 GPU's, Laptop GT 130M.
I'm folding because Dec 2005 I had radical prostrate surgery.
Posts: 296
Joined: Sat May 23, 2009 4:49 pm
Location: Mississippi near Memphis, Tn

Re: Project 2684 A3 Core + Windows (Native)

Postby bruce » Wed Jun 30, 2010 1:30 am

Yes. You did something wrong.

At least once during the installation, you started the client without the -smp flag and it reverted to the classic client, downloading a WU for a single CPU. Unfortunately this is a fairly common error, though the guides have been explicitly rewritten a couple of time to try to avoid whatever mistake you made during installation.

Is your installation sequence clear enough in your short-term-memory to tell us what step you missed?
Site Admin
Posts: 20998
Joined: Thu Nov 29, 2007 10:13 pm
Location: So. Cal.

Re: Project 2684 A3 Core + Windows (Native)

Postby PantherX » Wed Jun 30, 2010 1:49 am

Well, I did went to bed so the system was pretty much idle when it was running with -smp 7. I left at 1% and woke up to 3%, here is from HFM.NET:
Min. Time / Frame : 00:56:01 - 14,689.64 PPD
Avg. Time / Frame : 00:56:29 - 14,507.96 PPD
Cur. Time / Frame : 00:56:01 - 14,563.85 PPD
R3F. Time / Frame : 00:56:29 - 14,443.52 PPD
All Time / Frame : 00:56:29 - 14,443.52 PPD
Eff. Time / Frame : 01:13:19 - 11,127.32 PPD

I Ctrl+C the Client and changed the -smp 7 to -smp 8 and restarted. It started from 3% but when it did, it displayed "Using Gromacs checkpoints" I haven't seen this message before so I am guessing that it is specific to bigadv only.
If I am unable to lower my TPF with -smp 8, it will then experiment with -smp 6 and report my findings. If possible, I might bump by OC from 3.6 to 3.8 but that would be the last resort. I am also running the GPU2 Client.

@uncle fuzzy: could you please describe what you mean by "little leeway" as I will be needing about 3-4 hours before the deadline in order for me to finish uploading the WU to the Servers before the Preferred Deadline. I have head that the bigadv WU have 100MB results and on my connection, it takes roughly 1.5 hours to upload 60 MB file.

@Grandpa_01: Thanks, maybe that 20% boost is all I need to make it within the deadline.
User avatar
Posts: 6614
Joined: Wed Dec 23, 2009 9:33 am

Re: Project 2684 A3 Core + Windows (Native)

Postby rickoic » Wed Jun 30, 2010 2:08 am

bruce wrote:Yes. You did something wrong.

At least once during the installation, you started the client without the -smp flag and it reverted to the classic client, downloading a WU for a single CPU. Unfortunately this is a fairly common error, though the guides have been explicitly rewritten a couple of time to try to avoid whatever mistake you made during installation.

Is your installation sequence clear enough in your short-term-memory to tell us what step you missed?

1. Ran the install
2. Went to Program Files (x64) and made shortcut
3. Looked to change shortcut to different folding folder, but when I did it the shortcut turned into a shortcut to the folder, so deleted it and made another shortcut and left it alone.
4. Ran the short-cut and when it tried to d/l the b4 core it wouldn't unzip right. So had to stop it and return using administer priliveges and it started up.

When I ran the short-cut I put the flags into it so that it would run the -bigadv -smp 8 flags whenever the shortcut was ran.
Bet all I have to do is stop the folding and then restart it and the flags will then be active the next time it goes to get a work unit.

Fold on
Posts: 296
Joined: Sat May 23, 2009 4:49 pm
Location: Mississippi near Memphis, Tn


Return to SMP with bigadv

Who is online

Users browsing this forum: No registered users and 1 guest