Folding@home on Amazon EC2
Posted: Mon Dec 03, 2007 1:34 am
Transferred from the thread on the backup Google group here:
http://groups.google.com/group/foldinga ... 81397d1f83
I think I'm almost done with my Folding@home on EC2 experiments. Thanks to theMASS for a ton of help in getting different approaches to work and in analyzing the results at 4am a couple nights.
My initial impression is that EC2 is probably not cost effective for Folding@home compared to alternatives like buying cheap hardware or (obviously) running it on spare cycles on systems you already use.
It has been, however, an interesting experiment in running applications on EC2 and prompted me to build a 64-bit large/extra large AMI for Ubuntu 7.10 Gutsy which should be released soon.
Tests:
For the first test, I used Christer Edwards' folding installer for Ubuntu:
http://ubuntu-tutorials.com/category/folding/
This seems to create a single worker (not sure of terminology here) for each CPU (though feedback from the author indicates it should be using the SMP client on multi-CPU systems).
The small instance costs $0.10/hour to run (1/2 of a dual core CPU). It started 29 Nov 06:22:21 and has completed 1200000 out of 1500000 steps (80%) as of 2 Dec 22:12:59. The live FAH log is available directly from the small folding instance while I leave it running:
http://ec2folding.azeelo.com/folding/FAHlog.txt
Browse around that server for other info including Munin charts, cpuinfo, and config.cfg.
The large instance costs $0.40/hour to run (2 dual core CPUs) and took about 24+ hours to complete its first 2 WUs (concurrently). The live FAH logs are available directly from the medium folding instance while I leave it running:
http://ec2folding-large.azeelo.com/fold ... FAHlog.txt
http://ec2folding-large.azeelo.com/fold ... FAHlog.txt
I tried a large instance using the SMP client following instructions here:
http://folding.stanford.edu/English/FAQ-SMP#ntoc29
I don't have the results handy, but they did not appear to be very good from discussions with theMASS.
I tried an xlarge instance using the non-SMP client for a while at $0.80/hour and its performance per WU seemed equivalent to the small instance.
The SMP client claims to be optimized for 4 cores, so I didn't try it on the 8 core xlarge instance.
Results:
If my calculations are correct, the large instance was folding at about $5/WU and the small and xlarge instances were about $11/WU. The difference between large and xlarge doesn't make any sense to me which leads me to...
Caveats:
- I just learned about Folding@home so I may not have installed and tweaked the configuration to get maximum performance out of EC2.
- I may not understand how to configure EC2 to get the maximum performance out of it, especially for this application, especially on 64-bit.
- The sample WUs that were assigned may have been unusually hard. Apparently not all WUs are created equal, and I'm not sure the best way to judge a platform's performance without running it for a long time (which gets expensive on EC2).
Followup:
Followup on the idle CPU part of the thread: I believe that the "top" program is reporting idle percentage incorrectly on the small instance type. Both vmstat and Munin reported that the CPU was completely in use with zero percent idle, while top consistently showed 25% idle.
Followup on "stolen" CPU cycles: The correct term is apparently "steal" not "stolen". Approximately 50% of the perceived dual-core CPU gets assigned to steal as the VM increases CPU usage on the small instance type. The large and xlarge instance types have 2 and 4 complete dual-core CPUs available so no steal shows up.
Offer:
I'd hate for my beginner attempts to be taken as the last word in EC2 folding, but since there seems to be nobody else trying it out or publishing the results I figured I should toss out what I had.
If anybody else would like to take a look at folding on EC2, I can provide AMIs, recipes, and advice for getting it running. If you are an expert with the folding software but don't want to learn how to use EC2, I can even fire up some instances on EC2 and give you ssh access to study them.
Best,
--
Eric Hammond
http://www.anvilon.com/
http://groups.google.com/group/foldinga ... 81397d1f83
I think I'm almost done with my Folding@home on EC2 experiments. Thanks to theMASS for a ton of help in getting different approaches to work and in analyzing the results at 4am a couple nights.
My initial impression is that EC2 is probably not cost effective for Folding@home compared to alternatives like buying cheap hardware or (obviously) running it on spare cycles on systems you already use.
It has been, however, an interesting experiment in running applications on EC2 and prompted me to build a 64-bit large/extra large AMI for Ubuntu 7.10 Gutsy which should be released soon.
Tests:
For the first test, I used Christer Edwards' folding installer for Ubuntu:
http://ubuntu-tutorials.com/category/folding/
This seems to create a single worker (not sure of terminology here) for each CPU (though feedback from the author indicates it should be using the SMP client on multi-CPU systems).
The small instance costs $0.10/hour to run (1/2 of a dual core CPU). It started 29 Nov 06:22:21 and has completed 1200000 out of 1500000 steps (80%) as of 2 Dec 22:12:59. The live FAH log is available directly from the small folding instance while I leave it running:
http://ec2folding.azeelo.com/folding/FAHlog.txt
Browse around that server for other info including Munin charts, cpuinfo, and config.cfg.
The large instance costs $0.40/hour to run (2 dual core CPUs) and took about 24+ hours to complete its first 2 WUs (concurrently). The live FAH logs are available directly from the medium folding instance while I leave it running:
http://ec2folding-large.azeelo.com/fold ... FAHlog.txt
http://ec2folding-large.azeelo.com/fold ... FAHlog.txt
I tried a large instance using the SMP client following instructions here:
http://folding.stanford.edu/English/FAQ-SMP#ntoc29
I don't have the results handy, but they did not appear to be very good from discussions with theMASS.
I tried an xlarge instance using the non-SMP client for a while at $0.80/hour and its performance per WU seemed equivalent to the small instance.
The SMP client claims to be optimized for 4 cores, so I didn't try it on the 8 core xlarge instance.
Results:
If my calculations are correct, the large instance was folding at about $5/WU and the small and xlarge instances were about $11/WU. The difference between large and xlarge doesn't make any sense to me which leads me to...
Caveats:
- I just learned about Folding@home so I may not have installed and tweaked the configuration to get maximum performance out of EC2.
- I may not understand how to configure EC2 to get the maximum performance out of it, especially for this application, especially on 64-bit.
- The sample WUs that were assigned may have been unusually hard. Apparently not all WUs are created equal, and I'm not sure the best way to judge a platform's performance without running it for a long time (which gets expensive on EC2).
Followup:
Followup on the idle CPU part of the thread: I believe that the "top" program is reporting idle percentage incorrectly on the small instance type. Both vmstat and Munin reported that the CPU was completely in use with zero percent idle, while top consistently showed 25% idle.
Followup on "stolen" CPU cycles: The correct term is apparently "steal" not "stolen". Approximately 50% of the perceived dual-core CPU gets assigned to steal as the VM increases CPU usage on the small instance type. The large and xlarge instance types have 2 and 4 complete dual-core CPUs available so no steal shows up.
Offer:
I'd hate for my beginner attempts to be taken as the last word in EC2 folding, but since there seems to be nobody else trying it out or publishing the results I figured I should toss out what I had.
If anybody else would like to take a look at folding on EC2, I can provide AMIs, recipes, and advice for getting it running. If you are an expert with the folding software but don't want to learn how to use EC2, I can even fire up some instances on EC2 and give you ssh access to study them.
Best,
--
Eric Hammond
http://www.anvilon.com/