• 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.

Deadlines on a 500MHz rig.

D

DatHak512

Gawd
Joined
Jan 8, 2004
Messages
743
Just wondering about everyone's experinece here:
Do you think it would be smart to take only units without deadlines on my 500MHz PIII machine? (260MB RAM)? Right now i enabled big units and told the client 'no prefrence' when i came to choosing work units... and as a consequence i'm chewing my way through a 600 pointer right now. So that should take me a while. But for future refrence, what do you guys think?
 
if you are running FAH 24 hours without running anything else, you should be able to finish units on time. You will also get more workunits if you have set your work units to no preference. Most of the deadlines are set with a 200 mhz processor.
 
Who long is that 600 pointer going to take? I'm looking at grabbing ~10 400 mzh boxen and kinda was wondering the same deal.
 
The deadlines are not set with a 200 MHz processor, not by any means. Go read stanford's guidelines.

The 500 MHz machine should make deadlines if it is on 24/7.

You could always make it crunch timeless units.


From Stanford:

How do you set the deadlines for the work units?

Each work unit is benchmarked on a dedicated 2.8 GHz Pentium 4 machine with SSE2 disabled. Next, we apply this equation

timeout = 20 * (daysPerWU) + 2
deadline = max(30* (daysPerWU) + 2,10)

where daysPerWU is the number of days it took to complete the unit. The "+2" days is there to give an additional buffer for fast WUs (to allow for servers down, etc). If 30*daysPerWU is less than 10 days, we set the deadline to 10 days, as a minimum time for all projects. The timeout is the time at which the WU is resent to another client and the deadline is the last time which we will give stats credit for the WU.

Occasionally, deadlines may be set shorter or longer than the above calculation indicates, but the reason for having deadlines at all is that the sooner we get back work units, the sooner we can put the results to good use. The assignment server does take machine performance into account in making assignments, thereby allowing slower machines to receive more appropriate work units.
 
Personally all of the boxes that I have folding at 500Mhz or slower are all set for timeless units.

A. I dont have to worry about them misisng deadlines.
B. Id much rather see the box turn in a small workunit
every several days, than watch it gag on a 600 point
monstrocity for 2 or 3 weeks.

Besides as Stanford says, they get the best results (scientifically)
out of quick turnaround....not lots of points.

So Imho do science a favor and just run timeless on your slower
boxen.


 
marty9876 said:
Who long is that 600 pointer going to take? I'm looking at grabbing ~10 400 mzh boxen and kinda was wondering the same deal.
Click to expand...
Right now i'm looking at 585hrs, but yesterday it told me only like 158hrs (just a few days), so i'm guessing it'll be somewhere closer to 585hrs? That's about 25 days, but it's faster than the time-out for the work units, so i think i'll just keep on chugging here. Yeah, my machine is on 24/7: i'm setting it up just to be a file server in my dorm room, so hopefuly i won't have any problem meeting deadlines. I'm running Win2000Pro if anyone was intrested.
 
wraieghaeien said:
Besides as Stanford says, they get the best results (scientifically)
out of quick turnaround....not lots of points.
Click to expand...
Did they ever say why this was?
 
I have my dual P3 boxen running timeless units ( 500mhz x2 ) I just set it up a few days ago, they are still on the first units it downloaded. I am running two instances on that box. Its going to be about 3days to finish a unit. I would hate to see it running reg/big units
It would take 3weeks to a few months to finish.
u_DR_K13
 
Gk22CoE said:
Did they ever say why this was?
Click to expand...
The calculation isn't completely parallel; they basically need to finish one chunk of WUs before they can start on the next batch. So, if you've got the last WU sitting there in your machine for a long time, they can't finish out that batch.

As I understand it, anyways.
 
unhappy_mage said:
The calculation isn't completely parallel; they basically need to finish one chunk of WUs before they can start on the next batch. So, if you've got the last WU sitting there in your machine for a long time, they can't finish out that batch.

As I understand it, anyways.
Click to expand...
Hmm, maybe i'll stick it back for the 'timeless' preference then. :).
 
You must log in or register to reply here.
Back
Top