Topic: excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a] - page 62. (Read 179268 times)

on my 1070
gtx       ewbf      excavator
1070      430        400

On equihash, what are folks doing to match ewbf speeds or close to them?  I have not tested my 1070's yet.  I ran excavator with 2 threads for each card.


gtx         ewbf     excavator
980         330         300
titan xp   720         650


Thanks

Yes , with new driver , is ok .

not a bug, you need the last nvidia drivers or 378.xx version to display the wattage correctly

Hello,
how can I set intencity?

sp, one post before I said to copy your own nvml or install latest drivers.

Regarding speed; 250 sol for 3gb version with 60% TDP limit.

I get a bug in the GH/W calculation:

0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
0000000000000000000000000000000000000000000000000000000000000000000000000000000 0
00000000000000000000000000000.#INF00 GH/W
[13:10:07][0x00000f00][info] net | Share #18 accepted


000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000.#INF00 GH/W
3:10:21][0x00000f00][info] net | Share #19 accepted
3:10:29][0x00000f00][info] net | Share #20 accepted
3:10:33][0x000009f4][info] =====> 215.264541 H/s
3:10:33][0x000009f4][info] gpuinfo | GPU#0    TEMP: 56 C      USAGE: 100 %
MCTRL: 74 %   POWER: -2 W
3:10:33][0x000009f4][info] =====> Total power: 0 W    Efficiency: 100000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000

1060 3gb is only doing 215 with 2 threads.

My private fork is doing 275 on the same hardware, clocks and tdp. and 3 threads.

can used these miner with r9 fury card ati???

Good to know regarding nvml... Will work on some solution to fix this issue in future versions... For now, whoever wants to have accurate readings, just install latest NVIDIA drivers or copy your own nvml.dll.

yeah new driver fixed the reading

also tested old driver DLL file (on 2nd rig) and now reading are fine too, maybe in next miner version use the driver system DLL?

also speed now match ewbf miner... if you deduct 2% from his fee

Could you try and upgrade drivers to 378.78 ?

We have various cards and all show wattage correctly. Also, the reading fails at function nvmlDeviceGetPowerUsage, for which there is no reason to fail if supplied with proper device handle. And since nvidia-smi does show you a value, your card does support power readings.

EDIT: alternatively, you can put your own nvml.dll into excavator folder (copy it out of program files, nvidia).

Win10 x64 drv 378.57 5x 1070 Gainward phoenix (intel GPU is enebled but no monitor connected at any)

OK, here it is, new version as promised: http://nicehash.com/tools/excavator_v1.1.3a_Win64.zip

Changes:


Regarding overclocking:


For all, that Wattage report isn't working correctly, run under debug mode ('-d 1' or '-f 1') and paste log here. We would like to get to know whether the issue is because of pcibusid string or something else.

Yes, temps are not so high if you set low TDP, and not so loud. But with 100% TDP... things really get hot. All algos actually, by stock clocks, go over 100% TDP. Other cards reach more than 100% TDP with overclocking. This card gets quickly power throttled or thermal throttled.

Interesting stuff , im actually even more surprised by the running temps, they're really low 

It is an interesting thing we are noticing with these cards. Due to so big memory bandwidth, it is completely irrelevant to overclock memory if you run lower TDP - it does not help, instead, it can actually make less speed. We also noticed that downclocking memory can help slightly and giving some 10-20 sols more. 

This is probably efficiency world record for mining equihash (4.2 Sol per Watt).

Here we downclocked memory -400. Notice memory controller load - it is 71% which is below 80%. 80% is where memory starts to be major factor for equihash slowdown.

Limited to 150 W (60% TDP), the efficiency is much better (are there more efficient cards out there?):

We got 1080 Ti in our labs and are now adding support in excavator and will be releasing new alpha version soon.

Equihash:

These do run very hot. Need to see performance under water.

ah well without tdp limitation i can reach 440 i think with that crazy mem, but with 60% it's simply not feasible

actually my core is reaching 2000 with 60%...nevermind it's 1840 i confused with another algo

I believe they mean the core settings without the TDP limitation. Once limited by TDP it will be downclocked for sure. This would mean roughly +220 OC for the non OC cards?