GPU's again

WoZZeR

WoZZeR

WoZZeR

Associate
Joined
19 Jan 2007
Posts
2,068
Location
Northampton
I have started my first GPU WU this morning:

Code: 
 Project : 2737
Core	: Gromacs GPU
Frames : 100
Credit : 330
 
 
-- GPU 1 --
 
Min. Time / Frame : 7mn 54s - 601.52 ppd
Avg. Time / Frame : 7mn 54s - 601.52 ppd

I'll have a bash tomorrow at getting the 2nd GPU up and running, this one is using 50% of CPU power with CPU at 3.4Ghz(E6700) and GFX at 695 (GPU) and 1088 (RAM, DDR4)
 
What card are you using there?

The frame time looks a little on the slow side for that GPU core speed, though it depends what card/how many shaders etc...
Sometimes the first frame takes quite a bit longer than the rest too so it may get quicker still :)
 
I'm not sure if it's using that speed to crunch, in the ATI Overdrive bit it says just for 3D applications ? The temps are definately lower than they are in 3D mark and stuff like that.

The card is a Sapphire 1950XTX Toxic, I've left the Crossfire Dongle in but switched off Crossfire in the ATI menus so it should be off.

As always, all tips gratefully received, and uber tips especially welcome.
 
ahh right - in that case it's probably using 2D clocks since Folding doesn't trigger the 3D auto switching thingy.

I use ATI Tray Tools to clock my X1900XT to 630/730 manually which does the trick for me - not sure if it supports the 1950 or not, otherwise CCC may let you do it manually? :confused:


Whatever you do make sure you stop the client before you up the clock speed/voltage as if it's running at the time you'll probably lose the WU.

My X1900XT-512MB @ 630/730 with 1.4V Core
Project : 2737
Core : Gromacs GPU
Frames : 100
Credit : 330


-- X2-GPU --

Min. Time / Frame : 6mn 29s - 732.96 ppd
Avg. Time / Frame : 6mn 32s - 727.35 ppd
Click to expand...
 
I'll echo what Rich said. ATI overdrive doesn't recognise Folding as 3D. You're better off using ATI Tray Tools.

As a comparison, these are my X1900XTs - Abe is at 2D speeds and Millhouse is clocked to 662/828 using ATT (both with 4000+ San Diegos).

Project : 2737
Core : Gromacs GPU
Frames : 100
Credit : 330


-- //Abe/F@H/ --

Min. Time / Frame : 10mn 26s - 455.46 ppd
Avg. Time / Frame : 10mn 26s - 455.46 ppd


-- Millhouse --

Min. Time / Frame : 6mn 03s - 785.45 ppd
Avg. Time / Frame : 6mn 03s - 785.45 ppd
Click to expand...

Stan :)
 
I installed The Tray Tools, it looks complex, I will investigate it in more detail shortly. These cards seem like really good clockers, the temps are low and they have always been trouble free, so worth doing.

I didn't do anything to the cards at all just restarted the console leaving the settings as they were, when I restarted the console up it gave me this message:

Code: 
[11:55:20] Will resume from checkpoint file
[11:55:22] Working on 1258 p2737_GPUlambda
[11:55:23] Resuming from checkpoint
[11:55:23] Starting GUI Server
[11:55:23] Verified work/wudata_02.log
[11:55:23] File work/wudata_02.edr has changed since last checkpoint
[11:55:23] mdrun_gpu returned 114
[11:55:23] Going to send back what have done.
[11:55:23] logfile size: 16818
[11:55:23] - Writing 17356 bytes of core data to disk...
[11:55:23] Done: 16844 -> 3218 (compressed to 19.1 percent)
[11:55:23] ... Done.
[11:55:23] 
[11:55:23] Folding@home Core Shutdown: EARLY_UNIT_END
[11:55:25] CoreStatus = 72 (114)

Is that perhaps the writeback cache on the HD or a bug ?

So that's todays work down the pan, along with yesterdays.....
 
Last edited:
Ah, brilliant, top chap.:)

I shall fiddle with Tray Tools tonight and start up again in the morning, I can use -oneunit temporarily to avoid losing half WU's.
 
You must log in or register to reply here.
Back
Top Bottom