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

[SS2006]

i keep my nvidia with ewbf on nicehash, amd with claymore on nicehashminer on nicehash, and cpus on miningpoolhub using multipoolminer.  If nicehash starts supporting Lyra2z, then i'll switch my cpu to nicehash.  currently Lyra2z (zcoin) has been 3 to 4 times more profitable than cryptonight.

Why not use miningpoolhub for all your miners? They charge .9% fee  and you can exchange mined coins to coin of your choice for 0.2% additional fee.
So its 1.1% vs. 3% fee.

And what fee is paid using the nicehash miner?

[1715111218]

1715111218

[1715111218]

1715111218

[1715111218]

1715111218

[1715111218]

1715111218

[kopija]

i keep my nvidia with ewbf on nicehash, amd with claymore on nicehashminer on nicehash, and cpus on miningpoolhub using multipoolminer.  If nicehash starts supporting Lyra2z, then i'll switch my cpu to nicehash.  currently Lyra2z (zcoin) has been 3 to 4 times more profitable than cryptonight.

Why not use miningpoolhub for all your miners? They charge .9% fee  and you can exchange mined coins to coin of your choice for 0.2% additional fee.
So its 1.1% vs. 3% fee.

And what fee is paid using the nicehash miner?

You have a point.
But try using it on Linux or with ewbf miner

[alucard20724]

i keep my nvidia with ewbf on nicehash, amd with claymore on nicehashminer on nicehash, and cpus on miningpoolhub using multipoolminer.  If nicehash starts supporting Lyra2z, then i'll switch my cpu to nicehash.  currently Lyra2z (zcoin) has been 3 to 4 times more profitable than cryptonight.

Why not use miningpoolhub for all your miners? They charge .9% fee  and you can exchange mined coins to coin of your choice for 0.2% additional fee.
So its 1.1% vs. 3% fee.

miningpoolhub tends to be less because of the delay on exchanging coins on the exchanges, whereas with nicehash, i'm selling my hash to users that use nicehash services and not have to deal with exchanges.  I get paid in bitcoins, let someone else deal with the exchanges.

I don't have the time to be a day trader with the exchanges.

i have miningpoolhub set up as my backup though when nicehash fails.

[giagge]

Is there any chance of using excavator with another pool? Maybe with 1 minute fee? . Thank you .

[zawawa]

Is there any chance of using excavator with another pool? Maybe with 1 minute fee? . Thank you .

I don't think excavator is tied to NiceHash pools.
It's a pretty good deal, actually.

[zawawa]

The first version of the OpenCL Pascal kernel seems to be working in the benchmark mode.
The speed is not bad at all at 634 M/h on RX 480. Now let me see if I can connect to pools...

[zawawa]

The pool is accepting shares after fixing a simple bug. Phew!
I think I am getting used to the code base.
Let me see if I can port my Equihash kernel...

[alucard20724]

The pool is accepting shares after fixing a simple bug. Phew!
I think I am getting used to the code base.
Let me see if I can port my Equihash kernel...

if you can get the same speeds or better than ewbf, i'll consider moving my nvidia rigs back to nicehash... preferably better.  ewbf needs some competition again.

[zawawa]

The pool is accepting shares after fixing a simple bug. Phew!
I think I am getting used to the code base.
Let me see if I can port my Equihash kernel...

if you can get the same speeds or better than ewbf, i'll consider moving my nvidia rigs back to nicehash... preferably better.  ewbf needs some competition again.

Oh, there will be a lot of goodies coming for both NVIDIA and AMD users.
Right now, we are focusing on getting popular algos up and running, but once they are all in place, we will work on performance enhancements. The good thing about the modular design of excavator is that it can easily handle dual- and triple-mining, among other things.

[zawawa]

By the way, excavator turned out to be at least 5% faster than my open-source miner with Pascal on RX 480. Good stuff.

[kopija]

Oh, there will be a lot of goodies coming for both NVIDIA and AMD users.

What about Linux users?

[zawawa]

Oh, there will be a lot of goodies coming for both NVIDIA and AMD users.

What about Linux users?

Our plan is to make excavator cross-platform, which, of course includes Linux.
I personally would like to see Mac support as well, but I am not so sure about that.

[baten]

Complete noobie here - both on this forum (this is my first post) and on mining (only started two weeks ago).
Just wanted to thanks everybody on this forum, I learned a lot.

I started on my laptop - a mobile 1070 GTX, and I manage to get it to 410-415 sol/sec at 110 wats (voltage is not adjustable) with +160 clock and 600 mem (micron).

I also got a desktop 1070 Palit - which I managed to get to 430ish at 118 wats, voltage 0,831, +280 clock 600 mem.

In both cases I use 3 instances/threads (I found out I get more stability in the effective hashrate at nicehash/flypool)

Again thanks and keep up the good work!

[zawawa]

Complete noobie here - both on this forum (this is my first post) and on mining (only started two weeks ago).
Just wanted to thanks everybody on this forum, I learned a lot.

I started on my laptop - a mobile 1070 GTX, and I manage to get it to 410-415 sol/sec at 110 wats (voltage is not adjustable) with +160 clock and 600 mem (micron).

I also got a desktop 1070 Palit - which I managed to get to 430ish at 118 wats, voltage 0,831, +280 clock 600 mem.

In both cases I use 3 instances/threads (I found out I get more stability in the effective hashrate at nicehash/flypool)

Again thanks and keep up the good work!

excavator was designed with people like you in mind.
Glad to hear it's working for you.

[zawawa]

I am learning quite a bit from excavator's CUDA code for Equihash.
I may be able to catch up with Claymore and Optiminer after all...
If everything goes well, I should be able to get the first version of Equihash OpenCL kernel running tomorrow.

[patrike]

Excavator's API has a pretty interesting minimalist design philosophy, which is refreshingly different from sgminer etc.

Hi,
I had a quick look at the API of the current release 1.1.4a and although I understand this is just the very beginning, there are some concepts that can be improved. Maybe you are already planning these kind of changes for the 1.2 release? It would also be interesting to learn more about what kind of problems you are addressing by aiming for having an API design that is different from sgminer.

You are for example providing "accepted_per_minute" but no total number of accepted. Accepted Per Minute is actually not very usable for monitoring applications, because you typically want to measure how the value for Accepted is increasing or if it stays the same for a longer period of time. In general it's often better to provide the raw values in the API, instead of hiding the information by grouping it per minute or similar.

I've consumed a number of different mining software API's during the development of Awesome Miner, so if I can be of any help reviewing the API design, please let me know.
Thanks!

[djeZo]

Excavator's API has a pretty interesting minimalist design philosophy, which is refreshingly different from sgminer etc.

Hi,
I had a quick look at the API of the current release 1.1.4a and although I understand this is just the very beginning, there are some concepts that can be improved. Maybe you are already planning these kind of changes for the 1.2 release? It would also be interesting to learn more about what kind of problems you are addressing by aiming for having an API design that is different from sgminer.

You are for example providing "accepted_per_minute" but no total number of accepted. Accepted Per Minute is actually not very usable for monitoring applications, because you typically want to measure how the value for Accepted is increasing or if it stays the same for a longer period of time. In general it's often better to provide the raw values in the API, instead of hiding the information by grouping it per minute or similar.

I've consumed a number of different mining software API's during the development of Awesome Miner, so if I can be of any help reviewing the API design, please let me know.
Thanks!

We are talking about very different API here. You may be used to API that allows you to set pool, but no mining sw currently available allows you to turn devices on/off, turn algorithms on/off and the ability to create multialgorithm mining the way you like it with combination of any algorithms you like. Oh and here comes also the ability to fine tune OC parameters of every single GPU. So... basically, everything you need and no more miner restarts. When it comes to monitoring data you are speaking of, that is just a tip of the iceberg and nothing hard to add; we will take care of that too.

[patrike]

Excavator's API has a pretty interesting minimalist design philosophy, which is refreshingly different from sgminer etc.

Hi,
I had a quick look at the API of the current release 1.1.4a and although I understand this is just the very beginning, there are some concepts that can be improved. Maybe you are already planning these kind of changes for the 1.2 release? It would also be interesting to learn more about what kind of problems you are addressing by aiming for having an API design that is different from sgminer.

You are for example providing "accepted_per_minute" but no total number of accepted. Accepted Per Minute is actually not very usable for monitoring applications, because you typically want to measure how the value for Accepted is increasing or if it stays the same for a longer period of time. In general it's often better to provide the raw values in the API, instead of hiding the information by grouping it per minute or similar.

I've consumed a number of different mining software API's during the development of Awesome Miner, so if I can be of any help reviewing the API design, please let me know.
Thanks!

We are talking about very different API here. You may be used to API that allows you to set pool, but no mining sw currently available allows you to turn devices on/off, turn algorithms on/off and the ability to create multialgorithm mining the way you like it with combination of any algorithms you like. Oh and here comes also the ability to fine tune OC parameters of every single GPU. So... basically, everything you need and no more miner restarts. When it comes to monitoring data you are speaking of, that is just a tip of the iceberg and nothing hard to add; we will take care of that too.

Thanks for the update. cgminer/sgminer do have API's to enable/disable devices and set clocking per GPU, but of course not all the other features you list. I'm looking forward to follow the development of this miner - the concepts sounds interesting.

[zawawa]

Here he is! Better to be explained by the person who designed all this.
I am running a stress test on the new Equihash kernel now. So far, so good...

[baten]

I'm having trouble setting oc parameteres from the api. I works great when I modify the bat file, even better than using afterburner (ad least more stabile).

But when I try to input this on the equihash algoritm extra launch parameters : -ca -ca -ca -os 0 190 600 60 -or it saves it, but it does not apply it when I start the api, even after complete shutdown.

Am I doing something wrong?