Bitcoin Forum
December 09, 2016, 03:45:10 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 [7]  All
  Print  
Author Topic: Lowering mem clock to idle speeds SPEEDS UP Mh/s  (Read 37368 times)
SmokeAndMirrors
Full Member
***
Offline Offline

Activity: 168


View Profile
June 21, 2011, 12:41:19 AM
 #121

Naturally, memory clock wouldn't affect the hashes produced. This is not the memories job to provide calculations. The only thing you benefit from by lowering mem clocks is significant heat reduction produced by your gpu. Also, you may get more stale shares if you're in a pool as your gpu is taking that much longer to process and it tends to miss the last bit or so of a calculation. This is what generally causes a stale/invalid share (false information due to gpu leaving out a bit or two of info).

In my experience, lower mem clock to about 300 Mhz for a relatively stable experience. Doesn't cause too many invalid shares and may reduce your temp by about 8 degrees Celsius depending on your card.

Help Bitcoins by buying clothes, technology, books, etc. through people/stores that accept BTC. This will increase overall value of BTC as well as mitigate unnecessary bank transaction fees.

My address -
1EM9HGg1SEa5Bux1rVEPxGqGSfNTTc9EkC
1481298310
Hero Member
*
Offline Offline

Posts: 1481298310

View Profile Personal Message (Offline)

Ignore
1481298310
Reply with quote  #2

1481298310
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Zagitta
Member
**
Offline Offline

Activity: 84


View Profile
June 21, 2011, 01:39:29 AM
 #122

... Also, you may get more stale shares if you're in a pool as your gpu is taking that much longer to process and it tends to miss the last bit or so of a calculation. This is what generally causes a stale/invalid share (false information due to gpu leaving out a bit or two of info).
...

Don't spread bullshit like that, reducing the clock of GDDR ram, ram or any type of chip wouldn't make it "leave out a bit or two" (a FPGA or ASIC might do due to timeing issues but that would moste likely make it fail completly)
Secondly even if it did leave out bits the different mining applications are very unlikely to even accept them as shares and thus report them to the pool...
phelix
Legendary
*
Offline Offline

Activity: 1680


nmc:id/phelix


View Profile
June 23, 2011, 09:51:49 PM
 #123

Naturally, memory clock wouldn't affect the hashes produced. This is not the memories job to provide calculations. The only thing you benefit from by lowering mem clocks is significant heat reduction produced by your gpu. Also, you may get more stale shares if you're in a pool as your gpu is taking that much longer to process and it tends to miss the last bit or so of a calculation. This is what generally causes a stale/invalid share (false information due to gpu leaving out a bit or two of info).

In my experience, lower mem clock to about 300 Mhz for a relatively stable experience. Doesn't cause too many invalid shares and may reduce your temp by about 8 degrees Celsius depending on your card.
I am interested into anything that might help to reduce stales. Going up from 269 to 400 did not seem to result in less stales. I will run some more tests.

blockchained.com ■ bitcointalk top posts
PcChip
Sr. Member
****
Offline Offline

Activity: 294



View Profile
June 23, 2011, 10:51:03 PM
 #124

Naturally, memory clock wouldn't affect the hashes produced. This is not the memories job to provide calculations. The only thing you benefit from by lowering mem clocks is significant heat reduction produced by your gpu. Also, you may get more stale shares if you're in a pool as your gpu is taking that much longer to process and it tends to miss the last bit or so of a calculation. This is what generally causes a stale/invalid share (false information due to gpu leaving out a bit or two of info).

In my experience, lower mem clock to about 300 Mhz for a relatively stable experience. Doesn't cause too many invalid shares and may reduce your temp by about 8 degrees Celsius depending on your card.

Good sir, I do say you're quite skilled in the art of Talking Out Your Ass.

Reading your paragraph reminds me of when a woman goes to a mechanic, "he said my muffler bearings were going out, blinker fluid was low, and I somehow made it to the shop with only one transmission and need the second one put back in asap!"

All rates with Phoenix 1.50 / PhatK
------------------------------------------------------------------------------------------------------------------------------
5850 - 400 MH/s  |  5850 - 355 MH/s | 5830 - 310 MH/s  |  GTX570 - 115 MH/s | 5770 - 210 MH/s | 5770 - 200 MH/s
Pages: « 1 2 3 4 5 6 [7]  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!