how-to block ads
|
| | | | FAQ Revisions | Editors: Icarus  , sortofageek , Santa Fe , mouseferatu , Gizmo , mig
Last modified on 2009-06-24 21:01:04
| |
|
|
2.4 Tips n Tricks·Can I run more than one Distributed Computing project at the same time?
·Does F@H affect System Restore in WinXP
·F@H and Hyperthreading?
·How do I put the FAH console client in the system tray?
·How do I set up the FAH client on another computer?
·How do I set up multiple FAH clients on the same machine?
·How do I use qd to debug the FAH client?
·I have a dial-up modem - How do I set it up to auto-dial?
·Is it better to run two single processors or a dual processor machine?
·What can I do to make my computer fold faster?
| | | There are ONLY A FEW instances when it is feasible to run more than one project at a time. IE... VERY fast system, plenty of RAM, and knowing that the work units will complete in the alloted time frame allowed.
Some clients play nice together, others do not.
With folding and genoming the priorities are set low, so they will always take a back seat to WHATEVER your computer is doing. They will work, but for folding this usually means that the larger WU's that you are working on will not finish in the time allowed by Stanford. Rendering the WU useless and Stanford will not use the work.
IT IS NOT RECOMMENDED TO RUN MORE THAN ONE PROJECT AT A TIME PER SYSTEM.
If you wish to contribute to more than one project it is best if you switch the projects off, a week of one then a week of another, and so on.
Exception: Dual CPU systems run two clients only slightly slower per CPU than a single CPU system of same speed. You would actually be wasting cycles to run only one client on a multiple processor system.
 feedback form
 feedback form
by SueN edited by wafen
last modified: 2005-02-19 21:19:51 | | | If you are running any distributed Computer program it would be wise to get in the habit of creating your own Restore Points manually before adding software or making any major changes, and also on a regular basis.
--------------------------------------------------------------------------------
From "Frequently Asked Questions Regarding System Restore in Windows XP" at the MS TechNet site
• System Restore requires the machine to be in an idle state to create system check points. This is by design so that System Restore never intrudes when the user is using the machine by taking processing power to create a system checkpoint. Hence, if system restore never sees any idle time on the machine, it will not be able to create System Checkpoints. Often users may have some application which is also operating during idle time like a virus scanner or disk utility software. This again may cause System Restore to never get any idle time. Try disabling any software you may have had running at idle time and see if that solves your problem, for e.g. Running the software SetiSpy has been known to cause this issue.
--------------------------------------------------------------------------------
More info here.
--
feedback form
feedback form
by rfhar edited by mattmag
last modified: 2004-07-16 09:33:05 | | | Recently, a couple of questions have come up about Folding At Home and the new Hyperthreading technology available with the Intel processors.
Q.1. F@H only registers 50% on my CPU usage meter. Can I make it use 100%?
A.1. You can turn off the Hyperthreading, but this apparently makes little to no difference to the frame time. Don't ask me why - it's too horribly complex to answer!
Q.2. OK, so if I'm going to use Hyperthreading, what can I do to make sure I'm utilizing (see I can spell American!) all of my CPU's potential?
A.2. The best way is to run two instances of the F@H client. This is particularly easy to do. Just follow FAQ 3015 How do I setup multiple FAH clients on the same machine? and you'll be folding to maximum potential in no time!
feedback form
feedback form
by Rockster edited by wafen
last modified: 2005-08-24 13:49:24 | | | To move the FAH console release from the taskbar to the system tray, you will need a program like TRAYIT or 4t Tray Minimizer.
TrayIT
To use TRAYIT, create a directory for it and unzip the archive into that directory. Create a shortcut to the executable and run it. When the program opens, click START USING TRAYIT.
Now click on your FAH client on the taskbar to open it up on your desktop. RIGHT-CLICK the [X] in the upper right hand corner
and the program will drop into your system tray. To open it back up, simply click the icon in your tray. To return it to the tray, RIGHT-CLICK the [X] again.
feedback form
feedback form
by Spectre edited by MstrBlstr0
last modified: 2003-02-08 16:29:53 | | | To setup the client on another computer, just follow the "How to install and setup", in section 2.1, for that client.
* The important thing to note here is to use the "same username and team number".
The "userid" number will be different!
feedback form
feedback form
by Gizmo edited by sortofageek
last modified: 2004-05-20 17:26:21 | | | Multiple graphical (GUI) clients can not be run on the same machine, at this time.
It is important to note that your user name and team number will be the same for all instances, the userID will be the same for all clients on one computer (registry entry at time of first client install) but the Machine ID must be unique for each of the clients! First client installed should be configured as Machine ID 1, second should be Machine ID 2 and so on up to eight clients on one computer.
You will also need to create multiple FAH shortcuts (e.g. FAH1 and FAH2) on your desktop. And, it is very important that you use the -local switch in each of the FAH shortcuts!!!
| For dual processor systems: |
When you configure your clients, make sure each client has a different Machine ID#.
To do this, type yes for Change advanced options, and make sure client one has Machine ID 1.
In client two, go to Machine ID, and change to 2.
If you don't do this, you will most likely only get credit for one Work Unit.
You can set "affinity" for dual processor machines(assigning each wu to a particular processor), but with today's newer technology it is not necessary. If you set affinity, you must do it on both the console.exe and the Core.exe.
feedback form
feedback form
by Gizmo edited by sortofageek
last modified: 2006-06-03 21:34:27 | | | The FAH Wiki Answer
feedback form
feedback form
by sortofageek | | | Setup your dial-up to auto-login:
1. For WinME:
a. Highlight the dial-up connection icon in the dial-up networking folder.
b. Right click and select properties.
c. Select the "Security" tab.
d. Fill in you username and password.
e. Check the box "Connect Automatically".
2. Internet browser setup (WinME):
a. Select "Tools".
b. Select "Internet options".
c. Select "Connections".
d. Check box "Always dial my default connection".
e. Click on "Settings".
f. Enter you name and password.
g. Click on "Properties".
h. "Connection using":, Click on "Configure".
i. Select Connection tab.
j. Check box "Disconnect a call if idle for" and enter a value of 5 to 10 minutes. Click "OK". You may have to adjust it up or down later.
k. Select "Dialing tab".
l. Check box "Enable idle disconnect".
m. Check box "Don't prompt before disconnecting".
n. Check box "Disconnect when connection may not be needed.
1. For Win98:
a. Highlight the default dial-up connection icon in the dialup networking folder.
b. Right click and select properties.
c. Click "Connections".
d. Select "Settings".
e. Un-check "prompt for information before dialing".
2. Internet browser setup (Win98):
a. Select "Tools".
b. Select "Internet Options".
c. Select the "Connections" tab.
d. Check box "Always dial my default connection".
e. Select "Setting".
f. Enter your name and password.
g. Select "Advanced".
h. Check box "disconnect when connection may no longer be needed".
i. Check box "disconnect if idle for" and enter a value of 5 to 10 minutes. You may have to adjust it up or down later.
3. Set the idle timeout for your modem:
a. Go to Control Panel and click on Modems.
b. Select "Properties".
c. Select the "Connections" tab.
d. Select "Disconnect a call if idle for more than:" and enter a value of 5 to 10 minutes. You may have to adjust it up or down later.
Note: To test your auto dial-up and timeout disconnect setup, use your browser and make sure you are not connected to the Internet when you start.
You are now setup, so when your client needs to transmit a completed work unit your system will detect the need to connect and will auto-log you into your ISP, the client will transmit and receive work, and after 'x' minutes of being idle the modem will disconnect.
feedback form
feedback form
by Gizmo edited by wafen
last modified: 2002-11-03 21:56:18 | | | You can get information about running single processor machines versus dual processor machines here.
feedback form
feedback form
by Sheesh edited by nozero
last modified: 2003-06-11 19:27:17 | | | There are a number of things that will adversely affect your folding efficiency:
[1] CPU intensive games and programs
[2] Screensavers
[3] Power management
[4] Other DC clients running simultaneously
[5] Multiple CORE_65.EXE files running simultaneously
The Folding@Home client relies on idle cpu cycles to function. When cpu hungry programs, like a web browser or game are running, these programs eat into the idle cpu cycles, essentially slowing down how fast the folding clients crunch data. The more these programs run, the longer it will take for the client to complete its work. Occassional gaming or browsing will generally have little effect on the folding efficiency.
The Folding@Home client does write data to your hard drive from time to time, so for best system speed, its a good idea to disable hard drive parking or drive spin down in your power management in Windows:
Using cpu intensive screensavers while the folding client is running also taps into your precious idle cpu cycles. If your monitor is a power saving monitor or has this capability:
You can simply program power management to turn off your monitor after a set time, like a couple hours. The alternative would be to simply shut off your monitor manually or turning down the brightness.
Another thing to check if your system appears to be processing work REAL slowly is to see if there is more than one instance of CORE_65.EXE currently running. This file is the program that crunches the workunit. Sometimes when the client is shut down improperly, this program can remain running in memory. When you restart the client, it will execute another instance of this program, so you have it running twice, which will cut work production in half and most likely corrupt the data you are processing. A good program to check running tasks on your computer is TaskInfo.
Running multiple distributed computing projects simultaneously also adversely affects both project's clients. If you are involved in more than 1 project, like Seti@Home, Genome@Home, United Devices, Distributed Computing, and others; it is best to stick to 1 client at a time. Run 1 project for awhile, then switch to another for awhile. Just remember than Folding@Home's workunits can expire, so if you shut the client down for more than a few days, you should delete the workunit when you restart the client. Just go to the client's WORK dir and delete all the files there, and delete the QUEUE.DAT file in your Folding@Home directory, then restart the client to receive new work.
The speed or amount of RAM in your computer has very little impact on folding speed. However, a computer with limitted RAM will fold slower if alot of other programs are running and eating up all the free memory. The key to folding is the processor's FPU, or floating point unit speed. The faster the FPU speed, the faster you fold. As a general rule, the AMD processors are best designed for these projects. Intels are excellent as well, but the AMD chips are more efficient in this case.
These are some other things Ive discovered when it comes to folding and genoming efficiency:
[1] Screensavers that blank the monitor have NO EFFECT on client speed.
[2] Screensavers like Window's Starfield Simulation, 3D pipes... have a VERY SMALL effect on folding [a couple secs a frame]
[3] Running the FAH GUI release maximized on your desktop is only SLIGHTLY slower than the CONSOLE release [10 secs per frame max]
[4] Running FAH with EM3 or KDFOLD displayed on the desktop is only SLIGHTLY slower than running it in the tray.
[5] Running 16-bit games like DOOM, DUKE3D, or [in my son's case] ROM Emulators DRASTICALLY slow the clients. I saw GAH sequences go from 1 hour to 10+ hours while running a DOS based game.
[6] Surfing the web and visiting sites heavy with JAVA and FLASH animations is almost as bad as the 16-bit games. The clients were taking serious speed hits when my daughter was on the animation ridden NICK.COM site.
[7] RAM speed or amount of RAM doesnt seem to have any effect on client speed [tho I suppose more RAM does make the client run faster when you use the computer for other things besides FAH and GAH].
[8] AMDs fold better than INTELs [but we all knew this]. Its due to the way the AMDs floating point units are handled. They are better designed in this way.
feedback form
feedback form
by Spectre edited by MstrBlstr0
last modified: 2002-11-11 01:56:04 |
|
