Bitcoin Forum
May 26, 2019, 12:25:33 PM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: « 1 ... 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 [158] 159 160 161 162 163 164 165 166 167 168 169 170 171 172 »
  Print  
Author Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows)  (Read 222159 times)
nUm81
Member
**
Offline Offline

Activity: 126
Merit: 11


View Profile WWW
May 02, 2018, 10:23:06 AM
 #3141

Its not really that simple, with the variable difficulty on pools, the pool that the dev mines to will have a different difficulty then the pool that you are mining too.

Cheers - nUm - SnowGem Dev
Website- https://snowgem.org/ | Join our Discord | Reddit
1558873533
Hero Member
*
Offline Offline

Posts: 1558873533

View Profile Personal Message (Offline)

Ignore
1558873533
Reply with quote  #2

1558873533
Report to moderator
1558873533
Hero Member
*
Offline Offline

Posts: 1558873533

View Profile Personal Message (Offline)

Ignore
1558873533
Reply with quote  #2

1558873533
Report to moderator
1558873533
Hero Member
*
Offline Offline

Posts: 1558873533

View Profile Personal Message (Offline)

Ignore
1558873533
Reply with quote  #2

1558873533
Report to moderator
PLAY OVER 3000 GAMES
LIGHTNING FAST WITHDRAWALS
PLAY NOW
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
korenchkin
Newbie
*
Offline Offline

Activity: 11
Merit: 0


View Profile
May 02, 2018, 11:10:16 AM
 #3142

Hello DSTM,

I don't mind paying 2% dev fee, however, I noticed the v0.6 is currently submitting more dev shares than it should. could you explain in detail how actually are you calculating it? well in a very simple calculation 2% could be 2 shares in 100 accepted shares? isn't it that simple?  Huh

Would appreciate your quick reply.

Thanks,

i believe the only way to do this is to dedicate 2% of time,but he probably needs lower difficulty so he gets some shares on the limited time(because only shares count on pool,so this may look like he mines more for himself),but that's just a guess
dstm
Full Member
***
Offline Offline

Activity: 350
Merit: 126


View Profile
May 02, 2018, 02:12:59 PM
 #3143

Hi all! First of all, sorry for my bad English.

I have a problem. my rig on win10, msi afterburner, zm 0.6, 8 nvidia GPU, at config i set temp limit 67.
While i use remote desktop (teamviewer) all works well, temp limit reduce  intensity at 67 and increase it back well.
But if i disconnected from  remote desktop intensity not increasing after reducing by temp limit  and working at low hashrate.When i just reconnect to remote desktop intensity increasing back. Who can help me?
p.s. the same situation at my 2 rig with 5 nvidia GPU.  

Are you sure the performance drop is related to temperature controller? i.e. does it really only happen with temp-target enabled?
Pls pm me your logfile, I'll check if there is something unusual.

I have the same problem on win7, zm 0.6, temp limit 70°, 100% fan.
When GPU start temperature control AND i don't watch it via Teamviewer, GPU usage drops and don't restore until i join TV again.
Here is log of GPU usage drops on temp° controller and restores when i joined TV.
Code:
2018-04-28 18:34:04|   GPU0  66C  Sol/s: 525.0  Sol/W: 2.71  Avg: 534.6  I/s: 287.1  Sh: 0.94   1.00 94  
2018-04-28 18:34:05|   GPU1  60C  Sol/s: 501.7  Sol/W: 3.33  Avg: 497.0  I/s: 266.2  Sh: 1.43   1.00 93  
2018-04-28 18:34:05|   GPU2  69C  Sol/s: 526.3  Sol/W: 2.74  Avg: 536.0  I/s: 287.3  Sh: 0.98   1.00 78  
2018-04-28 18:34:08|   GPU3  66C  Sol/s: 538.8  Sol/W: 2.74  Avg: 536.1  I/s: 287.1  Sh: 1.56   1.00 78  +
2018-04-28 18:34:10|   GPU4  64C  Sol/s: 475.5  Sol/W: 3.68  Avg: 487.3  I/s: 260.4  Sh: 0.85   1.00 78  ++
2018-04-28 18:34:10|   GPU5  69C  Sol/s: 544.5  Sol/W: 2.67  Avg: 536.1  I/s: 287.6  Sh: 1.07   1.00 93  +
2018-04-28 18:34:11|   ========== Sol/s: 3111.9 Sol/W: 2.98  Avg: 3127.1 I/s: 1675.7 Sh: 6.83   1.00 85
2018-04-28 18:34:24|   GPU0  66C  Sol/s: 535.6  Sol/W: 2.71  Avg: 534.7  I/s: 287.1  Sh: 0.92   1.00 94  
2018-04-28 18:34:24|#  GPU2  reached temperature target 70C
2018-04-28 18:34:24|#  GPU2  enabling temperature controller
2018-04-28 18:34:25|   GPU1  60C  Sol/s: 501.4  Sol/W: 3.33  Avg: 497.1  I/s: 266.2  Sh: 1.41   1.00 93  
2018-04-28 18:34:25|   GPU2  64C  Sol/s: 520.4  Sol/W: 2.74  Avg: 535.8  I/s: 276.6  Sh: 0.97   1.00 78  
2018-04-28 18:34:28|   GPU3  67C  Sol/s: 536.9  Sol/W: 2.74  Avg: 536.1  I/s: 287.1  Sh: 1.54   1.00 78  
2018-04-28 18:34:30|   GPU4  64C  Sol/s: 490.3  Sol/W: 3.68  Avg: 487.4  I/s: 260.4  Sh: 0.84   1.00 78  
2018-04-28 18:34:31|   GPU5  69C  Sol/s: 530.4  Sol/W: 2.67  Avg: 536.0  I/s: 287.6  Sh: 1.06   1.00 93  
2018-04-28 18:34:31|   ========== Sol/s: 3114.9 Sol/W: 2.98  Avg: 3127.0 I/s: 1665.0 Sh: 6.73   1.00 85
2018-04-28 18:34:44|>  GPU0  66C  Sol/s: 533.8  Sol/W: 2.71  Avg: 534.6  I/s: 286.9  Sh: 0.91   1.00 94  
2018-04-28 18:34:45|>  GPU1  60C  Sol/s: 494.6  Sol/W: 3.33  Avg: 497.0  I/s: 266.4  Sh: 1.39   1.00 93  
2018-04-28 18:34:46|>  GPU2  49C  Sol/s: 120.0  Sol/W: 2.74  Avg: 529.7  I/s: 64.1   Sh: 0.95   1.00 78  
2018-04-28 18:34:48|>  GPU3  67C  Sol/s: 536.2  Sol/W: 2.74  Avg: 536.1  I/s: 287.1  Sh: 1.52   1.00 78  
2018-04-28 18:34:51|>  GPU4  64C  Sol/s: 485.2  Sol/W: 3.68  Avg: 487.3  I/s: 260.4  Sh: 0.82   1.00 78  
2018-04-28 18:34:51|>  GPU5  69C  Sol/s: 536.8  Sol/W: 2.67  Avg: 536.0  I/s: 287.3  Sh: 1.08   1.00 78  +
2018-04-28 18:34:51|   ========== Sol/s: 2706.5 Sol/W: 2.98  Avg: 3120.9 I/s: 1452.2 Sh: 6.68   1.00 83
2018-04-28 18:35:04|>  GPU0  66C  Sol/s: 535.0  Sol/W: 2.71  Avg: 534.7  I/s: 287.1  Sh: 0.94   1.00 78  +
2018-04-28 18:35:05|>  GPU1  60C  Sol/s: 498.8  Sol/W: 3.33  Avg: 497.0  I/s: 266.0  Sh: 1.37   1.00 93  
2018-04-28 18:35:06|>  GPU2  45C  Sol/s: 120.2  Sol/W: 2.73  Avg: 523.9  I/s: 64.0   Sh: 0.98   1.00 78  +
2018-04-28 18:35:08|>  GPU3  67C  Sol/s: 537.0  Sol/W: 2.74  Avg: 536.1  I/s: 287.3  Sh: 1.50   1.00 78  
2018-04-28 18:35:11|>  GPU4  64C  Sol/s: 495.4  Sol/W: 3.69  Avg: 487.5  I/s: 260.4  Sh: 0.81   1.00 78  
2018-04-28 18:35:11|>  GPU5  69C  Sol/s: 536.2  Sol/W: 2.67  Avg: 536.0  I/s: 287.6  Sh: 1.07   1.00 78  
2018-04-28 18:35:11|   ========== Sol/s: 2722.7 Sol/W: 2.98  Avg: 3115.2 I/s: 1452.4 Sh: 6.67   1.00 80

2018-04-28 21:06:36|>  GPU0  65C  Sol/s: 534.2  Sol/W: 2.72  Avg: 535.5  I/s: 287.1  Sh: 1.27   1.00 93  
2018-04-28 21:06:36|>  GPU4  64C  Sol/s: 501.7  Sol/W: 3.64  Avg: 488.6  I/s: 262.4  Sh: 1.17   1.00 78  +
2018-04-28 21:06:37|>  GPU3  63C  Sol/s: 532.1  Sol/W: 2.75  Avg: 535.9  I/s: 286.9  Sh: 1.24   1.00 78  
2018-04-28 21:06:40|   GPU2  38C  Sol/s: 118.8  Sol/W: 2.26  Avg: 174.5  I/s: 64.0   Sh: 0.36   1.00 78  
2018-04-28 21:06:40|   GPU1  59C  Sol/s: 496.1  Sol/W: 3.32  Avg: 496.9  I/s: 266.2  Sh: 1.23   1.00 78  
2018-04-28 21:06:50|   GPU5  41C  Sol/s: 119.1  Sol/W: 2.37  Avg: 254.5  I/s: 64.0   Sh: 0.54   1.00 78  
2018-04-28 21:06:50|   ========== Sol/s: 2302.0 Sol/W: 2.84  Avg: 2485.9 I/s: 1230.4 Sh: 5.81   1.00 80
2018-04-28 21:06:56|   GPU0  65C  Sol/s: 539.4  Sol/W: 2.72  Avg: 535.5  I/s: 286.9  Sh: 1.27   1.00 93  
2018-04-28 21:06:56|   GPU4  64C  Sol/s: 486.7  Sol/W: 3.64  Avg: 488.6  I/s: 262.4  Sh: 1.17   1.00 93  +
2018-04-28 21:06:57|   GPU3  64C  Sol/s: 547.5  Sol/W: 2.75  Avg: 536.0  I/s: 286.9  Sh: 1.24   1.00 78  
2018-04-28 21:07:00|   GPU2  38C  Sol/s: 122.8  Sol/W: 2.26  Avg: 174.4  I/s: 64.0   Sh: 0.37   1.00 78  ++
2018-04-28 21:07:00|   GPU1  59C  Sol/s: 494.8  Sol/W: 3.32  Avg: 496.8  I/s: 266.2  Sh: 1.24   1.00 85  ++*
2018-04-28 21:07:10|   GPU5  50C  Sol/s: 211.3  Sol/W: 2.37  Avg: 254.4  I/s: 111.8  Sh: 0.55   1.00 78  +
2018-04-28 21:07:10|   ========== Sol/s: 2402.5 Sol/W: 2.84  Avg: 2485.8 I/s: 1278.1 Sh: 5.84   1.00 84
2018-04-28 21:07:16|   GPU0  65C  Sol/s: 539.9  Sol/W: 2.72  Avg: 535.5  I/s: 285.3  Sh: 1.27   1.00 93  
2018-04-28 21:07:16|   GPU4  64C  Sol/s: 480.4  Sol/W: 3.64  Avg: 488.6  I/s: 261.9  Sh: 1.17   1.00 93  
2018-04-28 21:07:17|   GPU3  64C  Sol/s: 533.1  Sol/W: 2.75  Avg: 536.0  I/s: 285.5  Sh: 1.24   1.00 78  
2018-04-28 21:07:20|>  GPU2  57C  Sol/s: 406.8  Sol/W: 2.26  Avg: 174.8  I/s: 220.4  Sh: 0.37   1.00 78  
2018-04-28 21:07:20|>  GPU1  59C  Sol/s: 499.1  Sol/W: 3.32  Avg: 496.9  I/s: 265.6  Sh: 1.24   1.00 85  
2018-04-28 21:07:30|>  GPU5  57C  Sol/s: 532.7  Sol/W: 2.37  Avg: 255.0  I/s: 288.2  Sh: 0.55   1.00 79  +
2018-04-28 21:07:30|   ========== Sol/s: 2992.1 Sol/W: 2.84  Avg: 2486.7 I/s: 1606.9 Sh: 5.83   1.00 84
2018-04-28 21:07:36|>  GPU0  64C  Sol/s: 524.3  Sol/W: 2.72  Avg: 535.5  I/s: 284.9  Sh: 1.27   1.00 93  
2018-04-28 21:07:36|>  GPU4  64C  Sol/s: 496.0  Sol/W: 3.64  Avg: 488.6  I/s: 261.8  Sh: 1.17   1.00 93  
2018-04-28 21:07:38|>  GPU3  64C  Sol/s: 538.1  Sol/W: 2.75  Avg: 536.0  I/s: 285.6  Sh: 1.23   1.00 78  
2018-04-28 21:07:40|   GPU2  62C  Sol/s: 528.3  Sol/W: 2.27  Avg: 175.5  I/s: 286.4  Sh: 0.38   1.00 80  ++
2018-04-28 21:07:40|   GPU1  59C  Sol/s: 488.7  Sol/W: 3.32  Avg: 496.8  I/s: 262.7  Sh: 1.24   1.00 85  
2018-04-28 21:07:50|   GPU5  60C  Sol/s: 533.1  Sol/W: 2.37  Avg: 255.5  I/s: 283.5  Sh: 0.55   1.00 79  
2018-04-28 21:07:50|   ========== Sol/s: 3108.5 Sol/W: 2.84  Avg: 2487.9 I/s: 1664.9 Sh: 5.83   1.00 84

And here is typical GPU usage and temp graphic:


One more question, dstm. Could you add temperature limit option for GPU emergency shutdown (like in Claymore)? The reason for having such option is that your temperature controller works best with 100% fan setting, but it destroy fan very quickly. So it's sometimes good to have PID on fan and hard temp° limit to be sure GPU will turn off if exceed the limit.

Concerning zm's temperature controller.
Fan speed of 100% isn't necessary required, it's more important to have a reasonable constant fan speed - otherwise you'll get two controlling loops - which isn't optimal. I've changed the description of the 'temp-target' option to reflect this in recent zm versions.

Emergency shutdown:
Yes, I can add something like this.
However what exactly should happen after the temp-limit is reached on one of the GPUs? should zm terminate immediately?
Also don't forget, a user-space program can't guarantee you to react properly with respect to this (the hardware or the driver can get unresponsive) - however it should work in most cases.
dstm
Full Member
***
Offline Offline

Activity: 350
Merit: 126


View Profile
May 02, 2018, 02:13:43 PM
 #3144

Is there a function in dstm to restart the computer if the mining speed falls under a select value?
In claymore you can set up that the miner restarts after 5min if the hash falls below the chosen value.

How can I set up this function in dstm, in the readme file they are no comment about this..

ZM doesn't have something like this.
I don't think this is a good idea. You could end up in a reboot loop - this can damage your hardware.
I think a better solution is to implement a notification system - e.g. ZM could execute a configurable script when certain conditions arise.
dstm
Full Member
***
Offline Offline

Activity: 350
Merit: 126


View Profile
May 02, 2018, 02:14:31 PM
 #3145

I would like to incorporate your miner into some software, but I really need to know immediately when shares are accepted. Any plans to implement a verbosity or similar?

I can add this if it's important - what's the use case for immediate notification of accepted shares?
dstm
Full Member
***
Offline Offline

Activity: 350
Merit: 126


View Profile
May 02, 2018, 02:15:24 PM
 #3146

Hello DSTM,

I don't mind paying 2% dev fee, however, I noticed the v0.6 is currently submitting more dev shares than it should. could you explain in detail how actually are you calculating it? well in a very simple calculation 2% could be 2 shares in 100 accepted shares? isn't it that simple?  Huh

Would appreciate your quick reply.

Thanks,

Yes ofc.

2% of the running time are used to calculate solutions for the dev shares.
The amount of submitted shares depends on the difficulty, which is set by the server.
So your example '2% could be 2 shares in 100 accepted shares?' is right for the case where the difficulty of 'your shares' is equal to the difficulty of the 'dev shares'.
Blast77
Newbie
*
Offline Offline

Activity: 8
Merit: 0


View Profile
May 02, 2018, 03:26:54 PM
Last edit: May 08, 2018, 11:01:09 PM by Blast77
 #3147

I tried the --temp-target flag the other day and it seems like the miner just ignores it.  Temps stayed far above the limit.  Running ethOS 1.3.1 and dstm 0.6.0.1.  Any clues?  Thx

ragefarm
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
May 02, 2018, 06:22:52 PM
 #3148

Hey DSTM, just PMed you in regards to some upgrades that I thought I may be able to contribute to your miner.  Thanks for all the work.
Borsiy
Newbie
*
Offline Offline

Activity: 13
Merit: 0


View Profile
May 02, 2018, 06:39:26 PM
 #3149

Emergency shutdown:
Yes, I can add something like this.
However what exactly should happen after the temp-limit is reached on one of the GPUs? should zm terminate immediately?
Also don't forget, a user-space program can't guarantee you to react properly with respect to this (the hardware or the driver can get unresponsive) - however it should work in most cases.
I'd say stop using overheated GPU and keep informing about it in console, like Claymore's or EWBF's behavior. I know, the driver or hardware will shutdown it in case of overheat, but 100° is not healthy.
Maybe --temp-target can handle sudden rise of temperature and we don't need the emergency shutdown at all, but it's just not obvious from the description.
msklogix
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
May 02, 2018, 09:31:22 PM
 #3150

Hello DSTM,

I don't mind paying 2% dev fee, however, I noticed the v0.6 is currently submitting more dev shares than it should. could you explain in detail how actually are you calculating it? well in a very simple calculation 2% could be 2 shares in 100 accepted shares? isn't it that simple?  Huh

Would appreciate your quick reply.

Thanks,

Yes ofc.

2% of the running time are used to calculate solutions for the dev shares.
The amount of submitted shares depends on the difficulty, which is set by the server.
So your example '2% could be 2 shares in 100 accepted shares?' is right for the case where the difficulty of 'your shares' is equal to the difficulty of the 'dev shares'.


Thanks for your reply... but I have another question, how could a difficulty of the 'dev shares' differ from the difficulty of 'my shares'?
From what I know and you also mentioned that the difficulty is set by the pool server. and only smallest hashes/Sols (which can possibly be accepted) are submitted to the server to lower the bandwidth of the network.
Doomkin
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
May 02, 2018, 10:10:12 PM
 #3151

Hello DSTM,

I don't mind paying 2% dev fee, however, I noticed the v0.6 is currently submitting more dev shares than it should. could you explain in detail how actually are you calculating it? well in a very simple calculation 2% could be 2 shares in 100 accepted shares? isn't it that simple?  Huh

Would appreciate your quick reply.

Thanks,

Yes ofc.

2% of the running time are used to calculate solutions for the dev shares.
The amount of submitted shares depends on the difficulty, which is set by the server.
So your example '2% could be 2 shares in 100 accepted shares?' is right for the case where the difficulty of 'your shares' is equal to the difficulty of the 'dev shares'.


Thanks for your reply... but I have another question, how could a difficulty of the 'dev shares' differ from the difficulty of 'my shares'?
From what I know and you also mentioned that the difficulty is set by the pool server. and only smallest hashes/Sols (which can possibly be accepted) are submitted to the server to lower the bandwidth of the network.

So when you're mining using ZM, You mine whatever Crypto you want that uses Equihash to resolve.  When the DevFee kicks in, it selects a specific server and difficulty to mine the dev fee (Which May or May not be what you are mining.)  Hope this helps

-Thanks DSTM for the Miner/Your effort
msklogix
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
May 02, 2018, 11:00:33 PM
 #3152

Hello DSTM,

I don't mind paying 2% dev fee, however, I noticed the v0.6 is currently submitting more dev shares than it should. could you explain in detail how actually are you calculating it? well in a very simple calculation 2% could be 2 shares in 100 accepted shares? isn't it that simple?  Huh

Would appreciate your quick reply.

Thanks,

Yes ofc.

2% of the running time are used to calculate solutions for the dev shares.
The amount of submitted shares depends on the difficulty, which is set by the server.
So your example '2% could be 2 shares in 100 accepted shares?' is right for the case where the difficulty of 'your shares' is equal to the difficulty of the 'dev shares'.


Thanks for your reply... but I have another question, how could a difficulty of the 'dev shares' differ from the difficulty of 'my shares'?
From what I know and you also mentioned that the difficulty is set by the pool server. and only smallest hashes/Sols (which can possibly be accepted) are submitted to the server to lower the bandwidth of the network.

So when you're mining using ZM, You mine whatever Crypto you want that uses Equihash to resolve.  When the DevFee kicks in, it selects a specific server and difficulty to mine the dev fee (Which May or May not be what you are mining.)  Hope this helps

-Thanks DSTM for the Miner/Your effort

Yes, it does! Thanks!
josegve
Newbie
*
Offline Offline

Activity: 5
Merit: 0


View Profile
May 03, 2018, 10:32:30 AM
 #3153

About the temp limit setting, doesn't MSI Afterburner do the same thing?
Keko Fdez
Jr. Member
*
Offline Offline

Activity: 108
Merit: 7


View Profile
May 03, 2018, 10:37:35 AM
 #3154

For people with NVIDIA cards specially those with GTX 1070 Ti.

Has someone tried the new drivers 397.31 released on the 25th of april? if so any improvements compared to previous version 391.35??

I have installed 391.35 and with 70%TDP, +200 clock and +700 memory I get 3090 average hashrate with 6 GTX 1070 Ti.

Thanks everyone

chaostic
Newbie
*
Offline Offline

Activity: 22
Merit: 2


View Profile
May 03, 2018, 04:09:25 PM
 #3155

How about a "Shutdown script" of some sort so that if it overheats for any reason, internet lags out for any reason for failover etc.., one that we can configure to for instance, restart the miner in 5mins or 8mins once network has become reconnected and or load an app like Afterburner, the computer restart idea is actually pretty good, just put an option for ppl if they dont wanna use it then they dont add the flag for it?
chaostic
Newbie
*
Offline Offline

Activity: 22
Merit: 2


View Profile
May 03, 2018, 04:15:28 PM
 #3156

For people with NVIDIA cards specially those with GTX 1070 Ti.

Has someone tried the new drivers 397.31 released on the 25th of april? if so any improvements compared to previous version 391.35??

I have installed 391.35 and with 70%TDP, +200 clock and +700 memory I get 3090 average hashrate with 6 GTX 1070 Ti.

Thanks everyone




yes I have, and its about the same, wasnt really that big of a downfall one the driver before that tho at least not enough to make me rollback a GPU driver, I use Kernel Mode, 91% TPD, +184/+852 on mine, i get around 538-540ish with my 1070 ti, u can take it atw up to 1000 at the TPD you're at tho lol i'd turn it up to 94-106% if i were u tho Grin
Keko Fdez
Jr. Member
*
Offline Offline

Activity: 108
Merit: 7


View Profile
May 03, 2018, 04:58:41 PM
 #3157

For people with NVIDIA cards specially those with GTX 1070 Ti.

Has someone tried the new drivers 397.31 released on the 25th of april? if so any improvements compared to previous version 391.35??

I have installed 391.35 and with 70%TDP, +200 clock and +700 memory I get 3090 average hashrate with 6 GTX 1070 Ti.

Thanks everyone




yes I have, and its about the same, wasnt really that big of a downfall one the driver before that tho at least not enough to make me rollback a GPU driver, I use Kernel Mode, 91% TPD, +184/+852 on mine, i get around 538-540ish with my 1070 ti, u can take it atw up to 1000 at the TPD you're at tho lol i'd turn it up to 94-106% if i were u tho Grin

No thanks

I can get the same performance you get with 80% TDP/ +200 clock/ +700 mem that is 530-535 sols/s ish using far less elecricity than what you are using. It actually seems you are wasting it so I assume you do not pay for it. I do not know what brand you are using but mines are EVGA and MSI and they do not like more than +750 mem. Combined clock and mem they do not like more than +220 clock/+730 mem otherwise they crash (at least that is my experience)

There is also a compromise between what you get from the cards, the electricity you pay and the life expectancy of the equipment and I would say with your settings last one is not going to be long enough to make profit out of them.

chaostic
Newbie
*
Offline Offline

Activity: 22
Merit: 2


View Profile
May 04, 2018, 04:30:16 PM
 #3158

For people with NVIDIA cards specially those with GTX 1070 Ti.

Has someone tried the new drivers 397.31 released on the 25th of april? if so any improvements compared to previous version 391.35??

I have installed 391.35 and with 70%TDP, +200 clock and +700 memory I get 3090 average hashrate with 6 GTX 1070 Ti.

Thanks everyone




yes I have, and its about the same, wasnt really that big of a downfall one the driver before that tho at least not enough to make me rollback a GPU driver, I use Kernel Mode, 91% TPD, +184/+852 on mine, i get around 538-540ish with my 1070 ti, u can take it atw up to 1000 at the TPD you're at tho lol i'd turn it up to 94-106% if i were u tho Grin

No thanks

I can get the same performance you get with 80% TDP/ +200 clock/ +700 mem that is 530-535 sols/s ish using far less elecricity than what you are using. It actually seems you are wasting it so I assume you do not pay for it. I do not know what brand you are using but mines are EVGA and MSI and they do not like more than +750 mem. Combined clock and mem they do not like more than +220 clock/+730 mem otherwise they crash (at least that is my experience)

There is also a compromise between what you get from the cards, the electricity you pay and the life expectancy of the equipment and I would say with your settings last one is not going to be long enough to make profit out of them.



You will not get the same hash rate, and you are right I do not pay for Power, however if I did i'd still want the most hashrate I can get, life expectancy of cards is also irrelevant to me, and turning it down to you're level wont help that cause any if at all, to each their own I guess, I'd just rather have better hash rates, I also wouldnt rollback a driver lol for a few hashes, but from the looks of it, since the Zcash Founder is a complete and utter Moron, we'll be hunting for a new coin to mine shortly.
Xman79
Jr. Member
*
Offline Offline

Activity: 62
Merit: 1


View Profile
May 04, 2018, 04:50:02 PM
 #3159

When V0.7 ?
alltero
Newbie
*
Offline Offline

Activity: 9
Merit: 0


View Profile
May 04, 2018, 06:20:31 PM
 #3160

When V0.7 ?
https://shop.bitmain.com/product/detail?pid=00020180503154806494uGcSyiu806FD&utm_source=twitter&utm_medium=social&utm_campaign=z9-mini-announcement
#AntminerZ9
https://forum.z.cash/t/let-s-talk-about-asic-mining/27353/635
Pages: « 1 ... 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 [158] 159 160 161 162 163 164 165 166 167 168 169 170 171 172 »
  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!