• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Will this box finish WU's fast enough?

L

liquidtrance123

2[H]4U
Joined
Aug 29, 2000
Messages
2,395
I have a dually 500mhz with 512mb of ram, i was wondering if i set affinity to run an instance of FAH on each CPU would it be fast enough to finish both WU's in time?
 
Anything over 200 Mhz should finish the work units in time if running 24/7.

You dont need to set the affinity for F@H to run propperly on a duallie folding box.

Luck.......:D
 
Based on the level of your question -
A qualified YES.
No need to set affininty.
Lot's of "rules for duals"
Separate instances, separate machine id's, local switch, no 2 GUI's.

Please ask if you have more questions.
 
Machine ID's are set in the client.cfg file. You will have a config file for each instance you are running ( run them in separate folders ).
Edit the file in the second instance so it reads "machineid=2" ( the first instance will say "machineid=1", in it's config file ).
Then I run them both with the "-local" flag.
 
Originally posted by Tigerbiten:

Anything over 200 Mhz should finish the work units in time if running 24/7.
Click to expand...
I don't know about that. I have a dual 233MMX that I tried running F@H WUs when I initially set it up a couple of months ago. KDFold, my monitoring program, displayed a finish time of several months for some of the biggest WUs. That would exceed the deadline. I have it running G@H WUs now instead.

Unless the monitoring program was estimating wrong, I think the viability threshold is probably somewhere north of a 300MHz 6th Gen processor.
 
Originally posted by BlownFuse
Machine ID's are set in the client.cfg file. You will have a config file for each instance you are running ( run them in separate folders ).
Edit the file in the second instance so it reads "machineid=2" ( the first instance will say "machineid=1", in it's config file ).
Then I run them both with the "-local" flag.
Click to expand...
WARNING
Don't edit with most text editors. It's best to create/edit the .cfg file using the flag "-config" or "-configonly".
Again, based on the level of your question - some more advice -
There are 2 types of WU:
genome - these are credited to project 799 and benefit science without a time limit on turning them in.
Gromacs and Tinker - these are proteins with time limits.

There are two type of time limits - Useful to science and useful for credit. Stanford assigns proteins out with a time limit as posted in the psummary table . If you do not turn it in by then they reassign it, and it is basically to late for science. However to keep your interest up they will still give you longer to turn it in. This "grace period" is generally equal to the first deadline.
Foe example - I just grabbed a p683_TZ2_NAT_EXP.
Looking at psummary it gives a deadline of 21 days.
Looking at unitinfo.txt:
Current Work Unit
-----------------
Name: p683_TZ2_NAT_EXP
Download time: January 23 16:57:30
Due time: March 3 16:57:30
Progress: 2% [__________]
Click to expand...
So if I turn it in in 21 days it's good for science, after that, up to March 3, it's good for credit only.

Unfortunately they do not have a good rule they follow for setting the time limit. Thus you get proteins like p686 worth 71 points due in 30 days, and proteins worth the same, like p687, due in 50 days (from psummary). Thus depending how you look at it and which one you get there is a deadline from 30 to 100 days for 71 points.

I personally have a Cely 300@450 which hopefully will be turning in one of those 71 pointers in about 15 days, if it stops crashing.
 
From Stanford's FAQ.
Each work unit is benchmarked on a dedicated 500 MHz Celeron machine without SSE/3DNow. We look at how many days it takes, and multiply this by 2.5.
Click to expand...

So if its a pure F@H box then anything over 200 Mhz should finish in time.
But then unless your getting free power I dont think its worth running a pure 200 Mhz folding box.
Any cycles needed to run other programs will obviously mean you need a faster cpu.

Luck....... :D
 
My experience is that a 200 Mhz cpu will complete WUs within the time limit if 24/7 and limited other use, except for those proteins that are 18-pointers. Those have a short time limit, and EMIII reliably reports they won't make the deadline. Indeed, even 333's won't make the deadline for those 18-point WUs.

95000.gif
 
Originally posted by Celerator:

My experience is that a 200 Mhz cpu will complete WUs within the time limit if 24/7 and limited other use, except for those proteins that are 18-pointers. Those have a short time limit, and EMIII reliably reports they won't make the deadline. Indeed, even 333's won't make the deadline for those 18-point WUs.
Click to expand...
But which is better for legacy systems? G@H or F@H WUs??

The average point value for a G@H WU is ~20 points. My dual P233MMX can complete approximately 3 WUs a month per processor (~6 WUs/mo). That comes out to ~60 pts/mo/CPU. If a typical F@H WU takes over a month to complete, even one of those 70 pointer F@H WUs won't provide better production in the long run. In addition, you risk not making the deadline or more importantly, not contributing to science. I say forget about F@H for machines with processors under ~350MHz. Run G@H instead.
 
good advice, apollo-- my P2 300 can barely make some of the shorter-deadline WU's on F@H, but has no trouble chewing through the longer duration units.
 
i have a dual 333 that runs folding basically 24/7 and it makes deadlines
 
Originally posted by liquidtrance123
So would i be able to run dual instances by setting affinty/machine IDs? one instance to each 500mhz cpu?
Click to expand...

you dont have to set affinity, just run two copies, make sure you give each one its own machine id, done
 
OK boys! its up and running:D I scrounged together some parts laying around and built a Dual 500mhz P3 Dell Precision 410. 512mb Memory. Its running 2 instances of F@H4 with the optimization strings added to both shortcuts and machine ID#'s 1 & 2
Its using up 100% of both CPU's so i'm guessing the affinity is automatic? Machine ID's setup right? Just wanna make sure!

:cool:

EDIT: BTW i blame you %*#&%-er's for getting me addicted lol j/k
 
I have a bunch of 400's to 600mhz systems here at work doing nothing at all, any chance i could cluster them together? or would it just be easier to setup individually?
 
You must log in or register to reply here.
Back
Top