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

Work Unit

Rtstrider

Gawd
Joined
Dec 3, 2004
Messages
597
How long does it typically take for a work unit to be processed...It's taking me 4 1/2 days...Is this normal?
 
Rtstrider said:
How long does it typically take for a work unit to be processed...It's taking me 4 1/2 days...Is this normal?
Depends on the size of the work unit and the processor you're using. I've got a 600 pointer going on an Athlon 1200 and it's taking 5-6 days.

Also, are you using the console or graphical version? The console version is much faster - especially if you run it 24/7 allowing it 100% of your idle processes.

 
Your system should be able to pull QMDs if you have the flags set correctly. My system can handle one in just under 2 days, with a second thread of F@H running as a service. Are you forcing the SSE2 to kick on? The difference in GHz isn't that much so I would think they would be pretty close.
 
It also depends on what else you are doing on your machine. If you do a lot of gaming, that will eat up CPU cycles so folding can't do much if anything then.

Another thing we need to know is if you leave your system on 24/7. For most of us, that is just a given and we normally don't think to ask it. But if you only have the system on when you are using it, it will increase processing times a lot.

 
can you post some of the "FAHlog.txt" file?


Keep on Folding!! For the [H]orde!!

 
Rtstrider said:
Yeah the systems on 24/7 the only thing it's used for is a print server....

It's safe to assume this isn't the rig in your sig correct?

If it is a different one, please give us the specs, as slower machines, say less than 1.5GHz tend to really chug when it gets to folding.


 
Here's the system specs...

AMD 1700
1 gb patriot ddr pc3200 value ram
Biostar mb nforce 2 chipset with onboard geforce 4
1 160gb 7200 RPM western digital hd


Now I can overclock the amd to 1.8 but I've read too many horror stories using the value ram and mb I'm using....
 
Rtstrider said:
Here's the system specs...

AMD 1700
1 gb patriot ddr pc3200 value ram
Biostar mb nforce 2 chipset with onboard geforce 4
1 160gb 7200 RPM western digital hd


Now I can overclock the amd to 1.8 but I've read too many horror stories using the value ram and mb I'm using....

actually that's about right. I have a 1700+ which I use regularly and you are right on the money for most of the work units. :)

 
Cool cool, and I'm running in Graphical mode...Umm...Would I benefit more from console or graphical mode with my current folding setup?
 
Rtstrider said:
Cool cool, and I'm running in Graphical mode...Umm...Would I benefit more from console or graphical mode with my current folding setup?
Console is always better.
 
Rtstrider said:
Cool cool, and I'm running in Graphical mode...Umm...Would I benefit more from console or graphical mode with my current folding setup?

Running with the console is by far the preferred method of running F@H. You get back the cycles that the graphical uses to draw the protein, and it is many more times better stability wise. Graphical tends to take issue with any apps or games that use the OpenGL subsytem, so its just one more possible problem you don't have to worry about.

 
I believe you should be able to delete the winfah.exe and replace it with the console exe and start up where the graphical version left off. Just in case I am wrong, back up the directory first.

 
Back
Top