When proteins are created, they undergo a complex process known as folding, so-called because the protein molecule transforms from a long chain of amino acids to a complex shape (it "folds up"). The final shape of the protein is absolutely critical to determining its properties and function. Scientists have created software to simulate the folding process to better understand how proteins work, which in turn makes it possible to develope new drugs, cure diseases, etc.
Folding@Home is a project from Stanford University that uses millions of networked PCs to form a supercomputer for protein folding simulations. The client software is loaded on a PC, it contacts the central servers, and receives "work units". The client then runs on spare CPU time, and uploads finished work units to the server.
Folding@Home is a great way to make your computer do useful work even when you're not using it. Since it runs at a very low priority, you should never realize it's running when you're using the computer to do your work. Note that "using the computer" refers to doing heavy computations. Generally, tasks like web browsing and word processing involve very little CPU usage, so the Folding@Home client will be running at near 100% even when doing those kinds of tasks. It helps to leave you computer on at all times, but is not necessary, as the project will benefit from virtually any time that the client runs on your computer.
The following script will download the latest client from the Folding@Home website, and install it to opt/foldingathome, either in / or $HOME. It will ask you to set up the client (the defaults are usually sufficient), and copy that configuration for every CPU in your machine.
It is not possible to provide a .deb package for Folding@Home, because the client must be downloaded from Stanford's website. This is to ensure the integrity of the research.
To install, download the tarball and do
tar zxvf fah_install-version.tar.gz
This should extract the archive to a folder called folding/. Then
cd fah_install less README
to read the documentation. Finally,
sudo ./folding_install.sh install
to install the client.
You can also install to your $HOME, in case you do not have root access to the computer. Clearly, you would not have to prefix the command with sudo in this case. If you install to your $HOME, a cron job will be created to start the client automatically. If you install to the system, the client will automatically start when your computer boots up.
You can reconfigure the client using the supplied reconfigure script. You can also give the client command line options. See the README for more details.
Because the client runs at low priority, the client should not cause the CPU governor to kick up the frequency. In other words, even though the client runs at 100% CPU usage, it should not cause the CPU frequency to go up, which keeps the fan slow and quiet. If this is not the case, then the frequency governor should be reconfigured.
One can configure ACPI (the power regulation subsystem) to stop the client when the system goes on battery power, and to start it again when the power cord is plugged back in. Edit /etc/acpi/power.sh. Inside the if [ $? = 0 ] && [ x$1 != xstop ]; then block, add
# stop folding at home if [[ -x /etc/init.d/foldingathome ]] ; then /etc/init.d/foldingathome stop fi
and inside the else block, add
if [[ -x /etc/init.d/foldingathome ]] ; then /etc/init.d/foldingathome start fi
This assumes that the client has been installed for the entire system, which it should be if you are able to edit files in /etc in the first place!
For questions and bug reports, go to the [http://ubuntuforums.org/showthread.php?t=101817 forum thread].
Folding@Home is secure. The Stanford team has gone to great lengths to ensure security, both for the integrity of their research and the safety of donors' computers. However, the more secure the better. The Gentoo ebuild for Folding@Home creates a new user foldingathome whose sole purpose is to run the client. Now this installer offers same. It creates a user whose account is disabled, and runs the client as this user when the init script is run as root, so the client is never run as root.
For those with Hyper Threading CPUs, you probably know that an SMP kernel sees two processors. Then clearly, if you run two clients, you will get more work done than if you only run one (probably about 10-30% more). However, results that are done quickly are more useful than more results done slowly. The reason is that each work unit is a step in a giant simulation, with future steps depending on past ones. So the faster you get your work done, the faster the simulation can move along. Long story short, run one client for each physical CPU, not for each logical CPU. The installer should automatically count the number of CPUs in your system. See this [http://forum.folding-community.org/viewtopic.php?t=10427 post] in the Folding@Home forums.
A competitive folding@home team called Team Ubuntu has formed to represent the Ubuntu community and organize to have fun while doing some good. The team number is 45104. To join the team, simply enter 45104 when the setup dialog requests a team number. Those wishing to get optimal performance from their folding box should review the Hackaday blog entry on competitive folding linked below.
[http://folding.stanford.edu/ Folding@Home Distributed Computing]
[http://www.hackaday.com/entry/1234000673058540/ HOW-TO: Folding@Home competitively]
[http://fahstats.com/t.php?t=45104 Folding@Home Stats for Team Ubuntu]
[http://folding.extremeoverclocking.com/team_summary.php?s=&t=45104 Another Stats site]
[http://www.ubuntuforums.org/showthread.php?t=101817 Ubuntu Forms HowTo, Based off of this page]