excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a]

[dropky]

New version of excavator with Nist5 and improved NeoScrypt:
https://github.com/nicehash/excavator/releases/tag/v1.3.9a

Awesome, will test asap !

on my 1080Ti rigs,

Nist5
Palgin Ccminer 1.1 x64 > 395MH
Excavator 1.3.9 > 385MH

Neoscrypt
Palgin hsrminer neoscrypt > 7600MH
Excavator 1.3.9 > 7050MH

So nearly here, but not yet   Still to be thorough i will observe for one hour the average hashrate reported on pool on both algo. I tried to tweak a bit with the parameters for both algo, but it result in lower hashrates, seems like you optimised them pretty well already as parameters goes.

I'm always up for a challenge We'll put some more work into Neoscrypt and Nist5. Let me know how the pool speed comparison results out.

[sir_blacks]

Hello & here it is feedback with new release:

Hardware Spec & setting:

GPU 0: Gigabyte Windforce 2 NVIDIA GeForce GTX 1060 3GB (Samsung) dedicate to mining
GPU 1: Gigabyte NVIDIA GeForce GTX 650 2GB only for own use, not for mining
OS: Windows 7 Service Pack 1
Video Driver:  390.65
MSI Afterburn: 4.4.2
Power limit:   72 => ~86 W
Temp  limit:   80
Core  Clock:   +168
Memmory Clock: +700 (i can be push to 920 but is good only for ETH)

A. Equihash Setting 2 worker set in Mode 0 because Mode 1 is waaaay slower aka bearly hit 255 sol/s, noo other extra parameter used

{"id":1,"method":"worker.add","params":["0","0","0"]},
{"id":1,"method":"worker.add","params":["0","0","0"]}

a. 1.3.8.a = 282 Sol/s & very rare it goo down to 278
b. 1.3.9.a = 282 Sol/s & very rare it goo down to 278

- equihash algo speed: 282 Sol/s = no improvement
- running 2 hour farming Zencash, no crash / stall = good potential fix with new driver, need more time for testing, to be sure coz it was random
- reject % reduce a lot! i seen my few on one round when in 1.3.8.a usual 10% was something normal = improvement
- try to look on BTG coin it seams is something diferite vs other coin from this algoritm, Excavator react strange sometime
Other miner speed:

- DSTM 0.5.8  = ~300 Sol/s - very rare reject - very stable i use full weak with out problem
- EWBF 0.3.4b = 277 - 285 Sol/s - very rare reject - stable no issue

B. Neoscript default setting nothing change & test run was done on Feathercoin because is old & standard one

1.3.8.a B=603 (default) = 572 Kh/s => stable noo crash or stall
1.3.9.a B=603 (default) = 605 Kh/s => stable noo crash or stall

Other miner speed:

- Hsrminer by palginpav & alexkap = 710 - 720 Kh/s
- Nsgminer 0.9.4                        = 670 - 720 Kh/s
- Ccminer KlausT 8.18 cuda 9.1    = 643 Kh/s

- speed small improvement & it can be done much more for sure

cheers

[dropky]

Hello & here it is feedback with new release:

Hardware Spec & setting:

GPU 0: Gigabyte Windforce 2 NVIDIA GeForce GTX 1060 3GB (Samsung) dedicate to mining
GPU 1: Gigabyte NVIDIA GeForce GTX 650 2GB only for own use, not for mining
OS: Windows 7 Service Pack 1
Video Driver:  390.65
MSI Afterburn: 4.4.2
Power limit:   72 => ~86 W
Temp  limit:   80
Core  Clock:   +168
Memmory Clock: +700 (i can be push to 920 but is good only for ETH)

A. Equihash Setting 2 worker set in Mode 0 because Mode 1 is waaaay slower aka bearly hit 255 sol/s, noo other extra parameter used

{"id":1,"method":"worker.add","params":["0","0","0"]},
{"id":1,"method":"worker.add","params":["0","0","0"]}

a. 1.3.8.a = 282 Sol/s & very rare it goo down to 278
b. 1.3.9.a = 282 Sol/s & very rare it goo down to 278

- equihash algo speed: 282 Sol/s = no improvement
- running 2 hour farming Zencash, no crash / stall = good potential fix with new driver, need more time for testing, to be sure coz it was random
- reject % reduce a lot! i seen my few on one round when in 1.3.8.a usual 10% was something normal = improvement
- try to look on BTG coin it seams is something diferite vs other coin from this algoritm, Excavator react strange sometime
Other miner speed:

- DSTM 0.5.8  = ~300 Sol/s - very rare reject - very stable i use full weak with out problem
- EWBF 0.3.4b = 277 - 285 Sol/s - very rare reject - stable no issue

B. Neoscript default setting nothing change & test run was done on Feathercoin because is old & standard one

1.3.8.a B=603 (default) = 572 Kh/s => stable noo crash or stall
1.3.9.a B=603 (default) = 605 Kh/s => stable noo crash or stall

Other miner speed:

- Hsrminer by palginpav & alexkap = 710 - 720 Kh/s
- Nsgminer 0.9.4                        = 670 - 720 Kh/s
- Ccminer KlausT 8.18 cuda 9.1    = 643 Kh/s

- speed small improvement & it can be done much more for sure

cheers

Yeah... we haven't done any speed improvements on equihash in 1.3.9 version. What do you mean by "Excavator react strange sometime" when mining BTG? Do you get any error msgs?

Thanks for the feedback! We're constantly working on improving Excavator.

[sir_blacks]

Yeah... we haven't done any speed improvements on equihash in 1.3.9 version. What do you mean by "Excavator react strange sometime" when mining BTG? Do you get any error msgs?

Thanks for the feedback! We're constantly working on improving Excavator.

ok update 1.3.9.a mining BTG result in this:
- Excavator window it became lagy switching between application (alt tab) it take few sec to be bring in front if was behind a browser let say
- It generate huge amount of reject "low difficultie reason" , Zencash test run was perfect BTG nop is messy
example:

Est. Shares : 32,983,930 (done: 103.41%)
Your Valid   : 580.7254
Your Invalid : 239.3974 (29.19%) TO MUCH
Time Since Last Block:    40 minutes 21 seconds (round not done)

& this is happen only with excavator dtsm working fine, i will check later Zcash to see

[m1n1ngP4d4w4n]

New version of excavator with Nist5 and improved NeoScrypt:
https://github.com/nicehash/excavator/releases/tag/v1.3.9a

Awesome, will test asap !

on my 1080Ti rigs,

Nist5
Palgin Ccminer 1.1 x64 > 395MH
Excavator 1.3.9 > 385MH

Neoscrypt
Palgin hsrminer neoscrypt > 7600MH
Excavator 1.3.9 > 7050MH

So nearly here, but not yet   Still to be thorough i will observe for one hour the average hashrate reported on pool on both algo. I tried to tweak a bit with the parameters for both algo, but it result in lower hashrates, seems like you optimised them pretty well already as parameters goes.

I'm always up for a challenge We'll put some more work into Neoscrypt and Nist5. Let me know how the pool speed comparison results out.

So after a couple of hours on both algos, the difference is still here, but a bit smaller, about 2-3% for nist, and 6% for neoscrypt, getting there ! On another note it's ROCK stable as usual with excavator ! 0.11% of reject on nist5 and 0.15% with neoscrypt, it's pretty good !

[dropky]

Yeah... we haven't done any speed improvements on equihash in 1.3.9 version. What do you mean by "Excavator react strange sometime" when mining BTG? Do you get any error msgs?

Thanks for the feedback! We're constantly working on improving Excavator.

ok update 1.3.9.a mining BTG result in this:
- Excavator window it became lagy switching between application (alt tab) it take few sec to be bring in front if was behind a browser let say
- It generate huge amount of reject "low difficultie reason" , Zencash test run was perfect BTG nop is messy
example:

Est. Shares : 32,983,930 (done: 103.41%)
Your Valid   : 580.7254
Your Invalid : 239.3974 (29.19%) TO MUCH
Time Since Last Block:    40 minutes 21 seconds (round not done)

& this is happen only with excavator dtsm working fine, i will check later Zcash to see

Interesting... We'll take a look into it.

[dropky]

New version of excavator with Nist5 and improved NeoScrypt:
https://github.com/nicehash/excavator/releases/tag/v1.3.9a

Awesome, will test asap !

on my 1080Ti rigs,

Nist5
Palgin Ccminer 1.1 x64 > 395MH
Excavator 1.3.9 > 385MH

Neoscrypt
Palgin hsrminer neoscrypt > 7600MH
Excavator 1.3.9 > 7050MH

So nearly here, but not yet   Still to be thorough i will observe for one hour the average hashrate reported on pool on both algo. I tried to tweak a bit with the parameters for both algo, but it result in lower hashrates, seems like you optimised them pretty well already as parameters goes.

I'm always up for a challenge We'll put some more work into Neoscrypt and Nist5. Let me know how the pool speed comparison results out.

So after a couple of hours on both algos, the difference is still here, but a bit smaller, about 2-3% for nist, and 6% for neoscrypt, getting there ! On another note it's ROCK stable as usual with excavator ! 0.11% of reject on nist5 and 0.15% with neoscrypt, it's pretty good !

Thanks

[stzcze]

{"id":1,"method":"algorithm.add","params":["lyra2rev2","hub.miningpoolhub.com:20593","user.workername:password"]}

still status fail, do I have a bug somewhere? Thanks

[dropky]

{"id":1,"method":"algorithm.add","params":["lyra2rev2","hub.miningpoolhub.com:20593","user.workername:password"]}

still status fail, do I have a bug somewhere? Thanks

This looks ok. Unfortunately, some pools are not compatible with Excavator, that might be an issue here.

Can you post the cmd output with -d 0 (run excavator with -d 0 to increase console logging)?

[dropky]

{"id":1,"method":"algorithm.add","params":["lyra2rev2","hub.miningpoolhub.com:20593","user.workername:password"]}

still status fail, do I have a bug somewhere? Thanks

This looks ok. Unfortunately, some pools are not compatible with Excavator, that might be an issue here.

Can you post the cmd output with -d 0 (run excavator with -d 0 to increase console logging)?

Oh, I just remembered, we blocked miningpoolhub cause they were violating our EULA.

[Bimmber]

Could somebody explain what is the difference between normal Nicehash app and this - Excavator 

[sir_blacks]

Could somebody explain what is the difference between normal Nicehash app and this - Excavator  

Nicehash application it use Excavator like default miner ... because it belong to Nicehash & is develop by them ...

Nhm_setup_2.0.1.8 is a application / interface what track income, monitor & auto switch what is best to be mine according benchmark what you done on nicehash pool & it use Excavator miner, but it can use with out that for manual mining by ppls who not need to be told what's best do mine

chers

[stzcze]

{"id":1,"method":"algorithm.add","params":["lyra2rev2","hub.miningpoolhub.com:20593","user.workername:password"]}

still status fail, do I have a bug somewhere? Thanks

This looks ok. Unfortunately, some pools are not compatible with Excavator, that might be an issue here.

Can you post the cmd output with -d 0 (run excavator with -d 0 to increase console logging)?

Oh, I just remembered, we blocked miningpoolhub cause they were violating our EULA.

Thank you very much for the info

[dropky]

New version of Excavator is out:

https://github.com/nicehash/excavator/releases/tag/v1.4.0a

It's addressing the 'cuda out of memory' issues on NeoScrypt.

[opeth2112]

New version of Excavator is out:

https://github.com/nicehash/excavator/releases/tag/v1.4.0a

It's addressing the 'cuda out of memory' issues on NeoScrypt.

Still getting the same error with a 1080 ti.  I updated excavator and increased paging FYI.

[MarkAz]

New version of Excavator is out:

https://github.com/nicehash/excavator/releases/tag/v1.4.0a

It's addressing the 'cuda out of memory' issues on NeoScrypt.

No linux builds?

[opeth2112]

New version of Excavator is out:

https://github.com/nicehash/excavator/releases/tag/v1.4.0a

It's addressing the 'cuda out of memory' issues on NeoScrypt.

is there a CL argument to use to temporarily disable NeoScrypt until it can be resolved?

[opeth2112]

New version of Excavator is out:

https://github.com/nicehash/excavator/releases/tag/v1.4.0a

It's addressing the 'cuda out of memory' issues on NeoScrypt.

is there a CL argument to use to temporarily disable NeoScrypt until it can be resolved?

Never mind.  I have 2x1080ti @ 11gb ram.  Upped my paging space to 30gb and that fixed the problem.  Probably overkill on size, but I know now it should at LEAST be 2x total video RAM.

Still following to see if there are any further developments, but it's working for now.

[m1n1ngP4d4w4n]

since 1.3.8 i noticed a drop in keccak performance (7.1GH v1.3.7a) vs (6.6GH v1.3.8+) could you take a look ? (6x1080Ti rig)

[NoSubstitute]

For doo that you need to edit json file like this:
...
this it will add 2 worker / 1 device in M-0 Mode Be ware it depend by what algoritm it is use
...

Thank you for explaining this.
However, I tried it and although it works, it doesen't seem to yield a higher hash in total.
Each worker push about half the hash, but when added together, the total hash is noticably lower than when running a single worker.

I'm just mining Zcash (since NH was hacked) for fun, using a single Nvidia 1070 GPU, and i7 CPU.