So in an effort to help steer people in the right direction when they have decided to fold as to which client to run I have compiled the following information gathered from the F@H FAQs and my own personal experience.
How many points is it worth?
So first a quick introduction into how points are calculated, so first up its important to realise that not all work units are created equal, so not all take the same amount of time to complete. To solve this problem F@H use a set of bench mark systems to test work units, depending on how long the bench mark system takes will determine the points.
So the is an equation to determine how many points a particular work unit is worth. This equation is very simple and has only 3 terms they are,
Points value for unit type, x
Number of days bench mark system required to complete work unit, y
Points work unit is worth, z
So the equation looks like this,
x * y = z
Simple yes
So now some values for x, which depends on the F@H client you are running.
SMP = 1760
PS3 = 900
GPU = 330
CPU = 110
So now for an example,
Q. You are running a work unit using the CPU client which took the bench marking system 2.5 days to complete how many points is it worth?
A. 110 * 2.5 = 275 points
Which client is best/what should I use
This really depends on what your are using hardware wise we will look at a few different scenarios,
You have a duel core or quad core system (with a reasonable amount of memory, 1GB or more).
Use the SMP client.
You have a duel core or quad core system with less than 1GB memory.
Buy some more memory and run the SMP client , test SMP client for performance.
You have a single core CPU with an ATI X19xx graphics card.
Use the GPU client.
You have a single core CPU with an ATI x1650/x1800 graphics card.
Test the GPU client to see your performance.
You have a single core CPU and an nVidea graphics card or an ATI card which is not supported.
Use the CPU client.
You have a PS3.
Use the PS3 client.
How many points can I expect to generate
In this section I will put my personal experiences with some of the clients on my PC and will compare points per hour (pph).
So first my system, CPU is an Intel core 2 duo E6550, I have 2GB of Corsair XMS2 PC2-6400 C4 memory and my CPU is cooled with a Thermalright Ultra 90 with a quiet 92mm fan. My graphics card is an X1950 XT 256MB cooled with a Thermalright HR-03 with quiet 92mm fan.
Right starting with the SMP client (in Windows XP) which provides 1760 points per work unit (of size 500000 steps).
CPU Speed 2.33GHz, SMP unit takes ~30 hours, 59 pph.
CPU Speed 2.5GHz, SMP unit takes ~28 hours, 63 pph.
CPU Speed 2.675GHz, SMP unit takes ~27 hours, 65 pph.
CPU Speed 2.8GHz, SMP unit takes ~26 hours, 68 pph.
SMP units also come in a 1000000 step flavour I have only encountered one of these units so far and it was worth 1148 points,
CPU Speed 2.8GHz, SMP Unit takes ~22 hours, 52pph
Now I will look at the GPU client which provides 330 points per work unit.
Stock 2d Settings: GPU Clock 500MHz, Memory Clock 1188MHz, GPU work unit takes ~18 hours, 18pph.
Stock 3d Settings: GPU Clock 621MHz, Memory Clock 1800MHz, GPU work unit takes ~14 hours, 24pph.
It is potentially worth noting that you can run the CPU client at the same time as the GPU client on a duel core CPU, however due to the low memory on my x1950xt it utilises 1 CPU core to run as well. Apparently Graphics cards with more memory (512MB+) require less CPU time.
The CPU client bench mark is a 2.8GHz P4 with SSE turned off, I only have a Celeron @ 2GHz to test on as I don't want to stop SMP units to run on my main PC.
Two unit types have been completed they were as follows,
25000 step unit worth 338 points completed in 59.25 hours, 5.7pph.
5000000 step unit worth 165 points completed in 35.2 hours, 4.7pph.
Average pph based on above units, 5.3pph.
Now as we know a CPU unit is worth 110 points per day on the bench mark system so 4.6pph, as my Celeron clearly exceeds this at 2GHz compared to the benchmarked systems 2.8GHz the use of SSE is apparently quite significant.
An educated guess would be that a 3.5GHz+ clocked P4 with SSE could manage at most 10pph based on what we have seen from clock scaling on SMP units and this is over estimated in the CPU clients favour.
Assuming you have a duel core processor and so ran two instances of the CPU client and you got 10pph on each you would generate 20pph.
As this all shows the SMP client is the significantly the best way of turning time into folding. Next comes the GPU client which while out stripped by the SMP client easily beats the standard CPU client.
PS3 - King of Folding?
Now you may have read that PS3s are fantastic folding machines, and I cant deny it they are! Now the problem comes if your looking for maximum points that the PS3 is bench marked against a PS3 so you will be unable to achieve more than 900 points in a day for 37.5 pph.
While this is not to be sniffed at and if you have a PS3 your happy to fold on then please do, but I'm afraid the SMP client will net you more pph even on a slow (I would guess down to 2GHz) duel core.
Linux or Windows
Now Directhex has in another thread said that SMP units in Linux are significantly faster than under windows, and I am happy to believe this but have not tested for myself yet.
F@H state that the should be no difference between the speeds of Linux and Windows systems for the the clients. However, this was written before the introduction of the SMP client, so I would guess only applies to the CPU and GPU clients.
Final Thoughts
If you got this far and it all made sense then congratulations, hopefully you will now all run off and fold using the SMP client on your duel/quad core systems (and your PS3s while you wait for decent games to come out ). If you cant run the SMP client as you only have a single core CPU don't be put off, distributed computing is all about a lot of little bits adding up to a whole lot more!
Thanks for reading, if people have more times/cost per unit especially under Linux for SMP and for the single core that I can add in that would be great. I would also be interested in seeing how Macs fare in the SMP timing debate.