• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Confused about F@H work times and units

D

dnuggett

Diamond Member
Once again this DC project has me confused (apparently that's not hard to do). For some time I had been running the GUI w/ my laptop which is a 1.6 Celeron. It would turn in a work unit about once every 3 days worth almost predictably 70.90 points. This one started at 0/500. I built a new system a 2500+ oc'd to 3200+ at the FSB. This is Prime 95 stable overnight, so 10 or so hours. Here is where the confusion comes in. This system seems to be getting assigned WUs that start at 0/2500 and take about as long as the laptops 0/500 WUs take. Here's the kicker...... they are only worth 60 points!!!. There is another WU it gets that ends up resulting overnight in a 2 unit total and 64 points.

For the increase in power I have added, I am seeing nowhere near the results I expected. I mean the 0/2500 WU takes the same time as the 0/500 on my lappy but yeilds 10 less points. I would think that my 3200+ is turning in junk becasue of the OC, except it is Prime 95 stable. Have any of you guys faced this issue before?
 
<--- Quick looks at F@H screensaver, sees no mention of points.


Huh? Where's it say what's worth how many points?
 
Originally posted by: Jeff7
<--- Quick looks at F@H screensaver, sees no mention of points.


Huh? Where's it say what's worth how many points?
Click to expand...



Well you can follow it in the log included in the program files, or you can visit this link:

Stats link

Using that link you can see what work you have turned in for the day in total WUs and points.

EDIT: maybe that doesn't answer your question. The 0/500 or 0/2500 are not points but values used to calculate a % of work completed and on the GUI interface it is located under WU PROGRESS .
 
dnuggett, what ver of FaH are you running? Did you go into preferences and tell it only fah, etc...? Sounds like you got a bad download, or an old core unit. I'd delete your fah folder and redownload it.
 
RustyNale-

Well the version on the 3200+ is 4.0 and the version on the lappy is 3.24. Neither one of them had preferences on.
 
Thanks Rusty...

So I take it your Opteron has not had any of these probs? What times/points is it pulling off?
 
I've got 20 CPUs working on this, from a PPro200 to a AthlonXP2500+@2.31GHz (210FSB). Use v4 client on all with Gromacs 1.55 (12/22/03) core. -advmethods and -forcesse arguments. I had expected to climb much faster. Reviewing logs on various machines to see what kind of WUs are being turned in.

And the extremeoverclocking stats server seems overwhelmed very often. The "bugs, we have no bugs" page was funny the first 100 times.... 😕

My last 7 days of production. Funny, less points for 282WUs on 12/28 than 14 on 12/29. What's up with that?

01/02/04 269.90 7
01/01/04 413.82 9
12/31/03 122.55 3
12/30/03 453.19 11
12/29/03 529.33 14
12/28/03 506.76 282
12/27/03 756.71 59
 
IMHO, part of the problem is that the system F@H uses to determine points is a celeron 500.

A summary of the points for any individual WU can be found hereProject summary.

As for the 3200+, make sure you have the "-forcesse" and "-advmethods" flags enabled. If you don't use the "-forcesse" flag in version 4.0, F@H will default to 3DNow! optimizations, which will cut your production by at least 1/3.
 
Originally posted by: dnuggett
Thanks Rusty... So I take it your Opteron has not had any of these probs? What times/points is it pulling off?
Click to expand...

Since switching to -forcesse and advmethods with ver 4, I seem to be ( rough quess here ) averaging about 2 wu's a day with the Opteron, better if I stay off the comp---but then what's the use having it if not to enjoy it?? 😛

As for issues, I haven't had any problems that I could point at ver 4 for causing, all seems smooth...🙂
 
Right click the F@H item in the startup folder.

select "Properties"

add the -forcesse -advmethods to the end of the program in the "target" line.

Mine reads

"C:\Program Files\Folding@Home\winFAH.exe" -forcesse -advmethods

Do the same thing in the F@H entry on the start menu as well if you manually stop F@H and restart it.
 
I believe so, you should keep an eye on your log file for errors because the SSE will cause problems on some Athlons.

F@H defaults to 3Dnow! because some processors would crash while running SSE.

-forcesse is a version 4 command.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top