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

[stevej]

lol new version 2.0.1.3 removed daggerhashimoto for 3gb cards!!! LOL they dont know till April is profitable?

We decided to drop 3GB cards for daggerhashimoto because the DAG size was getting dangerously close to the 3GB limit and daggerhashimoto didn't even run on these cards especially when they are used as primary cards. This may not be a problem for experienced miners, but the majority of NHM users are casual ones. There are so many things to consider, you know...

I have been trying to figure out why I had no daggerhashimoto on my GTX 1060 3gb rig with NHM. now I know.
But this site below says the dag file is only 2.31gb yet, nowhere near the 3 gb limit ?

https://investoon.com/tools/dag_size

As mentioned before we dropped the daggerhashimoto for 3gb cards because there were a lot of issues/crashes with it among NHM users (especially on primary cards). We could remove the 3gb condition in excavator though, and you can run it without NHM then..

Ok,  then I could use it for external mining ?

[1714927949]

1714927949

[1714927949]

1714927949

[1714927949]

1714927949

[1714927949]

1714927949

[Yenbus]

Thanks for the information Dropky.

[dropky]

During benchmark excavator doesn't connect to the pool, it performs hashing on a test job which is hardcoded in the miner (always the same one). So, no free hashes for us If you don't believe me, you could always try to monitor the network..

Is there any particular reason that you couldn't just mine each particular algo (on the users account obviously), instead of just performing the benchmark?  I would think typically this isn't done because it would take a bunch of pools, but obviously Nicehash does them all, so that isn't an issue... Even if some of them aren't as profitable, it would be better than just burning the power for nothing - and be a real world benchmark.  Just wondering if there is some non-obvious reason...

The perks of performing benchmark on the same job is that it is always performed under the same conditions. Also, we avoid potential server unavailable issues, network delays and lack of orders for the specific algorithm.

[dropky]

As mentioned before we dropped the daggerhashimoto for 3gb cards because there were a lot of issues/crashes with it among NHM users (especially on primary cards). We could remove the 3gb condition in excavator though, and you can run it without NHM then..

Ok,  then I could use it for external mining ?

What do you mean by external mining? You could mine to NH pool just not by using NHM. I'll keep you updated on this.

[dropky]

We released a new version today that includes more neoscrypt improvements for some cards (mainly 1070 & 1060 cards):

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

[stevej]

As mentioned before we dropped the daggerhashimoto for 3gb cards because there were a lot of issues/crashes with it among NHM users (especially on primary cards). We could remove the 3gb condition in excavator though, and you can run it without NHM then..

Ok,  then I could use it for external mining ?

What do you mean by external mining? You could mine to NH pool just not by using NHM. I'll keep you updated on this.

Yes, thats what I meant, external mining to nicehash without NMH

[dropky]

As mentioned before we dropped the daggerhashimoto for 3gb cards because there were a lot of issues/crashes with it among NHM users (especially on primary cards). We could remove the 3gb condition in excavator though, and you can run it without NHM then..

Ok,  then I could use it for external mining ?

What do you mean by external mining? You could mine to NH pool just not by using NHM. I'll keep you updated on this.

Yes, thats what I meant, external mining to nicehash without NMH

I took a look at daggerhashimoto and excavator already supports it on 3GB cards (we've never put the 3GB condition to excavator, it was only added to NHM).  

Here is an example of config file for running dagger on one card:

Code:

[
	{"time":0,"commands":[
		{"id":1,"method":"algorithm.add","params":["daggerhashimoto","daggerhashimoto.eu.nicehash.com:3353","your_btc"]}
	]},
	{"time":3,"commands":[
		{"id":1,"method":"worker.add","params":["0","0"]}
	]},
	{"time":10,"loop":10,"commands":[
		{"id":1,"method":"algorithm.print.speeds","params":[]}
	]}
] 

To run it on 2 cards you just have to add another worker.add method, like this:

Code:

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

First parameter represents the algorithm id, the second one is device id - 0, 1...
Take a look here: https://github.com/nicehash/excavator/tree/master/api#worker-add

You have to run excavator with -c config.json parameter.

[ElMinator]

I really can't make the json work.
I have 8 NVIDIA cards but only 1 is being picked (nescrypt)
What should i do?

[dropky]

I really can't make the json work.
I have 8 NVIDIA cards but only 1 is being picked (nescrypt)
What should i do?

Can I see your json file? You have to add 8 workers, if you have 8 cards.

Code:

{"time":3,"commands":[
	{"id":1,"method":"worker.add","params":["0","0"]},
        {"id":1,"method":"worker.add","params":["0","1"]},
        {"id":1,"method":"worker.add","params":["0","2"]},
        {"id":1,"method":"worker.add","params":["0","3"]},
        {"id":1,"method":"worker.add","params":["0","4"]},
        {"id":1,"method":"worker.add","params":["0","5"]},
        {"id":1,"method":"worker.add","params":["0","6"]},
        {"id":1,"method":"worker.add","params":["0","7"]}
]},

[EvgeniyKorepov]

As mentioned before we dropped the daggerhashimoto for 3gb cards because there were a lot of issues/crashes with it among NHM users (especially on primary cards). We could remove the 3gb condition in excavator though, and you can run it without NHM then..

Ok,  then I could use it for external mining ?

What do you mean by external mining? You could mine to NH pool just not by using NHM. I'll keep you updated on this.

Yes, thats what I meant, external mining to nicehash without NMH

You can try MinerPro for automatic control of the Excavator https://github.com/EvgeniyKorepov/MinerPro-for-NiceHash

[ElMinator]

I really can't make the json work.
I have 8 NVIDIA cards but only 1 is being picked (nescrypt)
What should i do?

Can I see your json file? You have to add 8 workers, if you have 8 cards.

Code:

{"time":3,"commands":[
	{"id":1,"method":"worker.add","params":["0","0"]},
        {"id":1,"method":"worker.add","params":["0","1"]},
        {"id":1,"method":"worker.add","params":["0","2"]},
        {"id":1,"method":"worker.add","params":["0","3"]},
        {"id":1,"method":"worker.add","params":["0","4"]},
        {"id":1,"method":"worker.add","params":["0","5"]},
        {"id":1,"method":"worker.add","params":["0","6"]},
        {"id":1,"method":"worker.add","params":["0","7"]}
]},

So silly, i was missing the "," after each line. Thanks
Do you still support Awsome Miner? I keep getting "failed to open command file -p"

[dropky]

Do you still support Awsome Miner? I keep getting "failed to open command file -p"

You should address this question to them (since they have to support excavator, not the other way around).

[Gnomeks]

We released a new version today that includes more neoscrypt improvements for some cards (mainly 1070 & 1060 cards):

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

Good job, seems to be something around +4.5% on 1070

[DeLemon]

Got it up and running on my 1070 ti for zcash.  The nice part is it is much more stable on submitted shares over the past 2 hours vs DTSM or EFWB.  I like the OC when it is running and turn off when not.  Nice for gamer system that also mines in spare time.

[Cocbit]

Hello.

First of all, im new here so, sorry if i say something stupid but im just starting to learn how all this mining stuff works.

I set up a rig of 4x 1070ti and they are performing really well at 5.81MHs in neoscript, well, at least i think it is a good hashrate.

After a few days optimizing the overclock i made the benchmarks again and all them work without problems except for equihash wich crashes due to clock overload.
This only happens with that algo so i want to know how can i modify the config file to make it stable.
Underclocking doesnt seem a good idea because all other algos work perfectly and with good hashrates.

Thanks in advance for your help

[dropky]

Hello.

First of all, im new here so, sorry if i say something stupid but im just starting to learn how all this mining stuff works.

I set up a rig of 4x 1070ti and they are performing really well at 5.81MHs in neoscript, well, at least i think it is a good hashrate.

After a few days optimizing the overclock i made the benchmarks again and all them work without problems except for equihash wich crashes due to clock overload.
This only happens with that algo so i want to know how can i modify the config file to make it stable.
Underclocking doesnt seem a good idea because all other algos work perfectly and with good hashrates.

Thanks in advance for your help

You could change the overclock settings when you run equihash and set them back to your original settings when you switch to another algorithm. Take a look at device methods: https://github.com/nicehash/excavator/tree/master/api#methods (particularly device.set.core_delta, device.set.memory_delta and device.set.power_limit). 

[grendel25]

why do 1080 perform the same as 1070?  overlooked in optimization?

thx.. and sorry... I'm sure it's been answered by now but I can't just print the thread as a page anymore and word search like the good old days

[dropky]

why do 1080 perform the same as 1070?  overlooked in optimization?

thx.. and sorry... I'm sure it's been answered by now but I can't just print the thread as a page anymore and word search like the good old days

Because of the different memory types, 1070 cards have gddr5 and 1080 have gddr5x - for some algorithms gddr5 seems to be much better (neoscrypt, daggerhashimoto, cryptonight.. ).

[Cocbit]

why do 1080 perform the same as 1070?  overlooked in optimization?

thx.. and sorry... I'm sure it's been answered by now but I can't just print the thread as a page anymore and word search like the good old days

Hello. Thanks gor your answer.

I opened the default_command_file and saw the config but im not sure how i need to add the line to make the excavator underclock only with equihash.

I currently have the overclock with the graphic card software, so i want to reduce the clock around 50 for equihash so it can autoswitch when it is profitable.

Could you help me with that? Thanks

[dropky]

Hello. Thanks gor your answer.

I opened the default_command_file and saw the config but im not sure how i need to add the line to make the excavator underclock only with equihash.

I currently have the overclock with the graphic card software, so i want to reduce the clock around 50 for equihash so it can autoswitch when it is profitable.

Could you help me with that? Thanks

How exactly are you running excavator (standalone or with some miner)? How do you perform switching, you're using different config files for different algorithms or.. ?