mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   GPU to 72 (https://www.mersenneforum.org/forumdisplay.php?f=95)
-   -   GPU to 72 status... (https://www.mersenneforum.org/showthread.php?t=16263)

chalsall 2013-12-30 04:53

[QUOTE=flashjh;363228]We mourn with you![/QUOTE]

Indeed. Very sorry if our suggestion you rejoin our party cost you. :sad:

nucleon 2013-12-30 10:22

[QUOTE=chalsall;363233]Indeed. Very sorry if our suggestion you rejoin our party cost you. :sad:[/QUOTE]

It's cool :)

It was the wind storm blowing my curtains into my fan that killed it :)

It was already crunching on P-1. Titans are pretty good at P-1. 70GHz-days/day (ish).

Here's the breakdown with mersenne primes
2x AMD HD7990s : TF 1300GHz-days/day
1x Titan : P-1 70GHz-days/day
2x GTX580s : TF 850GHz-days/day

-- Craig

LaurV 2013-12-30 13:06

[QUOTE=nucleon;363251]2x AMD HD7990s : TF 1300GHz-days/day
[/QUOTE]
Do you mean for one? :shock: (for two would be somehow too less, but for one is bloody high! I could get ~900G from mine, close to maximum 1.02T if I only do like 40M-45M expos to 69 bits - the most profitable variant; also, the 7970 Ghz edition gets 630G in average, doing 42M to 69 bits).

nucleon 2013-12-30 13:51

2x 7990

They run too hot, so they're clocked down a bit.

Currently running 65M@74bits.

-- Craig

Aramis Wyler 2013-12-30 14:24

I just wanted to make a note that I had thought I'd burned out my 580 from heat at one point (I run a 480 and a 580) because when I unplugeed the 580 the computer ran just fine. Turned out though that the heat had actually stressed the (1050 watt) power supply, and so it only had the juice to run one card after that. I replaced the power supply some time later, and poof, the 580 started running again. I was happy that the 580 wasn't dead, but somewhat upset that I lost almost a month of computing time on it.

kracker 2013-12-30 16:24

[QUOTE=nucleon;363262]2x 7990

They run too hot, so they're clocked down a bit.

Currently running 65M@74bits.

-- Craig[/QUOTE]

Yeah, I heard that was a issue with the heatsink (dual 7990's). Are they really close together?

nucleon 2013-12-30 22:21

[QUOTE=kracker;363276]Yeah, I heard that was a issue with the heatsink (dual 7990's). Are they really close together?[/QUOTE]

Yeah, after I wrote my post, I checked the cards. Yeah they are pretty close.

I can unplug one and put it in the pci-e x4 slot to give it more space.

-- Craig

kracker 2013-12-31 00:01

Tom's Hardware has a article about that here:

[URL="http://www.tomshardware.com/reviews/radeon-hd-7990-crossfire-overheat,3539.html"]http://www.tomshardware.com/reviews/radeon-hd-7990-crossfire-overheat,3539.html[/URL]

Putting more space should help but probably won't completely remove the problem.

chalsall 2013-12-31 00:11

[QUOTE=kracker;363317]Tom's Hardware has a article about that here:[/QUOTE]

This is an example of why I /so/ love "the empirical"! Theory is great and helpful, but it's only a theory.... :smile:

nucleon 2013-12-31 08:19

It seems the other pci-e slot isn't suitable.

It doesn't work quite well - speed per gpu drops to 150Ghz-d/day. (Typical is 325-340GHz-d/d)

I've installed msi afterburner to get better details on speed.

It seems it's running at defaults 950core, 1500mem.

Here is the ini file. I'm open to suggestions.

[CODE]Verbosity=2
SievePrimes=105000
SievePrimesAdjust=1
SievePrimesMin=5000
SievePrimesMax=200000
SieveSizeLimit=64
NumStreams=3
VectorSize=2
GridSize=3
WorkFile=worktodo.txt
ResultsFile=results.txt
Checkpoints=1
CheckpointDelay=300
Stages=0
StopAfterFactor=2
PrintMode=1
TimeStampInResults=1
ProgressHeader=Date Time | class Pct | time ETA | GHz-d/day Sieve Wait
ProgressFormat=%d %T | %C %p%% | %t %e | %g %s %W%%
AllowSleep=1
GPUType=AUTO
SieveCPUMask=0
SmallExp=0
SieveOnGPU=1
GPUSievePrimes=75000
GPUSieveSize=126
GPUSieveProcessSize=24
FlushInterval=3
TestSieveSizes=1,2,3,4,5,6,7,8,9,10,11,13,16,19,20,21,22,25,30,36,43,50,58,67,77,88,100,120,170
TestSievePrimes=254,310,1846,21814,67894,82000,111157,222222,444444,777777,1000000[/CODE]


-- Craig

LaurV 2013-12-31 09:03

From former discussions I remember that GPUProcessSize of 24 has a chance in 6 to miss a factor, I think you should use 16 or 32. I use 16. The only parameter which seems to influence the speed is the VectorSize (correctly set to 2 for GCN cards, the default of 4 is much worse). Also, primes, I go by the default 84486, but there is not much speed difference between 60, 80, 100k. I go by GPUType=GCN, but it does not really matter for speed, assuming it is AUTO and correctly detected as GCN.

What really makes a difference: go to the "performance" tag in the CCT and set the Overdrive/Power Control to about +15%, otherwise the card will try to keep the power consumption "in check" and throttle after few seconds (it shows that the GPU is used 99%, but in reality is only used 60-70%, the rest is throttling). For me, with 0% (or even +5%) it starts with almost 1T, but back off to ~600G in the first ~5 minutes. When I set it to +10%, still backs off after a longer time. With +15% it continues to run max speed. Of course, this means you need to properly cool the cards, but my AMD cards are air cooled too (I mean, they are not water cooled, only for the gtx stuff I use water cooling).

About the second slot, the card works on in x8 or even x4 slots, as mfakto does not have big traffic. You can check the bios, maybe the slot has strange settings there (different features disabled?).


All times are UTC. The time now is 23:17.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.