...FahMon (though it doesn't seem to be in real-time -- does it just read the FAG log when you start the program?).
The folding directory (or folder) contains at least the following:
- Work (a directory or folder that contains several work related files plus log files)
- Fahlog.txt (the running log of current work progress plus a limited amount of past work)
- machineindependent.dat - For Linux and OSX, contains a unique computer ID in binary form.
Windows default generates this ID in the Windows Registry.
These are not same as machineid discussed below.
- Client.cfg (the configuration file for the client - contains username, team number, machineid & setup parameters)
- The folding client (Fah-xxx.exe or Folding@Home-xxx.exe) This is the executable that starts the folding core.
- One or more cores (FahCorexxxNumber.exe) - these do the folding
- Queue.dat - contents not fully disclosed by Stanford. Encoded data regarding the work unit.
- Unitinfo.txt - a file that shows the name of the protein, download date, & currrent progress, etc.
- SMP folders have a version of the mpiexec (for multiple processing cores)
The filename extensions (.xxx) may not be visible to some users depending on OS setup.
Fahmon, or some versions of it, examines the Work files, Queue.dat files, Fahlog.txt and Unitinfo.txt.
Fahmon does not have a protein display, it mainly tracks progress at update times selectable by the user.
If a protein display is desired,
see this post regarding InCrease.
Now trying to figure out how to either have two different smp clients so my 8 cores are used (2 x 4), or use the SMP 8 flag and see if there are WUs that can use 8 cores.
If you choose to use two clients or more, make separate directory (folders) for them. Set up the start-links or start-commands so that the OS cannot get confused because the Folders (directories) will contain executables with the same names.
Okay, now I see 4 FahCore_a2.exe in the monitor,
Seems good, currently Core A2 is the most efficient one.
and they are all running around 90% (wonder why they don't go higher, because that's equivalent to not using 40% of one CPU).
The four threads generated by the client depend on each other to make progress. They cannot be computed independently. Each thread (folding calculation) runs at different speeds. Ultimately the folding speed can be no faster than the slowest thread, thus cores waiting (less than 100% utilization).
Some folders run other clients (could be regular clients or SMP clients) to pick up the unused CPU cycles. There are various combinations that have been tried. Some run one SMP client per core (four threads), in your case that would be 32 threads. One-client-per-core is not the best configuration, but it may be better than some possible setups.
You may have to experiment and find the best combination for your system.
Google around and checked forums to figure out how to simply install two clients in different folders, and couldn't find anything very useful.
This is an attempt to recall the process, and provide a bit of Mac OS guidance, but it may be lacking.
- Copy one complete install into a separate directory.
- Grant appropriate permissions to the copied files, specifically:
The client (Fah6), the cores (FahCore_xNumber.exe), mpiexec, and the Work folder.
Permissions can be granted using the equivalent of "sudo chmod +x", this grants permission to everyone.
Permissions could be related to an inquiry in the first post.
"...can't open the application Folding@home because it is not supported on this architecture"
Windows folders don't have to be too concerned about permissions, just have to be concerned about viruses.
- Change the "machineid" located in the Client.cfg file of 2nd client, as follows:
In the second folding directory (folder):
Open the Client.cfg file with an editor and find "machineid=1"
Change the "1" to "2" and save it. Do not make any other changes, no spaces, no backspaces.
Just insert a 2 in front of the 1 and delete only the 1.
- Set up directed "Start" or "Command" links to the clients to be sure they are local to the OS, use the -local flag to start the clients.
A WinXP illustration of start-links is shown here using -advmethods flag.
In a similar manner as illustrated: Multiple flags can be used such as: -local -advmethods -smp -verbosity 9
Use one space between each specific flag.
Install more clients in a similar manner, increasing "machineid" up to 16.
Official support docs are pretty basic and don't seem to cover this.
Officially, Stanford prefers that SMP contributors fold with a maximum number of cores per work unit. The reasoning is to get a given work unit back to Stanford as quickly as possible. Of course many folders like to maximize efficiency of their computers and also to maximize their points-per-day (PPD)
Edited by dnamechanic, 21 December 2008 - 05:11 AM.