You are running cards with only 106 W power, no wonder you get low hashpower (400 per card). Now just increase TDP if you want more speed, eg set TDP to 70 and see how that improves hashrate.
EDIT: You did not show your memory clocks, but if you have samsung, you can easily go 4700. If you have micron, you can go 4400 stable and experiment with 4450.
Topic: excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a] - page 60. (Read 179300 times)
March 21, 2017, 01:31:40 PM
March 21, 2017, 12:55:25 PM
Launch parameters for 5x1070
excavator.exe -a equihash -s equihash.eu.nicehash.com:3357 -u 1PJQRnBRZosg********.***07:x -ca -ca -or -os 0 100 700 60 -os 1 100 700 60 -os 2 100 700 60 -os 3 100 700 60 -os 4 100 700 60
Add to the description, it was necessary to find out experimentally
The results are not impressive. (At EWBF's speed 2450H/s)
excavator.exe -a equihash -s equihash.eu.nicehash.com:3357 -u 1PJQRnBRZosg********.***07:x -ca -ca -or -os 0 100 700 60 -os 1 100 700 60 -os 2 100 700 60 -os 3 100 700 60 -os 4 100 700 60
Add to the description, it was necessary to find out experimentally
The results are not impressive. (At EWBF's speed 2450H/s)
Code:
[20:52:28][0x00001794][info] net | Share #66 accepted
[20:52:29][0x00000c94][info] =====> 1.996253 kH/s
[20:52:29][0x00000c94][info] gpuinfo | GPU#0 TEMP: 50 C USAGE: 99 % MEMCTRL: 63 % POWER: 106.192 W
[20:52:29][0x00000c94][info] gpuinfo | GPU#1 TEMP: 59 C USAGE: 99 % MEMCTRL: 75 % POWER: 106.999 W
[20:52:29][0x00000c94][info] gpuinfo | GPU#2 TEMP: 59 C USAGE: 99 % MEMCTRL: 74 % POWER: 106.553 W
[20:52:29][0x00000c94][info] gpuinfo | GPU#3 TEMP: 60 C USAGE: 99 % MEMCTRL: 76 % POWER: 106.988 W
[20:52:29][0x00000c94][info] gpuinfo | GPU#4 TEMP: 60 C USAGE: 99 % MEMCTRL: 75 % POWER: 107.099 W
[20:52:29][0x00000c94][info] =====> Total power: 533.831 W Efficiency: 3.739485 H/W
[20:52:35][0x00001794][info] net | Share #67 accepted
March 21, 2017, 11:40:34 AM
Can you read hashrate directly from miners and send to pool? This can make users hash rate more stable.
March 21, 2017, 10:32:28 AM
I wrote in the other thread:
A possible speedup for equihash
Could the blake2s pass be removed completely (round 0)? Dual mined with the memory accesses? I am not talking about 2 threads, but one thread with the round0 merged into the other rounds.
The miner will need to do 1 nonce search(round1-round8) and one blake2s (round0) merged into the round1-round8 code per iteration. Since you work on the round0 data from the previos run, the nonce found would be the result of the previous padding data.
On NVIDIA round0 take 20% of the time. (The opensource ZEC DJezo kernel)
A possible speedup for equihash
Could the blake2s pass be removed completely (round 0)? Dual mined with the memory accesses? I am not talking about 2 threads, but one thread with the round0 merged into the other rounds.
The miner will need to do 1 nonce search(round1-round8) and one blake2s (round0) merged into the round1-round8 code per iteration. Since you work on the round0 data from the previos run, the nonce found would be the result of the previous padding data.
On NVIDIA round0 take 20% of the time. (The opensource ZEC DJezo kernel)
1 nonce is already used now, but each blake2s hash has different id, so you get out ~2 mil blake2s hashes. You could minimize read and writes, but then you would have to recalculate blake2s hashes each round (computation-memory tradeoff), which for sure would, even if you reached higher speed, cause much higher power consumption.
March 21, 2017, 09:57:20 AM
What this the .bat for mining zec on another pool with nvidia ? .
March 21, 2017, 04:18:47 AM
I wrote in the other thread:
A possible speedup for equihash
Could the blake2s pass be removed completely (round 0)? Dual mined with the memory accesses? I am not talking about 2 threads, but one thread with the round0 merged into the other rounds.
The miner will need to do 1 nonce search(round1-round8) and one blake2s (round0) merged into the round1-round8 code per iteration. Since you work on the round0 data from the previos run, the nonce found would be the result of the previous padding data.
On NVIDIA round0 take 20% of the time. (The opensource ZEC DJezo kernel)
A possible speedup for equihash
Could the blake2s pass be removed completely (round 0)? Dual mined with the memory accesses? I am not talking about 2 threads, but one thread with the round0 merged into the other rounds.
The miner will need to do 1 nonce search(round1-round8) and one blake2s (round0) merged into the round1-round8 code per iteration. Since you work on the round0 data from the previos run, the nonce found would be the result of the previous padding data.
On NVIDIA round0 take 20% of the time. (The opensource ZEC DJezo kernel)
March 21, 2017, 02:34:38 AM
This is intriguing when you run 8 rigs in an apartment (48x GTX 1070) as the outside temp starts to warm up. It's also interesting because at 70-75 TDP I could easily run 3x rigs per 20A circuit.
I run 3x gtx 1070 rigs on 16A without any problems.
March 21, 2017, 02:32:53 AM
Haven't seen a Pascal card to die because of high overclock. We did destroy one due to water leakage and some stuff was burnt on it, but never due to high memory clock and we are running them 24/7 mining. Just make sure you have adequate cooling, which you already need if you are mining 24/7.
I use oc and reduced TDP and have no 1070 cards RMA'd since september. (6 months running 100% mining)
Of the gtx 1060 3gb's I have RMA'd 1% (6 months running 100% mining)
March 20, 2017, 11:40:21 PM
Intriguing results for low power compared to 100% TDP.
OLD
EVGA Hybrid GTX 1070 x 6
TDP 100%
Temp Limit 83 (Unlinked)
Core +125
Mem +575
Fan Speed Auto (usually stays around 28%)
NHEQ 0.5a - Equihash (ZEC on Flypool) - 2635 H/s
Excavator 1.1.0a - Equihash (ZEC on Flypool) - 2680 H/s
NEW
EVGA Hybrid GTX 1070 x 6
TDP 75%
Temp Limit 83 (Unlinked) / Voltage locked to 0.85V (108-113W per card)
Core +137
Mem +600
Fan Speed Auto (usually stays around 28%)
Excavator 1.1.3a - Equihash (ZEC on Flypool) - 2510 H/s
This is intriguing when you run 8 rigs in an apartment (48x GTX 1070) as the outside temp starts to warm up. It's also interesting because at 70-75 TDP I could easily run 3x rigs per 20A circuit.
OLD
EVGA Hybrid GTX 1070 x 6
TDP 100%
Temp Limit 83 (Unlinked)
Core +125
Mem +575
Fan Speed Auto (usually stays around 28%)
NHEQ 0.5a - Equihash (ZEC on Flypool) - 2635 H/s
Excavator 1.1.0a - Equihash (ZEC on Flypool) - 2680 H/s
NEW
EVGA Hybrid GTX 1070 x 6
TDP 75%
Temp Limit 83 (Unlinked) / Voltage locked to 0.85V (108-113W per card)
Core +137
Mem +600
Fan Speed Auto (usually stays around 28%)
Excavator 1.1.3a - Equihash (ZEC on Flypool) - 2510 H/s
This is intriguing when you run 8 rigs in an apartment (48x GTX 1070) as the outside temp starts to warm up. It's also interesting because at 70-75 TDP I could easily run 3x rigs per 20A circuit.
how are you locking Voltage?? "locked to 0.85V" ..
regards
nemo?
March 20, 2017, 08:47:49 PM
Intriguing results for low power compared to 100% TDP.
OLD
EVGA Hybrid GTX 1070 x 6
TDP 100%
Temp Limit 83 (Unlinked)
Core +125
Mem +575
Fan Speed Auto (usually stays around 28%)
NHEQ 0.5a - Equihash (ZEC on Flypool) - 2635 H/s
Excavator 1.1.0a - Equihash (ZEC on Flypool) - 2680 H/s
NEW
EVGA Hybrid GTX 1070 x 6
TDP 75%
Temp Limit 83 (Unlinked) / Voltage locked to 0.85V (108-113W per card)
Core +137
Mem +600
Fan Speed Auto (usually stays around 28%)
Excavator 1.1.3a - Equihash (ZEC on Flypool) - 2510 H/s
This is intriguing when you run 8 rigs in an apartment (48x GTX 1070) as the outside temp starts to warm up. It's also interesting because at 70-75 TDP I could easily run 3x rigs per 20A circuit.
OLD
EVGA Hybrid GTX 1070 x 6
TDP 100%
Temp Limit 83 (Unlinked)
Core +125
Mem +575
Fan Speed Auto (usually stays around 28%)
NHEQ 0.5a - Equihash (ZEC on Flypool) - 2635 H/s
Excavator 1.1.0a - Equihash (ZEC on Flypool) - 2680 H/s
NEW
EVGA Hybrid GTX 1070 x 6
TDP 75%
Temp Limit 83 (Unlinked) / Voltage locked to 0.85V (108-113W per card)
Core +137
Mem +600
Fan Speed Auto (usually stays around 28%)
Excavator 1.1.3a - Equihash (ZEC on Flypool) - 2510 H/s
This is intriguing when you run 8 rigs in an apartment (48x GTX 1070) as the outside temp starts to warm up. It's also interesting because at 70-75 TDP I could easily run 3x rigs per 20A circuit.
March 20, 2017, 05:15:55 PM
Hi Ive been testing your new version 1.1.3a been having great results with the 1070's at -30-40 tdp very similar speeds to EWBF now (well done) and with no fee(thank-you)
im trying to add excavator to my multi algo bat.. it is working but as my bat switches algos by stratum disconnect.. excavator will not close and instead it say's stratum disconnect retrying in 12 seconds and just stays on loop doing that..
my question is there a command a can add to the bat file to make excavator close when stratum is disconnected?
i have tried excavator.exe -h for a full list of current commands but there doesn't seem to be anything related to stratum disconnect or close if connection lost..
your help would be much appreciated
Regards
Nemo
im trying to add excavator to my multi algo bat.. it is working but as my bat switches algos by stratum disconnect.. excavator will not close and instead it say's stratum disconnect retrying in 12 seconds and just stays on loop doing that..
my question is there a command a can add to the bat file to make excavator close when stratum is disconnected?
i have tried excavator.exe -h for a full list of current commands but there doesn't seem to be anything related to stratum disconnect or close if connection lost..
your help would be much appreciated
Regards
Nemo
There is no such command, but wait for API commanding interface to be implemented, you will be able to do magic with it once it is done.
March 20, 2017, 03:51:58 PM
Hi Ive been testing your new version 1.1.3a been having great results with the 1070's at -30-40 tdp very similar speeds to EWBF now (well done) and with no fee(thank-you)
im trying to add excavator to my multi algo bat.. it is working but as my bat switches algos by stratum disconnect.. excavator will not close and instead it say's stratum disconnect retrying in 12 seconds and just stays on loop doing that..
my question is there a command a can add to the bat file to make excavator close when stratum is disconnected?
i have tried excavator.exe -h for a full list of current commands but there doesn't seem to be anything related to stratum disconnect or close if connection lost..
your help would be much appreciated
Regards
Nemo
im trying to add excavator to my multi algo bat.. it is working but as my bat switches algos by stratum disconnect.. excavator will not close and instead it say's stratum disconnect retrying in 12 seconds and just stays on loop doing that..
my question is there a command a can add to the bat file to make excavator close when stratum is disconnected?
i have tried excavator.exe -h for a full list of current commands but there doesn't seem to be anything related to stratum disconnect or close if connection lost..
your help would be much appreciated
Regards
Nemo
March 20, 2017, 03:48:34 PM
Anyone tested on the pools. I get a bit faster hashrate poolside with nheqminer than EFBW's miner. Probobly because of the donation code and poolswitching.. I am not using the excavator, but I guess same. somebody should setup a test and compare two identical cards for 24hours...
The excavator is good on the 1070, and not so good on the 1060 3gb...
The excavator is good on the 1070, and not so good on the 1060 3gb...
March 20, 2017, 03:43:07 PM
I used -ca -ca :-D
March 20, 2017, 03:41:45 PM
Well for me the miner is bit slower on 1070 cards by 200sol/s in total.
It performs well on GTx1080 and 1080Ti
It performs well on GTx1080 and 1080Ti
Have you tried with -cd 0 0 0 1 1 1 2 2 2 etc?
March 20, 2017, 03:34:37 PM
Well for me the miner is bit slower on 1070 cards by 200sol/s in total.
It performs well on GTx1080 and 1080Ti
It performs well on GTx1080 and 1080Ti
March 20, 2017, 03:32:06 PM
I have been testing this a lot and have very good results at 120W TDP limit at each card, i would say it is very close to EWBF and without the fee and lost switching time it is better. I will switch all of my rigs once I have little more time 
March 20, 2017, 03:13:12 PM
I was expecting a readme or the excavator.txt to explain all the settings to the miner. Seems like the .bat files contain most of that with no help on the OC settings. I think a full list of settings and commands is something very basic that should be added in.
I do not see any difference in performance at 50% TDP for equihash on my 1070 over EQM from the NiceHash GUI so I'll stick with that for now. As for mining and holding it seems the 1070 FTW pumps much higher Sol/s over all the other ones on EWBF. This seems isolated to just FTW's and certain 1070 editions but it is some sign that there is more optimization to be made with Equihash
I've seen claims of 1080's hitting 600 Sol/s on EWBF also
I do not see any difference in performance at 50% TDP for equihash on my 1070 over EQM from the NiceHash GUI so I'll stick with that for now. As for mining and holding it seems the 1070 FTW pumps much higher Sol/s over all the other ones on EWBF. This seems isolated to just FTW's and certain 1070 editions but it is some sign that there is more optimization to be made with Equihash
I've seen claims of 1080's hitting 600 Sol/s on EWBF also
March 20, 2017, 02:52:55 PM
And if I have 6 cards on the rig? Can I specify the same settings for all of them?
If your cards ID is 0 then the example for setting +100 core, +700 mem and 60 tdp would be:
If you are so affraid of "frying" your card, then perhaps you shouldn't be mining at all and just let the card be in idle mode
I don't think it needed sarcasm, but it was fun, so it's ok
Again I'm no expert in mining on cuda, and I see no one on gaming forum who overclock this high the memory of a 1080. So +800 feels like possible bacon smell to me, maybe not.
And yes, when I'm mining with my AMD rigs or my this nvidia gaming pc, I consider all the costs even the burning overkill of a card, risks cost compared to profits. Correct me if I'm wrong but don't see that as being frightened by the outcome of an extreme oc.
Overclocking AMD of 10% with modified bios for 200€ (in France) 480s is ok because the cards are "cheap" compared to the nvidia ones.
Haven't seen a Pascal card to die because of high overclock. We did destroy one due to water leakage and some stuff was burnt on it, but never due to high memory clock and we are running them 24/7 mining. Just make sure you have adequate cooling, which you already need if you are mining 24/7.
Can you post the command line you are using for overclocking and lowering the TDP for the 1070s? Just want to see an example to work from.
Thanks.
Thanks.
If your cards ID is 0 then the example for setting +100 core, +700 mem and 60 tdp would be:
If you are so affraid of "frying" your card, then perhaps you shouldn't be mining at all and just let the card be in idle mode
I don't think it needed sarcasm, but it was fun, so it's ok
Again I'm no expert in mining on cuda, and I see no one on gaming forum who overclock this high the memory of a 1080. So +800 feels like possible bacon smell to me, maybe not.
And yes, when I'm mining with my AMD rigs or my this nvidia gaming pc, I consider all the costs even the burning overkill of a card, risks cost compared to profits. Correct me if I'm wrong but don't see that as being frightened by the outcome of an extreme oc.
Overclocking AMD of 10% with modified bios for 200€ (in France) 480s is ok because the cards are "cheap" compared to the nvidia ones.
Haven't seen a Pascal card to die because of high overclock. We did destroy one due to water leakage and some stuff was burnt on it, but never due to high memory clock and we are running them 24/7 mining. Just make sure you have adequate cooling, which you already need if you are mining 24/7.
March 20, 2017, 02:42:01 PM
Why does the NiceHash GUI run the EQM miner instead?
Is Excavator able to push beyond 60% TDP, and how does it perform on 50% ?
I may need help configuring Excavator equihash for the NiceHash pool. I could not get EWBF to work on it before. I am downloading now and I will see what I batch configurations are in it.
Is Excavator able to push beyond 60% TDP, and how does it perform on 50% ?
I may need help configuring Excavator equihash for the NiceHash pool. I could not get EWBF to work on it before. I am downloading now and I will see what I batch configurations are in it.
Jump to: