Pages:
Author

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

member
Activity: 68
Merit: 10
Thanks for the answer, but I already realized
Code:
[
{"time":0,"commands":[
{"id":1,"method":"algorithm.add","params":["equihash","zcl.suprnova.cc:4042","User.node07"]}
]},
{"time":3,"commands":[
{"id":1,"method":"worker.add","params":["0","0"]},
{"id":1,"method":"worker.add","params":["0","0"]},
{"id":1,"method":"worker.add","params":["0","1"]},
{"id":1,"method":"worker.add","params":["0","1"]},
{"id":1,"method":"worker.add","params":["0","2"]},
{"id":1,"method":"worker.add","params":["0","2"]},
{"id":1,"method":"worker.add","params":["0","3"]},
{"id":1,"method":"worker.add","params":["0","3"]},
{"id":1,"method":"worker.add","params":["0","4"]},
{"id":1,"method":"worker.add","params":["0","4"]}
]},
{"time":5,"commands":[
{"id":2,"method":"device.set.tdp","params":["0","111"]},
{"id":2,"method":"device.set.tdp","params":["1","111"]},
{"id":2,"method":"device.set.tdp","params":["2","111"]},
{"id":2,"method":"device.set.tdp","params":["3","111"]},
{"id":2,"method":"device.set.tdp","params":["4","111"]},
{"id":2,"method":"device.set.core_delta","params":["0","80"]},
{"id":2,"method":"device.set.core_delta","params":["0","80"]},
{"id":2,"method":"device.set.core_delta","params":["0","80"]},
{"id":2,"method":"device.set.core_delta","params":["0","80"]},
{"id":2,"method":"device.set.core_delta","params":["0","80"]},
{"id":2,"method":"device.set.memory_delta","params":["0","700"]},
{"id":2,"method":"device.set.memory_delta","params":["0","700"]},
{"id":2,"method":"device.set.memory_delta","params":["0","700"]},
{"id":2,"method":"device.set.memory_delta","params":["0","700"]},
{"id":2,"method":"device.set.memory_delta","params":["0","700"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"worker.print.speed","params":["1"]},
{"id":1,"method":"worker.print.speed","params":["2"]},
{"id":1,"method":"worker.print.speed","params":["3"]},
{"id":1,"method":"worker.print.speed","params":["4"]},
{"id":1,"method":"worker.print.speed","params":["5"]},
{"id":1,"method":"worker.print.speed","params":["6"]},
{"id":1,"method":"worker.print.speed","params":["7"]},
{"id":1,"method":"worker.print.speed","params":["8"]},
{"id":1,"method":"worker.print.speed","params":["9"]},
{"id":1,"method":"algorithm.print.speeds","params":["0"]}
]}
]
By the way what does it mean ""id":2" ? In the documentation about this forgot to write...

The result is more than pathetic:
Code:
[18:22:27][0x00001e24][info] core | Device #0-0 speed: 202.539308 H/s
[18:22:27][0x00001e24][info] core | Device #0-1 speed: 206.219820 H/s
[18:22:27][0x00001e24][info] core | Device #1-2 speed: 207.831280 H/s
[18:22:27][0x00001e24][info] core | Device #1-3 speed: 206.463997 H/s
[18:22:27][0x00001e24][info] core | Device #2-4 speed: 208.180113 H/s
[18:22:27][0x00001e24][info] core | Device #2-5 speed: 204.169727 H/s
[18:22:27][0x00001e24][info] core | Device #3-6 speed: 204.628798 H/s
[18:22:27][0x00001e24][info] core | Device #3-7 speed: 207.113224 H/s
[18:22:27][0x00001e24][info] core | Device #4-8 speed: 207.310311 H/s
[18:22:27][0x00001e24][info] core | Device #4-9 speed: 208.467500 H/s
[18:22:27][0x00001e24][info] core | Algorithm 'equihash' total speed: 2.062495 kH/s

The previous version excavator gave 2,241 kH/s.
hero member
Activity: 588
Merit: 520
NEW RELEASE - v1.2.1a

Download: https://github.com/nicehash/excavator/releases

Urgently read: https://github.com/nicehash/excavator/blob/master/README.md

Changelog:
Quote
support for API and commanding file at the same time
added commanding file event: on_quit
fixed connection bug
added HTTP server for API commands
fixed a bug in phymem.sys
optimized equihash OpenCL kernel
added API method: info
general fixes and improvements

We are also working on a good pro-style API documentation that can be found here: https://github.com/nicehash/excavator/tree/master/api
hero member
Activity: 588
Merit: 520
How to set up on 5 GTX1070?
Old start line:
excavator.exe -a equihash -s zcl.suprnova.cc:4042 -u User.node07:x -ca -ca -od 5 -or -os 0 %core_delta% %mem_delta% %tdp% -os 1 %core_delta% %mem_delta% %tdp% -os 2 %core_delta% %mem_delta% %tdp% -os 3 %core_delta% %mem_delta% %tdp% -os 4 %core_delta% %mem_delta% %tdp%

I'm probably stupid, but I can not translate it into json file config  Huh

The cmd file I use for my machine that has 4 various NVIDIA cards is following:
Code:
[
{"time":1,"commands":[
{"id":1,"method":"algorithm.add","params":["equihash","equihash.eu.nicehash.com:3357","EDITEDOUT"]}
]},
{"time":2,"commands":[
{"id":1,"method":"worker.add","params":["0","0"]},
{"id":1,"method":"worker.add","params":["0","1"]},
{"id":1,"method":"worker.add","params":["0","1"]},
{"id":1,"method":"worker.add","params":["0","2"]},
{"id":1,"method":"worker.add","params":["0","2"]},
{"id":1,"method":"worker.add","params":["0","3"]},
{"id":1,"method":"worker.add","params":["0","3"]}
]},
{"time":5,"commands":[
{"id":1,"method":"device.set.power_limit","params":["0","126"]},
{"id":1,"method":"device.set.core_delta","params":["0","100"]},
{"id":1,"method":"device.set.memory_delta","params":["0","800"]},
{"id":1,"method":"device.set.power_limit","params":["1","90"]},
{"id":1,"method":"device.set.core_delta","params":["1","100"]},
{"id":1,"method":"device.set.memory_delta","params":["1","700"]},
{"id":1,"method":"device.set.power_limit","params":["2","72"]},
{"id":1,"method":"device.set.core_delta","params":["2","100"]},
{"id":1,"method":"device.set.memory_delta","params":["2","400"]},
{"id":1,"method":"device.set.power_limit","params":["3","126"]},
{"id":1,"method":"device.set.core_delta","params":["3","130"]},
{"id":1,"method":"device.set.memory_delta","params":["3","900"]}
]},
{"time":10,"commands":[
{"id":1,"method":"worker.reset","params":["0"]},
{"id":1,"method":"worker.reset","params":["1"]},
{"id":1,"method":"worker.reset","params":["2"]},
{"id":1,"method":"worker.reset","params":["3"]},
{"id":1,"method":"worker.reset","params":["4"]},
{"id":1,"method":"worker.reset","params":["5"]},
{"id":1,"method":"worker.reset","params":["6"]}
]},
{"time":15,"loop":15,"commands":[
  {"id":1,"method":"algorithm.print.speeds","params":[]}
]},
{"event":"on_quit","commands":[
{"id":1,"method":"device.set.tdp","params":["0","100"]},
{"id":1,"method":"device.set.core_delta","params":["0","0"]},
{"id":1,"method":"device.set.memory_delta","params":["0","0"]},
{"id":1,"method":"device.set.tdp","params":["1","100"]},
{"id":1,"method":"device.set.core_delta","params":["1","0"]},
{"id":1,"method":"device.set.memory_delta","params":["1","0"]},
{"id":1,"method":"device.set.tdp","params":["2","100"]},
{"id":1,"method":"device.set.core_delta","params":["2","0"]},
{"id":1,"method":"device.set.memory_delta","params":["2","0"]},
{"id":1,"method":"device.set.tdp","params":["3","100"]},
{"id":1,"method":"device.set.core_delta","params":["3","0"]},
{"id":1,"method":"device.set.memory_delta","params":["3","0"]}
]}
]

First, establish connection with remote pool - algorithm equihash.

Then I add workers so CUDA stuff is initialized (potential jump to P0 state can happen here).

Then waiting a bit for all these CUDA context are initialized and applying clocks and TDP.

After 10 seconds, I reset speed counter of all workers.

Then after 15 seconds and every 15 seconds print total speed to console.

And I also have on_quit even that resets applied clocks and TDPs back to default values.

Hope this helps you Smiley
member
Activity: 68
Merit: 10
How to set up on 5 GTX1070?
Old start line:
excavator.exe -a equihash -s zcl.suprnova.cc:4042 -u User.node07:x -ca -ca -od 5 -or -os 0 %core_delta% %mem_delta% %tdp% -os 1 %core_delta% %mem_delta% %tdp% -os 2 %core_delta% %mem_delta% %tdp% -os 3 %core_delta% %mem_delta% %tdp% -os 4 %core_delta% %mem_delta% %tdp%

I'm probably stupid, but I can not translate it into json file config  Huh
sr. member
Activity: 728
Merit: 304
Miner Developer
1.2.0a works great with nvidia cards.

But, I cant make it work with amd cards
[error] opencl | Failed to load phymem.

It comes with phymem.sys , I have to copy this file to any places? (Windows7)

Thank you.
PD: Yes, I have executed turn-driver-signature-enforcement-off.bat and reboot and run excavator as admin.
Driver: win7-64bit-radeon-software-crimson-relive-16.12.2-jan3

There is a bug in the current alpha version that prevents the driver from being loaded in some cases.
I fixed the bug already and am waiting for the next alpha version myself.
jr. member
Activity: 76
Merit: 1
1.2.0a works great with nvidia cards.

But, I cant make it work with amd cards
[error] opencl | Failed to load phymem.

It comes with phymem.sys , I have to copy this file to any places? (Windows7)

Thank you.
PD: Yes, I have executed turn-driver-signature-enforcement-off.bat and reboot and run excavator as admin.
Driver: win7-64bit-radeon-software-crimson-relive-16.12.2-jan3
sr. member
Activity: 406
Merit: 250
djeZo
When do you optimize the excavator by 6-8%?

When we put in all of popular algorithms and get some good anti-reversing tehcniques in place so our ideas and hard work isn't stolen again. Until then, we better keep it a bit under, so we don't draw too much attention.

why they should stole your work if they already have the same speed? do you suspect that EWBF is stealing your work and therefore he was able to reach your speed in this way?
sr. member
Activity: 728
Merit: 304
Miner Developer
Well, these numbers are also affected by other hardware components, too.
(My dev PC is quite old...)
I'm pretty sure excavator will reach 300 S/s on my old PC soon, though.
sr. member
Activity: 703
Merit: 272
Here is the latest news with the OpenCL support of excavator:



The hardware/software configuration is as follows:

Stock Radeon RX 480
Windows 10 64-bit
AMD Crimson Software 16.9.2

With the same configuration, Claymore's runs at around 271 S/s.

I am not entirely sure when the most recent optimizations would be publicly available, but you guys will definitely see a vastly optimized version of excavator at some point in the future.

My stock RX 480 cards do 289-305 on claymore's
sr. member
Activity: 1246
Merit: 274
djeZo
When do you optimize the excavator by 6-8%?

When we put in all of popular algorithms and get some good anti-reversing tehcniques in place so our ideas and hard work isn't stolen again. Until then, we better keep it a bit under, so we don't draw too much attention.

I can certainly understand and agree with that, nobody likes having their code stolen. Is there any kind of approximate time frame for when these newer optimizations might be available via NiceHash? Thanks!
sr. member
Activity: 1484
Merit: 253
zawawa What about optimization for GCN1.0 cards?
hero member
Activity: 588
Merit: 520
djeZo
When do you optimize the excavator by 6-8%?

When we put in all of popular algorithms and get some good anti-reversing tehcniques in place so our ideas and hard work isn't stolen again. Until then, we better keep it a bit under, so we don't draw too much attention.
sr. member
Activity: 728
Merit: 304
Miner Developer
Here is the latest news with the OpenCL support of excavator:



The hardware/software configuration is as follows:

Stock Radeon RX 480
Windows 10 64-bit
AMD Crimson Software 16.9.2

With the same configuration, Claymore's runs at around 271 S/s.

I am not entirely sure when the most recent optimizations would be publicly available, but you guys will definitely see a vastly optimized version of excavator at some point in the future.
newbie
Activity: 3
Merit: 0
EWBF's 485 Sol
https://image.ibb.co/jGm90k/1.jpg
Palit GTX 1070 Jetstream
Core 1964 Voltage 0.900 Mem +800 micron

if i use excavator. 456 sol
https://image.ibb.co/cA0K0k/2.jpg

24/7 stable mining

djeZo
When do you optimize the excavator by 6-8%?
sr. member
Activity: 463
Merit: 250

GTX 1070 EWBF's CUDA Zcash miner

  Speed          Power usage       Effecincy
 490 Sol             137W            3.58 Sol/W

What are your settings for that? I cant even come close to that at 155w

You cant, i highly doubt he can do it over longer period.

Also nicehash, those numbers are awesome? Have you made some iprovements to the equihash algo?

 Those numbers look like 1080 numbers - that's almost IDENTICAL to what I see on my Gigabyte 1080 at +150 core, stock memory, and 70% power limit with EBWF on Win7.
 (489/141/3.48 when I just looked at it but it does bounce around a bit).

 I've not seen any of my 1070s manage more than about 450 sol/s even with power limit and overclock BOTH set quite high and the cards running over 80C temps.




Almost any 1070 can go over 465 sols, most of them can do 480. But not efficient. Thats why i measure the cards at 120W.  Also using stock memory on a memory intensive algo is just throwing money away.
member
Activity: 93
Merit: 10
I have msi gaming x gtx1070's and I will be happy if I get 420 sols with low W usage. any one have recomendations on afterburner settings?
legendary
Activity: 1498
Merit: 1030

GTX 1070 EWBF's CUDA Zcash miner

  Speed          Power usage       Effecincy
 490 Sol             137W            3.58 Sol/W

What are your settings for that? I cant even come close to that at 155w

You cant, i highly doubt he can do it over longer period.

Also nicehash, those numbers are awesome? Have you made some iprovements to the equihash algo?

 Those numbers look like 1080 numbers - that's almost IDENTICAL to what I see on my Gigabyte 1080 at +150 core, stock memory, and 70% power limit with EBWF on Win7.
 (489/141/3.48 when I just looked at it but it does bounce around a bit).

 I've not seen any of my 1070s manage more than about 450 sol/s even with power limit and overclock BOTH set quite high and the cards running over 80C temps.



hero member
Activity: 588
Merit: 520
so when will the 1.2.1.a beta be out :-D

Hopefully today; we are finalizing web status page.
full member
Activity: 162
Merit: 100
so when will the 1.2.1.a beta be out :-D
hero member
Activity: 588
Merit: 520

Also nicehash, those numbers are awesome? Have you made some iprovements to the equihash algo?

Nop, that's it. Just optimized OC params, nothing more.
Pages:
Jump to: