Lowering mem clock to idle speeds SPEEDS UP Mh/s

[jasonk]

So I did the tweaks to afterburner cfg file, and was able to lower my mem clock from 1000Mhz to 500Mhz, but the slider will not allow for more.

I see several of you posting going down to the 200, 300 and 400Mhz range.  How?

I have a 5830 under Win7 64bit.  Thx.

[1714065065]

1714065065

[1714065065]

1714065065

[1714065065]

1714065065

[EpicBacon]

So I did the tweaks to afterburner cfg file, and was able to lower my mem clock from 1000Mhz to 500Mhz, but the slider will not allow for more.

I see several of you posting going down to the 200, 300 and 400Mhz range.  How?

I have a 5830 under Win7 64bit.  Thx.

Slide it to 500, hit apply, close msi afterburner. Then when you open msi again it should let you go down lower.

[dishwara]

So I did the tweaks to afterburner cfg file, and was able to lower my mem clock from 1000Mhz to 500Mhz, but the slider will not allow for more.

I see several of you posting going down to the 200, 300 and 400Mhz range.  How?

I have a 5830 under Win7 64bit.  Thx.

Slide it to 500, hit apply, close msi afterburner. Then when you open msi again it should let you go down lower.

+1

So far, i can't able to find a direct way to go 1038 & 360 directly.
The only way is to apply, restart & change.
So, you can't just start mining rig & go away. you have to change mem clk & after you can leave mining rig, until, it restarts again. 

[jasonk]

Cool.  Gained about 2-3M hashes by dropping it down to 339.  341 and 339 give me the same.  Anything slightly higher or lower give me like 1M less.

This also decreased my card power by 20W, and temperature by about 5C!  

Currently running a single 5830 @ 920Mhz.  Agression is at 7.  At 11 I will gain a few more M hashes.  I get 264Mhash/sec now.

[dishwara]

Cool.  Gained about 2-3M hashes by dropping it down to 339.  341 and 339 give me the same.  Anything slightly higher or lower give me like 1M less.

This also decreased my card power by 20W, and temperature by about 5C! 

Currently running a single 5830 @ 920Mhz.  Agression is at 7.  At 11 I will gain a few more M hashes.  I get 264Mhash/sec now.

Please try mem clk at this speed, 920/3 + 14, that's 320.66= 320 mhz & post how much Mhash/s u get.

[jasonk]

Cool.  Gained about 2-3M hashes by dropping it down to 339.  341 and 339 give me the same.  Anything slightly higher or lower give me like 1M less.

This also decreased my card power by 20W, and temperature by about 5C! 

Currently running a single 5830 @ 920Mhz.  Agression is at 7.  At 11 I will gain a few more M hashes.  I get 264Mhash/sec now.

Please try mem clk at this speed, 920/3 + 14, that's 320.66= 320 mhz & post how much Mhash/s u get.

At 920/320 I get 263-264.

At 925/324 I get 265-266.

[slurch]

Cool.  Gained about 2-3M hashes by dropping it down to 339.  341 and 339 give me the same.  Anything slightly higher or lower give me like 1M less.

This also decreased my card power by 20W, and temperature by about 5C!  

Currently running a single 5830 @ 920Mhz.  Agression is at 7.  At 11 I will gain a few more M hashes.  I get 264Mhash/sec now.

Please try mem clk at this speed, 920/3 + 14, that's 320.66= 320 mhz & post how much Mhash/s u get.

At 920/320 I get 263-264.

At 925/324 I get 265-266.

You might be able to OC that all the way up to 960. Hell, I saw Frankiebits say he had his at 1000 for a while...though I couldn't tell you how he did that. I run mine at 960, and I seem to have one of the most unstable systems on the forum in terms of getting the speeds everyone else is. 960 is damn stable, though. I get around 290 or so while using the computer, but I can't get my memory clock as low as I'd like. I'd say edge the core clock up by 5 and just keep an eye on it for a bit. Sometimes I'll launch like 3 Firefox tabs with YouTube videos just to make sure the system is stable before I OC it more.

Edit: If you do this, keep an eye on the temp. I use a tool called GPU Observer...it's a Windows sidebar gadget. Too lazy to link.

[jasonk]

Cool.  Gained about 2-3M hashes by dropping it down to 339.  341 and 339 give me the same.  Anything slightly higher or lower give me like 1M less.

This also decreased my card power by 20W, and temperature by about 5C!  

Currently running a single 5830 @ 920Mhz.  Agression is at 7.  At 11 I will gain a few more M hashes.  I get 264Mhash/sec now.

Please try mem clk at this speed, 920/3 + 14, that's 320.66= 320 mhz & post how much Mhash/s u get.

At 920/320 I get 263-264.

At 925/324 I get 265-266.

You might be able to OC that all the way up to 960. Hell, I saw Frankiebits say he had his at 1000 for a while...though I couldn't tell you how he did that. I run mine at 960, and I seem to have one of the most unstable systems on the forum in terms of getting the speeds everyone else is. 960 is damn stable, though. I get around 290 or so while using the computer, but I can't get my memory clock as low as I'd like. I'd say edge the core clock up by 5 and just keep an eye on it for a bit. Sometimes I'll launch like 3 Firefox tabs with YouTube videos just to make sure the system is stable before I OC it more.

Edit: If you do this, keep an eye on the temp. I use a tool called GPU Observer...it's a Windows sidebar gadget. Too lazy to link.

Wow... 960 seems kind of high. I may try it though.  I use MSI afterburner to monitor temps (dual monitors).  @ 925/324 @ 60% fan speed, I run at 61C.

[jasonk]

Man, how are you getting 290 Mhash/s with a 5830 @ 960Mhz.

I'm at 960Mhz now and averaging 275Mhash/s....

[nster]

Man, how are you getting 290 Mhash/s with a 5830 @ 960Mhz.

I'm at 960Mhz now and averaging 275Mhash/s....

whats your mem? are you using pheonix 1.4 or the newest poclbm?

[jasonk]

Man, how are you getting 290 Mhash/s with a 5830 @ 960Mhz.

I'm at 960Mhz now and averaging 275Mhash/s....

whats your mem? are you using pheonix 1.4 or the newest poclbm?

1.4.  Also, I forgot to mention I was using aggression = 7.  Now with Agression = 11 I'm at about 285Mhash/s.

Whats strange is I've run into a wall.  I can increase my core to 970 or 975 and get Zero increase in performance over 965.  Strange...

I'm now at 965/185 running strong @ 62C @ 60% fan.

Also, I'm running Win7 64bit with Stream SDK 2.4.  I read some people say 2.1 is better and I'll get better results?

[nster]

Man, how are you getting 290 Mhash/s with a 5830 @ 960Mhz.

I'm at 960Mhz now and averaging 275Mhash/s....

whats your mem? are you using pheonix 1.4 or the newest poclbm?

1.4.  Also, I forgot to mention I was using aggression = 7.  Now with Agression = 11 I'm at about 285Mhash/s.

Whats strange is I've run into a wall.  I can increase my core to 970 or 975 and get Zero increase in performance over 965.  Strange...

I'm now at 965/185 running strong @ 62C @ 60% fan.

Also, I'm running Win7 64bit with Stream SDK 2.4.  I read some people say 2.1 is better and I'll get better results?

yup with the 5XXX series, there is a specific sdk (2.1) and a Cat version (10.something) that is best

[nster]

After some more tweaking, my best for core 1020 is 344 on my 6870

[dishwara]

After some more tweaking, my best for core 1020 is 344 on my 6870

Impressive. Can you share that?
I am on win 7 32, with new poclbm or phoenix 1.4 ,in 6870,  only able to get 296 Mhash/s with 1029/359 or 301 Mhash/s with 1038/360.

[nster]

I meant 1020 core and 344 mem is my sweetspot lol

I only get 301~302 Mh/s

312 with phatk

[PcChip]

I didn't read the last 2 pages but I wanted to give my opinion of what is happening, it's either:

1. Ram Latency is being reduced (as was already mentioned)

2. Clock dividers being used between core and memory are hitting a favorable divider at the "sweet spot", favorable meaning most efficient


This kind of thing used to happen for example on p35 chipsets, there were some bus frequencies that while lower, were faster due to "memory latches" (latencies used) and ram dividers

[nster]

I didn't read the last 2 pages but I wanted to give my opinion of what is happening, it's either:

1. Ram Latency is being reduced (as was already mentioned)

2. Clock dividers being used between core and memory are hitting a favorable divider at the "sweet spot", favorable meaning most efficient


This kind of thing used to happen for example on p35 chipsets, there were some bus frequencies that while lower, were faster due to "memory latches" (latencies used) and ram dividers

I think it is number 2, as between 344 and 343 or 344 and 345, I lose ~2Mh/s

[pokermon919]

I can't seem to edit the msiafterburner file. It won't let me save. I tried to uninstall Catalyst but anything that will install drivers for my card always has catalyst in it. Can one of you kind souls please link me to driver only without catalyst along with the package? Thank you very much in advance!

[phelix]

for how long do you measure your hashrate? with -a 64 mine is still jumping arround randomly more than the difference a small change to the memclock makes.

[phelix]

for how long do you measure your hashrate? with -a 64 mine is still jumping arround randomly more than the difference a small change to the memclock makes.