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

Are the GPU cores variable length?

H

Hito Bahadur

[H]ard|DCer of the Month - December 2006
Joined
Jul 8, 2004
Messages
3,169
Just completed my first GPU core and it ended at 85 frames: (p2711)

12:22:58] Completed 82
[12:31:52] Completed 83
[12:40:46] Completed 84
[12:49:39] Completed 85
[15:04:05]
[15:04:05] Finished Work Unit:
[15:04:05] - Reading up to 45408 from "work/wudata_04.trr": Read 45408
[15:04:05] - Reading up to 970996 from "work/wudata_04.xtc": Read 970996
[15:04:05] logfile size: 35603
[15:04:05] Leaving Run
[15:04:06] - Writing 1053079 bytes of core data to disk...
[15:04:07] Done: 1052567 -> 1017218 (compressed to 96.6 percent)
[15:04:07] ... Done.
[15:04:07] - Shutting down core
[15:04:07]
[15:04:07] Folding@home Core Shutdown: FINISHED_UNIT
[15:04:09] CoreStatus = 64 (100)
[15:04:09] Sending work to server



Is this normal?
 
Agreed. Just noticed a 3 hour failure to post to the log and then it resumed. Must be a coding issue.
 
Hito Bahadur said:
Just completed my first GPU core and it ended at 85 frames
Is this normal?
Click to expand...

I guess you missed my note in this thread

Note: When you get to 85 frames and it appears the client has stopped, don't panic. All 4 of the WUs I've done so far stopped showing progress after 85 frames in the log, but the client is infact still processing the WU and all 4 WUs finished.
Click to expand...

ChelseaOilman

 
Nope, although things don't seem to be as bad as I originally thought:

P2711 seems to be a slower protein that some of the other 220 point proteins:

Where I was at 8min34sec for 2711, I am at 8min8sec for 2723. So the protein definately has something to do with it.

I don't seem to be memory bandwidth limited as raising my memory speed hasn't dramatically improved things whereas I have gotten an almost linear increase in performance from raising the CPU speed.

It may still be a driver or system install issue, but I don't have time right now to do a reload on that system as I am working on a takehome final, but that will happen within the next week. Right now I am just playing with clock speeds.
 
More data:

I've scaled my memory from 621 to 634.5 and my times have gone (for p2711) from 8.90min to 8.72min or a scale of about 95% which is pretty darn good. Hopefully there is more stable headroom on the card.
 
From Stanford

How will points be awarded? What kind of impact do we expect this to have on work units and Folding team scores?
We will continue to award points in the same method as we’ve always used in Folding@Home. To award points for a WU, the WU is run on a benchmark machine. The points are currently awarded as 110 points/day as timed on the benchmark machine. We will continue with this method of calibrating points by adding an ATI X1900XT GPU to the new benchmark machine (otherwise, without a GPU, we could not benchmark GPU WU's on the benchmark machine!). Since Core_10 GPU WU's cannot be processed on the CPU alone, we must assign a new set of points for GPU WUs, and we are setting that to 440 points/day to reflect the added resources that GPU donors give to FAH.
 
You must log in or register to reply here.
Back
Top