- Joined
- Nov 16, 2002
- Location
- Neenah, WI
Per member request, here is the beta of the thread :
Disclaimer! Read Before Posting!:
This thread was not intended to be an end-all solution for what to run on a given CPU. It is intended to help guide *most* new users onto the correct path. We could debate forever and never get anywhere. It's generalizing and YES, some machines are safe to run other things on, but again, this is assuming the worst about a given machine and not knowing everything about the machine.
If you have a legitimate correction let me know.
CPU and Folding at Home Flag/Option Matching.
**Thread under construction**
What Flags/Console are best for my machine?
This is not ment to be strictly followed, it's ment to point people in the right
direction, feel free to set whatever options/flags to whatever you want/feel would be best.
Every machine running should have the -verbosity 9 flag set. It makes it far easier to diagnose problems if the maximum amount of data is written to the log.
Non-Brand/Type Specific CPU's:
Not Listed:
Flags:
1ghz+
Less than 512mb RAM;
Any type of SSE or 3DNow!
Flags:
1ghz+
256mb+ but less than 512mb RAM;
Any type of SSE or 3DNow!
Flags:
Intel CPU's:
Pentium M, 1ghz+ Celeron(D/M), 1ghz+ Pentium III, Pentium 4, Pentium D
256mb+ but less than 512mb:
Flags:
Pentium M, 2.0ghz+ Celeron(D), Pentium 4, Pentium D
512mb or more RAM:
Flags:
AMD CPU's:
Turion 64, 1ghz+ Duron, Sempron 2500+ or higher, 1ghz+ Athlon(xp), Athlon 64, Athlon 64X2, Athlon FX
256mb+ but less than 512mb:
Flags:
Turion 64, Sempron 2800+ or higher, 1.2ghz+ Athlon(xp), Athlon 64, Athlon 64X2, Athlon FX
512mb or more RAM:
Flags:
Links and other sources related to Flags/Options:
note: the -forcesse is not supported by version 5.xx of the folding@home client
Future Updates:
Let me know if there is anything I'm missing, or you would like to change. Also thoughts would be appreciated.
Disclaimer! Read Before Posting!:
This thread was not intended to be an end-all solution for what to run on a given CPU. It is intended to help guide *most* new users onto the correct path. We could debate forever and never get anywhere. It's generalizing and YES, some machines are safe to run other things on, but again, this is assuming the worst about a given machine and not knowing everything about the machine.
If you have a legitimate correction let me know.
CPU and Folding at Home Flag/Option Matching.
**Thread under construction**
What Flags/Console are best for my machine?
This is not ment to be strictly followed, it's ment to point people in the right
direction, feel free to set whatever options/flags to whatever you want/feel would be best.
Every machine running should have the -verbosity 9 flag set. It makes it far easier to diagnose problems if the maximum amount of data is written to the log.
Non-Brand/Type Specific CPU's:
Not Listed:
Flags:
- -local
- bigpackets=no
- ignoredeadlines=no
**Notebooks Only** - [power]battery=yes
1ghz+
Less than 512mb RAM;
Any type of SSE or 3DNow!
Flags:
- -forceasm
- -local
- bigpackets=no
- ignoredeadlines=no
**Notebooks Only** - [power]battery=yes
1ghz+
256mb+ but less than 512mb RAM;
Any type of SSE or 3DNow!
Flags:
- -advmethods
- -forceasm
- -local
- bigpackets=no
- ignoredeadlines=no
**Notebooks Only** - [power]battery=yes
Intel CPU's:
Pentium M, 1ghz+ Celeron(D/M), 1ghz+ Pentium III, Pentium 4, Pentium D
256mb+ but less than 512mb:
Flags:
- -advmethods
- -forceasm
- -local
- bigpackets=no
- ignoredeadlines=no
**Notebooks Only** - [power]battery=yes
Pentium M, 2.0ghz+ Celeron(D), Pentium 4, Pentium D
512mb or more RAM:
Flags:
- -advmethods
- -forceasm
- -local
- bigpackets=yes
- ignoredeadlines=no
**Notebooks Only** - [power]battery=yes
AMD CPU's:
Turion 64, 1ghz+ Duron, Sempron 2500+ or higher, 1ghz+ Athlon(xp), Athlon 64, Athlon 64X2, Athlon FX
256mb+ but less than 512mb:
Flags:
- -advmethods
- -forceasm
- -local
- bigpackets=no
- ignoredeadlines=no
**Notebooks Only** - [power]battery=yes
Turion 64, Sempron 2800+ or higher, 1.2ghz+ Athlon(xp), Athlon 64, Athlon 64X2, Athlon FX
512mb or more RAM:
Flags:
- -advmethods
- -forceasm
- -local
- bigpackets=yes
- ignoredeadlines=no
**Notebooks Only** - [power]battery=yes
Links and other sources related to Flags/Options:
- A how to on setting up flags can be found here.
- A how to on editing the options (config file) can be found here. (Thread not up yet, will be soon, sorry)
- A how to on setting flags for the console at WIKIpedia can be found here[url]
[*]Here's a piece taken from Wedo's Ultimate FAH Install Guide. It outlines what each flag does really well. The original thread is located [url=http://www.ocforums.com/showthread.php?t=231247]here
Wedo's Ultimate FAH Install Guide said:Here is your guide to the flags:
- -local
Used with multiple cpu rigs (dually, HT, quad cpus etc) to set up FAH as one client per one cpu. If this flag isn't used on a dually and two instances are running, your rig will show up as running at 50% in task manager as both instances will split the processing power of one cpu leaving the other to sit at idle.
- -service
Sets FAH as a service. Very important flag that will tell your rig to use srvany.exe to run FAH4Console.exe as a service instead of running the client in the console window. Thereby keeping your rig folding even when no one is logged on.
- -forceSSE
Forces SSE use for AMD's. P4's do not need this flag, but it doesn't hurt so it's including in most automated FAH installs like the One-Click.
- -forceasm
Forces the use of 3DNow and SSE. In some instances, if a power failure occured, your computer locks up (not due to FAH), or your kid brother kicks over your tower, FAH will restart in a form of "safe mode" that doesn't use 3DNow/SSE. This will cause your machine to fold much slower so this flag forces the higher setting on no matter how the client was turned off previously.
- -advmethods
The gromacs flag. This flag tells FAH to only seek out Gromacs (a type of protein) from the Stanford servers. Gromacs used to be the end-all-be-all of point production. However, recent changes to the point value for Tinkers have made this flag counter-productive on AMD rigs.
- -verbosity 9
Gives you the uber update in your log files. More info will be written in case your having issues or are just interested in what FAH is doing.
note: the -forcesse is not supported by version 5.xx of the folding@home client
Future Updates:
- Add SMP
- Get new versions of the one click, with settings already in them for each different cpu type
- Finish this thing...
Let me know if there is anything I'm missing, or you would like to change. Also thoughts would be appreciated.
Last edited: