WU rate?

botheredbothered Manchester UK
edited November 2003 in Folding@Home
How long does it take, roughly, on average, round about, off the top of your head, to do a WU?
I used to fold for a short time on Icrontic and I'm sure I used to do much more than now. I've been at it for weeks and have only done five!
I know I've not got the fastest PC here but it's no slouch and it's on all day every day, though quite a lot of gaming goes on.
So roughly, generally, what's normal?

Comments

  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited November 2003
    Varies from wu to wu and depends on your system. Some have 400 frames that can go in less than 1min a frame and some have 100 that take like 6mins a frame. IMHO you should just set it as a service and forget about it. If you have any problems, then stop the service before doing something cpu intensive. Right now I'm on a WU that's 20min a frame, so that's gonna be awhile =/
  • edcentricedcentric near Milwaukee, Wisconsin Icrontian
    edited November 2003
    I believe that my 1.4 tbird gets about 25 points/day.
    Some wus take a few days and some just 12 hours.
    But the point output is fairly constant.

    Are you folding tinkers or gromacs??
  • mmonninmmonnin Centreville, VA
    edited November 2003
    Here is a Zip file of everything I have done lately. My computer the 2.14 and another 1800+ that was OCed part way thru somewhere. to like 1.7 or so. There is a genome service on my computer for backup as well.

    This is one great feature about EM3.
  • csimoncsimon Acadiana Icrontian
    edited November 2003
    what client and what flags are you using? maybe you can speed things up.
  • Straight_ManStraight_Man Geeky, in my own way Naples, FL Icrontian
    edited November 2003
    Gromacs units might be gettign bigger in terms of steps per frame. I have been gettting p1000+ WUs lately. These are 2.5 Million step units. Each frame is 1000 steps. 2500 frames per WU. 25 Frames per percent accomplished. But, they are running faster per frame than the older WUs. Thus, I am doing a WU every 10 hours to 18 hours depending on project details-- Tinkers take same box 26-28 hours to do.

    One thing, I am using the 4.00Pre1 client and it IS faster but seems to get bigger frame WUs than the old client did. The older client was getting more tinkers, the newer one almost ZERO tinkers but these huge things tuned for faster boxes and more vector calcs than not. If I do vector graphics work in Corel Draw, the time per percent DOUBLES. More vector calc skewed WUs, some greater time. But, these units are typically 51-62 pointers EACH.

    Try the new pre1 client, EXPECT to have to hand feed it a -forceSSE -advmethods (It does forceasm by itself on my Barton box, the Intel box cannot do -forceSSE but benefits from -forceasm).

    John.
  • profdlpprofdlp The Holy City Of Westlake, Ohio
    edited November 2003
    The bottom line is "Points-Per-Week", Not "WU's-Per-Week".

    Stanford is setting the point/WU ratio to reflect what they feel is a fair indication of what a WU is worth to their research. I have been having problems with one machine, which now receives a greater number of low-point WU's than it did previously. If you are producing a reasonable amount of points based on your computers potential I wouldn't let it worry you.

    Your computers "potential" can be maximized by following the tweaking tips others have mentioned. :thumbsup:
  • csimoncsimon Acadiana Icrontian
    edited November 2003
    Ageek had this to say
    ... the Intel box cannot do -forceSSE but benefits from -forceasm.

    really?
  • edited November 2003
    I imagine that -forceasm and -forceSSE on an Intel rig will accomplish the same thing with the beta version 4 of the client. The -forceasm is the flag that will make sure your proc uses the assembly loops native to the proc; 3DNow! for AMD and SSE for Intel. The -forceSSE flag should still activate SSE on Intel procs, but isn't specifically needed to use SSE like on an AMD proc to use SSE assembly loops.
Sign In or Register to comment.