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

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

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 !

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

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.

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

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.

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.

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

Thanks for the clarification I hope they are in my favour soon then 

Due to extremely high bitcoin transaction fees, payment schedule for external wallet for balances greater than 0.01 btc are adjusted accordingly to blockchain conditions. If on the day of the payout, payments for 0.01 btc are possible, they'll be processed (meaning... payments for 0.01 btc will be processed eventually). Payouts for balances greater than 0.1 BTC are paid daily.

Just a general query as the payput threshold faq doesnt make much sense as it says something different on another page. Im currently mining using your miner and have a balance approaching 0.01btc. Im using an external wallet and wondering if that uts correct payout threshold or do i have to reach 0.1btc?

Thanks.

As long as users will download Excavator from GitHub on their own, you're not violating Excavator's EULA.

If I create an application of the analogue of NHM and will distribute it (but the users will have to install the Excavator themselves) - this will not violate EULA?

Sorry, we're not changing our EULA.

Hi there,

I'd like to create a docker image to give excavator a try. I saw the huge disclamer saying it's not allowed to redistribute. What a pity...

Would you consider changing your mind ? Otherwise I'll only publish the Dockerfile and people will have to build the image themself which is quite unefficient...

Regards, Adam.

Thanks you sir, keep up the good work, i love excavator 

We're well aware of the performance gap on Neoscrypt and we're working on optimisations as we speak, new version should be out soon. Same goes for equihash, we're actively working on it. I wasn't aware of the rejects though, will take a look into it. Thanks for the feedback!

ello there
few small feedback & request:

1. Excavator need attention for BTG algoritm coz it generate to many reject / fail & same equihash algo it need better tuning like speed / power see dtms, bminer what are much much faster & optimal

example: dtms, bminer work constant 1060 GTX 3G with 300-310 Sol /s - 86W vs Excavator 282 Sol/s - 86W ONLY if is set on M0 mode

2. Neoscript same it can get more speed
example: 1060 GTX 3G Excavator work with 540 when hsrminer or nsgminer it push to 600-620

i test all version 1.3.0.a, 1.3.3.a, 1.3.4.a, 1.3.6.a, 1.3.7.a, 1.3.8.a ... all are great but they need better ajustment & personal i will like to get back to Excavator becouse i like much more json + bat run combo it can make thing more organize & easy

cheers

Currently there is no option for backup pools, but it's definitely a reasonable request, I'll see what I can do. 

Hello Team,

Is there a way to setup backup pools in excavator ? If not can it be added as a feature ? Would be great to have, some nicehash stratum are going down and it's a shame to lose out in mining time when they does.

Thanks