Just installed folding@home
Medlock
Miramar, Florida Member
Umm... yeah I'm kinda new here. So to join team short-media i just enter 93 under team number in configuration? Is there anything I should know about this program, except that it'll rape my processor? :wow2: Any specific configuration options you recommend?
0
Comments
If so then add this: ' -advmethods -forcesse' to the shortcut in the startup folder. IN the target line in properties. So it would be like this: C:\FAH directory\fah.exe -advmethods -forcesse. If there are quotes put the new stuff after the target line.
What these do is get you doing semi-beta Work Units (WUs). They use SSE, and 2dnow! (if you have an AMD) on your CPU to go much faster and do a lot more work for Stanford. -forcesse will force you to use SSE on your CPU, the fastest of the optimizations.
Yup, got the pretty pictures. :bigggrin: I don't have an AMD processor, P4. They have support for SSE. Will it help it go faster? And why's it only usin' 50% of my processor. No hyper-threading support?
Oh!...and Welcome to the Greatest Team there is!
yes u can do it that way, you just need the -local switch for both the gui and console versions. this allows 2 F@H's to be running. the -local switch saves all the info in each individual folders.
example
C:\Programs\FAH1\FAH4Console.exe -local -advmethods
C:\Programs\FAH2\FAH4GUI.exe -local -advmethods
each version needs its own folder. i dont use the GUI version so as the how to with the switches i wouldnt know.
Make a new folder for the console. FAH2 or whatever you want to your program files or wherever you want. Download the console version in there. Make a shortcut to the client and do the same like you did for the Startup shortcut (IE the advmethods and forcesse things). This time add the '-local' tag behind the other 2 switches. Spaces between all of them. Click on the shortcut and configure the client. Make sure to enter yes to advances options and machine ID#2.
You can use the same username and Team #93.:)
If you have any more questions, keep asking.:)
Sally has 2 running (for now). Just loves it. Plenty of others running the same setup.
Oops, nearly forgot, welcome TheGr81.
Thanks guys, glad I am welcomed.
I'm sure one of the more "knowledgable ones" will help you out further before too long.
Gotta love Hyperthreading, 2 Work Units at the time with one proc.
Cheerio Jon
There is no option to change the machine ID# in the GUI. Thats why you can run 2 of them. They will both try to run the same machine ID and try to do the same WU and you would end up getting like hald the production but still be using 100% of the CPU.
Yep lots of stuff in the Everything about folding thread, including a link to Tray it!. It will take anything in your taskbar and put it in your system tray, by the clock.
My System 1 below is operating in hyperthreading mode, with two instances of Folding@Home employed. I've got one console version set to start Folding operations via the Startup folder; the second Folding console iteration is started via FireDaemon Light 1.6 Service Manager. In retrospect, it would have been easier to set this up with the -local flag. When I first discovered that my system was only utilizing 50% CPU capacity (right after I built the machine), I didn't know about the -local option.
Word of caution: hyperthreading with two instances of Folding can be unstable for the folding simulations under overclocking. If you overclock, ensure that your CPU temperature is not overly high and that you have high quality RAM. Previously I was running garden variety (Geil) RAM in System 1. After switching to my present RAM, I am having nearly flawless folding performance, even at the front side bus overclock of 25%.
Also, P4 Northwoods are very efficient with folding Gromacs, but are not up to par with AMD XP Athlons when folding "Tinker" proteins. The
-advmethods flag will cause your system to have a bias towards receiving Gromacs.
Console version how to:
Go to your Folding@Home installations folders. Open the Cleint.cfg folder. It should look something like this attached image. At the end where it reads "cpuusage=100", edit the numeral to read '80' (for each folding client). See what that does for temperatures and stability. Yes, it will slow production; but a slower stable machine will outperform a fast, unstable setup.
....Maybe if the option was there.
From client.cfg...
[settings]
username=TheGr8est12003
team=93
asknet=no
machineid=2
[http]
active=no
host=localhost
port=8080
usereg=no
Something wrong there? Maybe I should just reinstall the console and edit it at first configuration? It's odd. The other installation (GUI) has all that in client.cfg, and I did change it to 80%.
I would like to say that each process stays at 40%, but they seem to alternate between 30% and 50%. Is it supposed to do that? It's weird. But both of them together never take more than about 80% of my processor.
....Correction. Sometimes both of them make 60-100%. It kinda keeps jumping up and down.
Not so fast there, Young Skywalker! AMD Bartons leave any P4 version in the dust when processing Tinker proteins. Gromacs are best handled by P4s, especially if you can get two them running simultaneously in hyperthreading. (Hyperthreading is somewhat overrated; but there are some applications and multi-tasking environments where HT simply rocks.)
If your computer is currently folding the ~In Water proteins, then yes, that CPU usage fluctuation is completely normal. I think I've observed a couple of the other new Gromacs proteins causing similar results, souch as the ~fkfe-all (no, that's not an expletive!).
Sure, I don't think 52-56*C with a P4 Northwood is too high either; but under heavy load, like Folding's 100% CPU utilization, instability can creep in. Ageek was explaining that this instability may not be due to the CPU temperature itself, but to the CPU residual waste heat that radiates out to other components nearby - namely, the RAM. Beats me.
Oh man, I might just have to try that!
TheGr81, I think you are finding one of the reasons we enjoy Folding so much -- in pursuit of performance we have a real-world benchmark that provides all kinds of data for further tweaking and upgrading.
Res, nice to see you back here. Don't be a stranger, man.:)