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

sir_blacks

jr. member

Activity: 119

Merit: 3

@dropky

Quote from: dropky on January 22, 2018, 06:00:41 AM

We've just pushed out a new version:
https://github.com/nicehash/excavator/releases/tag/v1.4.1a

It includes a fix for issues with the re-connection to the NH stratum servers on Equihash, DaggerHashimoto and CryptoNight.

Quote from: dropky on January 24, 2018, 05:53:37 AM

We uploaded the binary for v1.4.1a compiled with CUDA 9.1.

Excavator compiled with CUDA 9.1 outperforms the one compiled with CUDA 8.0 on some algorithms.

Benchmark results can be found here:
https://github.com/nicehash/excavator/releases/tag/v1.4.1a

sorry i am confuse what's update ? 2 day agow 1.4.1.a > now you say new update but same version ? what's the catch ? & in other way 1.4.1.a Equihash still crash, stall & personaly i give up let a miner run & need to watch all the time because not know when it will crash is become ...

- excavator_v1.4.1a_NVIDIA_Win64.zip = 8.0, 9.0 ??!?!?!
- excavator_v1.4.1a_NVIDIA_Win64_CUDA_9.1.zip only with 9.1 ?!?!?

anyway hope you will fix it in a future

dropky

jr. member

Activity: 132

Merit: 7

We uploaded the binary for v1.4.1a compiled with CUDA 9.1.

Excavator compiled with CUDA 9.1 outperforms the one compiled with CUDA 8.0 on some algorithms.

Benchmark results can be found here:
https://github.com/nicehash/excavator/releases/tag/v1.4.1a

dropky

jr. member

Activity: 132

Merit: 7

We've just pushed out a new version:
https://github.com/nicehash/excavator/releases/tag/v1.4.1a

It includes a fix for issues with the re-connection to the NH stratum servers on Equihash, DaggerHashimoto and CryptoNight.

dropky

jr. member

Activity: 132

Merit: 7

Quote from: m1n1ngP4d4w4n on January 20, 2018, 08:55:51 AM

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)

I'll take a look into this. We haven't made any changes on keccak though.

dropky

jr. member

Activity: 132

Merit: 7

Quote from: opeth2112 on January 19, 2018, 05:25:06 PM

Quote from: opeth2112 on January 19, 2018, 05:04:13 PM

Quote from: dropky on January 19, 2018, 04:36:21 AM

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.

As you have already figured it out, you have to increase the virtual memory to avoid 'cuda out of memory' issues.

dropky

jr. member

Activity: 132

Merit: 7

Quote from: MarkAz on January 19, 2018, 12:04:08 PM

Quote from: dropky on January 19, 2018, 04:36:21 AM

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?

We'll upload linux builds shortly.

NoSubstitute

newbie

Activity: 10

Merit: 0

Quote from: sir_blacks on December 27, 2017, 08:24:10 AM

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.

m1n1ngP4d4w4n

full member

Activity: 224

Merit: 100

CryptoLearner

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)

opeth2112

newbie

Activity: 5

Merit: 0

Quote from: opeth2112 on January 19, 2018, 05:04:13 PM

Quote from: dropky on January 19, 2018, 04:36:21 AM

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.

opeth2112

newbie

Activity: 5

Merit: 0

Quote from: dropky on January 19, 2018, 04:36:21 AM

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?

MarkAz

hero member

Activity: 687

Merit: 511

Quote from: dropky on January 19, 2018, 04:36:21 AM

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

newbie

Activity: 5

Merit: 0

Quote from: dropky on January 19, 2018, 04:36:21 AM

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.

dropky

jr. member

Activity: 132

Merit: 7

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.

stzcze

jr. member

Activity: 109

Merit: 1

Quote from: dropky on January 17, 2018, 07:27:43 AM

Quote from: dropky on January 17, 2018, 04:33:17 AM

Quote from: stzcze on January 16, 2018, 04:55:06 PM

{"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

sir_blacks

jr. member

Activity: 119

Merit: 3

Quote from: Bimmber on January 17, 2018, 09:14:27 AM

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

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 Wink

chers

Bimmber

newbie

Activity: 210

Merit: 0

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

dropky

jr. member

Activity: 132

Merit: 7

Quote from: dropky on January 17, 2018, 04:33:17 AM

Quote from: stzcze on January 16, 2018, 04:55:06 PM

{"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.

dropky

jr. member

Activity: 132

Merit: 7

Quote from: stzcze on January 16, 2018, 04:55:06 PM

{"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)?

stzcze

jr. member

Activity: 109

Merit: 1

{"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

jr. member

Activity: 132

Merit: 7

Quote from: m1n1ngP4d4w4n on January 15, 2018, 03:03:55 PM

Quote from: dropky on January 15, 2018, 12:57:26 PM

Quote from: m1n1ngP4d4w4n on January 15, 2018, 10:39:43 AM

Quote from: dropky on January 15, 2018, 09:34:04 AM

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 Wink

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 Wink

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

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