Pages:
Author

Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) - page 72. (Read 224961 times)

member
Activity: 154
Merit: 10
Thought I would give dtsm a try for mining zencash have to say I'm pretty impressed a massive gain in sols. Hitting over 310 with a gtx 1060 3gb.

Holy cow, amazing.

What model? On what clocks you get that?
full member
Activity: 729
Merit: 114
Agreed! I was pleasantly surprised as well. Managed to tweak overclock settings even further compared to ewbf/ccminer attempts. Running 6 1070s (zclassic):

Code:
2018-01-01 10:00:28 AM|   GPU1  52C  Sol/s: 485.7  Sol/W: 3.59  Avg: 483.6  I/s: 259.1  Sh: 1.12   0.99 195
2018-01-01 10:00:30 AM|   GPU2  58C  Sol/s: 481.0  Sol/W: 3.61  Avg: 486.6  I/s: 260.8  Sh: 1.21   1.00 197 +
2018-01-01 10:00:38 AM|   GPU4  58C  Sol/s: 484.0  Sol/W: 3.62  Avg: 487.4  I/s: 261.2  Sh: 1.19   0.99 285
2018-01-01 10:00:43 AM|   GPU0  46C  Sol/s: 478.8  Sol/W: 3.64  Avg: 489.8  I/s: 262.5  Sh: 1.22   1.00 202 +
2018-01-01 10:00:43 AM|   GPU3  40C  Sol/s: 492.8  Sol/W: 3.63  Avg: 488.6  I/s: 261.8  Sh: 1.19   1.00 197
2018-01-01 10:00:45 AM|   GPU5  57C  Sol/s: 494.0  Sol/W: 3.62  Avg: 487.2  I/s: 261.0  Sh: 1.27   1.00 202 +
2018-01-01 10:00:45 AM|   ========== Sol/s: 2916.3 Sol/W: 3.62  Avg: 2923.2 I/s: 1566.3 Sh: 7.21   1.00 213

Do you mind sharing your OC settings? My current setting only gives me 460-470 Sol/s with 3.0-3.1 Sol/W...
Also how do you get to display the date and time?

Try +135 core, +600-750 on memory and 66-70% PL.  for date and time it's parameter --time in config file.  The below is a EVGA 1070 SC at 66%PL

ID   DEVICE NAME   °C   ∅ SOL/S   ∅ SOL/W   ∅ WATT   SHARES   LAT
0   GeForce GTX 1070   48   461.25   4.38   105.23   36 / 0   125
1   GeForce GTX 1060 6GB   62   303.83   3.86   78.77   28 / 0   125
2   GeForce GTX 1060 6GB   60   301.28   3.84   78.45   18 / 0   117
Total   -   1066.36   4.03   262.45   82 / 0   122
newbie
Activity: 64
Merit: 0
Agreed! I was pleasantly surprised as well. Managed to tweak overclock settings even further compared to ewbf/ccminer attempts. Running 6 1070s (zclassic):

Code:
2018-01-01 10:00:28 AM|   GPU1  52C  Sol/s: 485.7  Sol/W: 3.59  Avg: 483.6  I/s: 259.1  Sh: 1.12   0.99 195
2018-01-01 10:00:30 AM|   GPU2  58C  Sol/s: 481.0  Sol/W: 3.61  Avg: 486.6  I/s: 260.8  Sh: 1.21   1.00 197 +
2018-01-01 10:00:38 AM|   GPU4  58C  Sol/s: 484.0  Sol/W: 3.62  Avg: 487.4  I/s: 261.2  Sh: 1.19   0.99 285
2018-01-01 10:00:43 AM|   GPU0  46C  Sol/s: 478.8  Sol/W: 3.64  Avg: 489.8  I/s: 262.5  Sh: 1.22   1.00 202 +
2018-01-01 10:00:43 AM|   GPU3  40C  Sol/s: 492.8  Sol/W: 3.63  Avg: 488.6  I/s: 261.8  Sh: 1.19   1.00 197
2018-01-01 10:00:45 AM|   GPU5  57C  Sol/s: 494.0  Sol/W: 3.62  Avg: 487.2  I/s: 261.0  Sh: 1.27   1.00 202 +
2018-01-01 10:00:45 AM|   ========== Sol/s: 2916.3 Sol/W: 3.62  Avg: 2923.2 I/s: 1566.3 Sh: 7.21   1.00 213

Do you mind sharing your OC settings? My current setting only gives me 460-470 Sol/s with 3.0-3.1 Sol/W...
Also how do you get to display the date and time?
newbie
Activity: 1
Merit: 0
Is it normal for hash rate to drop by half on DSTM miner console, NOT on pool hash rate. I am mining equihash on nicehash or miningpoolhub.

I cant understand why it does this. The gpus are not overheating or crashing. It is just a massive reduction in hash rate that's fixed by reboot of console.

It changes the difficulty rate and then drops.


I'm having the same issue trying v0.5.6 and v0.5.7.  It starts out around 4,600 Sol/s and it slowly drops to around 2,000 Sol/s over the course of a couple of hours.  Running SMOS and have tried mining several equihash coins at a couple of different pools with the same results.  Rebooting makes it go back up to 4,600 Sol/s it then it slowly drops down again.  Temperatures are all <55C with a target of 75C.  Servers seem to be changing GPU difficulties often.  Overclocks set to 0 while I try to figure this out.
full member
Activity: 378
Merit: 135
Just did the switch from EWBF last night as well.  After 12 hours I am seeing 100 sol increase over 5 cards from EWBF.  Pretty happy overall.
jr. member
Activity: 95
Merit: 2
Thought I would give dtsm a try for mining zencash have to say I'm pretty impressed a massive gain in sols. Hitting over 310 with a gtx 1060 3gb.

Agreed! I was pleasantly surprised as well. Managed to tweak overclock settings even further compared to ewbf/ccminer attempts. Running 6 1070s (zclassic):

Code:
2018-01-01 10:00:28 AM|   GPU1  52C  Sol/s: 485.7  Sol/W: 3.59  Avg: 483.6  I/s: 259.1  Sh: 1.12   0.99 195
2018-01-01 10:00:30 AM|   GPU2  58C  Sol/s: 481.0  Sol/W: 3.61  Avg: 486.6  I/s: 260.8  Sh: 1.21   1.00 197 +
2018-01-01 10:00:38 AM|   GPU4  58C  Sol/s: 484.0  Sol/W: 3.62  Avg: 487.4  I/s: 261.2  Sh: 1.19   0.99 285
2018-01-01 10:00:43 AM|   GPU0  46C  Sol/s: 478.8  Sol/W: 3.64  Avg: 489.8  I/s: 262.5  Sh: 1.22   1.00 202 +
2018-01-01 10:00:43 AM|   GPU3  40C  Sol/s: 492.8  Sol/W: 3.63  Avg: 488.6  I/s: 261.8  Sh: 1.19   1.00 197
2018-01-01 10:00:45 AM|   GPU5  57C  Sol/s: 494.0  Sol/W: 3.62  Avg: 487.2  I/s: 261.0  Sh: 1.27   1.00 202 +
2018-01-01 10:00:45 AM|   ========== Sol/s: 2916.3 Sol/W: 3.62  Avg: 2923.2 I/s: 1566.3 Sh: 7.21   1.00 213
sr. member
Activity: 504
Merit: 251
★777Coin.com★ Fun BTC Casino!
Thought I would give dtsm a try for mining zencash have to say I'm pretty impressed a massive gain in sols. Hitting over 310 with a gtx 1060 3gb.
newbie
Activity: 64
Merit: 0
New version running fine on Ubuntu 16.04 server.  Cant tell any difference from 0.5.7.

Try increasing your Afterburner settings and see what you get..   My total Sol/s now are 2950 to 2961... used to be around 2890.  

I'm already +700 mem and +200 core with my 1070Ti GPUs. Its ran all night with the new version so when I log into the box I'll check the SOL/s averages and see if they increased.
newbie
Activity: 20
Merit: 0
Is it normal for hash rate to drop by half on DSTM miner console, NOT on pool hash rate. I am mining equihash on nicehash or miningpoolhub.

I cant understand why it does this. The gpus are not overheating or crashing. It is just a massive reduction in hash rate that's fixed by reboot of console.

It changes the difficulty rate and then drops.
hero member
Activity: 630
Merit: 502
New version running fine on Ubuntu 16.04 server.  Cant tell any difference from 0.5.7.

Try increasing your Afterburner settings and see what you get..   My total Sol/s now are 2950 to 2961... used to be around 2890. 
There is an MSI Afterburner version for the Linux command line?
jpl
member
Activity: 154
Merit: 11
New version running fine on Ubuntu 16.04 server.  Cant tell any difference from 0.5.7.

Try increasing your Afterburner settings and see what you get..   My total Sol/s now are 2950 to 2961... used to be around 2890. 
newbie
Activity: 64
Merit: 0
New version running fine on Ubuntu 16.04 server.  Cant tell any difference from 0.5.7.
jpl
member
Activity: 154
Merit: 11
New Version 0.5.8

con: add support for protocol v.01000020
link openssl statically

I'm releasing 0.5.8 before the planned 0.6 due to recent requests/interest in Zclassic. Pools reporting protocol version 01000020 are supported now. 0.5.8 links latest openssl statically - zm should work fine now for people who had difficulties with openssl libraries on their distributions.

Thanks!  Seems to run faster on flypool on my initial tests so far. 
full member
Activity: 420
Merit: 184
Single connection was added already to 0.5.7 I believe.

Lol, so many versions of so many miners; so little time! Well, 0.5.7 has been chugging away for many hours and my the hashrate reported by the pool matches what dstm says it is, and I am seeing very few rejected shares - maybe 0.1% total?

To the op/dev: I'd really like to see a cumulative run time counter.

full member
Activity: 258
Merit: 104
Hashrate of 0.5.7 seems pretty much the same as 0.5.6; not trying 0.5.8 on account of the single connection issue which I don't fully understand, but which sounds bad regardless.



Single connection was added already to 0.5.7 I believe.

Single connection was a definite plus for me.  Reduced rejected shares and more stable connection.  Seems to be be good for some people, not so good for others.  Maybe having it as an option would make everyone happy.  But the default should definitely be single connection.
newbie
Activity: 56
Merit: 0
Hashrate of 0.5.7 seems pretty much the same as 0.5.6; not trying 0.5.8 on account of the single connection issue which I don't fully understand, but which sounds bad regardless.



Single connection was added already to 0.5.7 I believe.
full member
Activity: 420
Merit: 184
Hashrate of 0.5.7 seems pretty much the same as 0.5.6; not trying 0.5.8 on account of the single connection issue which I don't fully understand, but which sounds bad regardless.

jr. member
Activity: 30
Merit: 2

I have just tested with EVGA 3G mini single fan as well.
But it looks like when I pushed core more than 135 the miner will crash.
At my current setting with +120 core, +120mem, 8 GPUs rig's stable at ~2336sol/s @85% power limit (average 290-293sol/s for each GPU).
Ah what's your GPU memory, Hynix or Samsung?
Btw, your payment fee is quite good, I need to pay roughly about 120$ for renting service.

It's weird because my rig is running at +150 core without any problem. The normalized hashrate is  305sol/s.
member
Activity: 155
Merit: 10
I'm mininig using GTX 1080. Today I've noticed one strange bug (?).

I'm overclocking my GPU. If the memory has + 100-249mhz my hashrate oscilates close to 520-530 sol/s and It's close to 282-285. But only if I add 1mhz (249 -> 250) my hashrate increases approximately to 560 sol/s and It/s to almost 300.

I've run miner few times and checked this several times after hashrate stabilization. Always the same. Is this normal?

ZM measures the time your GPU has required to execute the solver (using the most accurate clocks your system provides) and calculates all the values based on this. So this is how your hardware/drivers/overclocking-program behaves.

I try to understand it, hovewer currently it looks for me something like this (pseudocode):
Code:
if(timeToSolve <= 300) //example value
hashrate = 530 + rand()%2;
else if (timeToSolve > 300)
hashrate = 550 + rand()%2;
//etc.

Do not get me wrong, I wouldn't to controvert your programming skills, nonetheless it looks a bit strange comparing to other miners that performance changes with step resposne (function) and it would be great if you could take a look at it in your free time.
Thank you in advance.
Pages:
Jump to: