Determining CPU usage.Determining the number of available cores or logical processors.Installing the SMP client.Installing additional clients on older and slower Multi-Core Processors.CPU usage.
•Right click on the 'Task Bar' at the bottom of your screen.
•Left click and select 'Start Task Manager'.
The CPU usage is displayed at the bottom of the Task Manager window.The number of cores or logical processors.
•Left click on 'Start".
•Left click on 'All Programs'.
•Left click on 'Accessories'.
•Left click on 'System Tools'.
•Left click on 'System Information'.
Under Item 'Processors', the number of cores and/or logical processors are displayed.Installing the SMP client on Multi-Core Processors.
Your system must have a recent dual core processor or better to run this client with the -smp switch in SMP mode. Four cores or more are strongly recommended. This means older single core processors cannot run this client with the -smp switch, and older dual cores will not meet the very short work unit deadlines. If after running this client with the -smp switch on an older dual or an older quad core system, and the client does not meet the work unit preferred deadline, please remove the SMP client and replace it with one or more instances of this preferred CPU client technique and/or GPU client. For more information, please read this installation guide. Windows XP or newer is required to run v6.x clients or later. and .NET 2.0 or newer is required in XP to run the SMP client. Windows Vista and newer meet both of these requirements. Windows 2000 is not supported.
You must first stop and delete the current running client. Consider waiting until the current Work Unit completes and then simultaneously depress the 'Ctrl' key with the 'c' key while in the console window. Then delete your FAH folder and all of its contents. If you were running the FAH client as a service you may also have to uninstall it via your Windows 'Control Panel'.
First, create a new folder for the FAH SMP client. In Windows Vista and Windows 7, this location is suggested: C:\Users\[username]\FAH - Please do NOT install the SMP client in C:\FAH or C:\Program Files\FAH to avoid issues with permissions. Vista/7 have new security restrictions (not in Win XP) that prevent the client from running. In Windows XP, this location is suggested: C:\FAH.
Download and open the v6.34 (or v7 Beta) SMP client executable file to the folder you just created from the instructions found Here.
To make the next steps easier to follow, renaming the client executable to something shorter, easy to remember, and install using the system console is suggested. Right-click on the executable file, select Rename and change it to 'fah6' or 'fah7' if you chose the newer beta version.
Note: Depending on the file name and folder display settings, the file extension may or may not be shown. Rename Folding@home-Win32-x86 to fah6 or rename Folding@home-Win32-x86.exe to fah6.exe.
You may want to consider a passkey at this point. It is recommended and you can acquire more points for each WU. Find out about how to get a passkey Here.
The next step is to configure the client. Open a Command Prompt and change the directory to the location where you unzipped the FAH SMP client. For example: ...>cd C:\Users\admin\fah
Type this in the command prompt to begin (assuming you renamed the FAH executable to "fah6" or "fah6.exe" depending on the file view settings as noted above):
At the prompt: C:\Users\[your user name]\FAH
fah6 -configonly -smp
The client will display some information and then prompt you for answers to configuration questions. Note that for most answers, the default setting is the recommended setting. Here is an example of what is displayed on screen, with an explanation of each option:
Installing additional clients on older Multi-core processors.
[16:25:22] Configuring Folding@Home...
User Name [Anonymous]?
Enter your FAH User Name (not the Windows user name). Or press enter to accept the default user name Anonymous. Almost everyone selects a personalized user name.
Team Number ? 4
Enter your FAH Team #. We are Team Number 4.
Enter your passkey, or press enter to leave it blank and go to the next option. Use of a passkey is optional. However, a passkey is required to be eligible for the quick return bonus on SMP2 work units.
Ask before fetching/sending work (no/yes) [no]?
Because of the short deadlines on SMP work assignments, persistent connections are strongly recommended and this option should be set to no.
Use proxy (yes/no) [no]?
If you are connected to a proxy, enter yes and configure the proxy options for proxy user name, password, address, etc. Or press enter to skip.
Acceptable size of work assignment and work result packets (bigger units
may have large memory demands) -- 'small' is <5MB, 'normal' is <10MB, and
'big' is >10MB (small/normal/big) [normal]? big
This option states a preference for the size of work units downloaded and uploaded to the project servers. Note that all SMP WUs are large in size, so big is the required setting. Bigger units will also have bigger memory requirements. If you run on a slower broadband or dialup internet connection, small is the recommended setting to ease your bandwidth usage and you may want to switch to the CPU client instead.
Change advanced options (yes/no) [no]? yes
If you want to change the advanced options, enter yes. It is not mandatory but is recommended for SMP installs.
Core Priority (idle/low) [idle]?
This adjusts the FAH client priority level. This is similar to, but not the same as the Windows priority setting. In most cases, the default idle setting is recommended.
Note: For better performance when mixing CPU or SMP clients with GPU clients, raise the priority of the GPU clients by selecting the low priority setting. Do NOT change the Windows priority settings for the client or fahcore.
CPU usage requested (5-100) ?
This will adjust the percentage of CPU usage. The FAH client only uses spare CPU cycles not used by other programs, so reducing this setting is not typically necessary. However, if you want to lower system temperatures, or reserve CPU cycles for more intensive computer tasks, enter a number below 100. In the SMP client, changing this setting does not reduce CPU usage.
Disable highly optimized assembly code (no/yes) [no]?
If you are having issues running the client, disable this. For 99.9% of the users, leave this at the default setting since this reduces the client performance a lot.
Pause if battery power is being used (useful for laptops) (no/yes) [no]?
If you run a laptop, set this to yes to pause if the laptop is not plugged into the wall. This will avoid the client draining the battery.
Interval, in minutes, between checkpoints (3-30) ?
Number of minutes between each checkpoint where the client is writing the client progress to disk in case of unexpected interruption. 15 is the recommended setting.
Memory, in MB, to indicate (1013 available) ?
Sets the amount of memory seen by the work servers. By default, it shows the full system memory amount. Note that reducing this setting does not reserve more memory for other programs. However, reducing this setting will prevent the client from downloading memory intensive work units. A setting too low may prevent the client from getting any new work. In the SMP client, .5 GB per CPU core is the minimum, while 1 GB per core is recommended.
Machine ID (1-16) ?
This is not applicable for the SMP client.
Launch automatically, install as a service in this directory (yes/no) [no]?
If you want the client to run as a service, say yes and it will install a new entry in the services list. The next time you restart the computer, the service will start automatically and run in the background. SMP as a service is only supported in v6.30 and newer.
Note: The current Windows user account must have Administrator privileges to install FAH as a service. And rebooting the computer to start the client running as a service is required.
The following options require you to restart the client before they take effect Disable CPU affinity lock (no/yes) [no]?
Not useful for SMP since it uses all cores.
Additional client parameters ? -smp
You can enter the client flags here so you don't have to type the flag each time you run the client. We strongly suggest you enter the -smp flag, especially when running as a service. Do NOT enter -config or -configonly or any single-use flag in this field to avoid problems.
IP address to bind core to (for viewer) ?
For future use when the Viewer is working better. Specifies the IP address of the machine of which the viewer should display the client output.
When you press enter after the last question, the configuration will end and you will be back to the command prompt. You have successfully configured the client so the next step is to start the client. Here are 3 ways:
1. By clicking on the executable icon (this assumes you entered the proper flags during configuration).
2. By typing fah6 on the same command prompt window. Enter the necessary flags (including the mandatory -smp flag) if you didn't enter those during configuration.
3. Create a new shortcut to the FAH executable, and double click that shortcut icon (assuming you added all needed flags to the client setup).
4. Create a new shortcut to the FAH executable and add it to your 'Startup' file.
Normally, if everything is done correctly, the client will be folding along fine. To verify the client is progressing, open the task manager and make sure there is one instance of the multi-threaded FahCore_a3.exe in the list. Or you can open the fahlog.txt file to see the client's progress.
For each additional core or logical processor you must create an additional FAH folder. As you created your original FAH client in folder C:\FAH, you must now create C:\FAH2, C:\FAH3, etc. for each logical processor that you wish to run the client on.
Use the original procedure that you followed for your first client and duplicate the installation procedure that you followed Here with these exceptions:
At the installation question for:
Change advanced options [no] (yes/no)? yes
Answer yes, and then at:
Machine ID (1-8) ? 2
Answer 2 for a dual core processor. For every additional core for which you will be running another client you must increment the Machine ID by +1
by Scilicet edited by sortofageek
last modified: 2012-05-15 18:02:53