Author

Topic: Nicehash & GTX1070 - Higher mem or lower consumption (Read 266 times)

member
Activity: 336
Merit: 15
It is possible to achieve more than 180MH with a 6 card rig and consume around 700 watt. My optimal settings were with 61% PL. Just look out to not decrease it too much as you lose more hashrate than you save costs.

Also calculate if you really make less with more profitable coins considering the high energy costs.
legendary
Activity: 1106
Merit: 1014
1100mhz core clock (-..?)
2126mhz mem clock (+450)
812mV
I'm pretty sure you can set higher core clock even at 812 mV. 1.1 GHz is super low, try something around 1.5 GHz or even more.

Due to the high energy costs i was aiming for lowest consumption. Right now im thinking if it would make sense to give it a few more watts in order to get a higher clock/mem frequency to squeeze some more mh/s outta it.
Anyone having some expirience with this?
If you just have to mine ETH (and there are more profitable coins for 1070s out there), then memclock is the first thing you should worry about. Increase it as much as you can, higher memclock won't have nearly as much effect on the power consumption as it will on the hashrate.
full member
Activity: 127
Merit: 100
Good evening!

Im having a mining rig running with 6 gtx1070 (different brands).
Right now im using nicehash to get a steady income. I havnt tested it but mayone one of you already did and can answer my questions.

Right now im using MSI Afterburner and the manual frequency graph (ctrl+f), because the power target does not seem to work for me.
So right now all my cards are running with about:

1100mhz core clock (-..?)
2126mhz mem clock (+450)
812mV
90-110W power consumption

DaggerHashimoto ~26mh/s (ranges between 22-28) per card.

Im paying 0.27$ /kwH

Due to the high energy costs i was aiming for lowest consumption. Right now im thinking if it would make sense to give it a few more watts in order to get a higher clock/mem frequency to squeeze some more mh/s outta it.
Anyone having some expirience with this?

Jump to: