Hmm... Very interesting.
ccminer is GPL'ed, no?
The source code should be available.
By the way, I was finally able to get the GDS working on Windows on the AMD land.
It has been so long playing catch up with Claymore's and Optiminer...
Topic: excavator by NiceHash - multi-algorithm NVIDIA GPU miner [1.5.6a] - page 53. (Read 179296 times)
May 08, 2017, 12:50:36 PM
May 08, 2017, 12:43:52 PM
Look on https://github.com/palginpav/ccminer/releases/tag/2.1-equihash_test
715 hash on 1080 non ti!
Try to test on nicehash - dont work. But on zpool works good.
1. Highly unrealistic speed up.715 hash on 1080 non ti!
Try to test on nicehash - dont work. But on zpool works good.
2. Why would someone post 3 different solvers with so big speed difference? Why not simply put up the fastest?
3. No source code - beware of possible malware!!!
The 3rd exefile is 64mb big. #1 is 32mb
May 08, 2017, 12:20:26 PM
Look on https://github.com/palginpav/ccminer/releases/tag/2.1-equihash_test
715 hash on 1080 non ti!
Try to test on nicehash - dont work. But on zpool works good.
715 hash on 1080 non ti!
Try to test on nicehash - dont work. But on zpool works good.
1. Highly unrealistic speed up.
2. Why would someone post 3 different solvers with so big speed difference? Why not simply put up the fastest?
3. No source code - beware of possible malware!!!
May 08, 2017, 09:29:30 AM
Look on https://github.com/palginpav/ccminer/releases/tag/2.1-equihash_test
715 hash on 1080 non ti!
Try to test on nicehash - dont work. But on zpool works good.
715 hash on 1080 non ti!
Try to test on nicehash - dont work. But on zpool works good.
Area you getting the same speed on the pool though? I am only getting about 40% of what the miner says.. on yiimp.
May 08, 2017, 07:55:58 AM
Look on https://github.com/palginpav/ccminer/releases/tag/2.1-equihash_test
715 hash on 1080 non ti!
Try to test on nicehash - dont work. But on zpool works good.
715 hash on 1080 non ti!
Try to test on nicehash - dont work. But on zpool works good.
May 05, 2017, 11:23:06 PM
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?
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?
I assume you are referring to NiceHash Miner. You can't set these parameters there (yet).
Yes, that was what I meant. Tx for the explanation. Good to hear it will be there in the future, as I guess each algorithm has slightly different oc values that you can find and set apriori, and dont have to rely on afterburner, which would give only on set of oc values.
May 05, 2017, 02:48:20 PM
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?
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?
I assume you are referring to NiceHash Miner. You can't set these parameters there (yet).
May 05, 2017, 01:37:45 PM
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?
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?
Nobody is picking this up? Let me take a look after I'm done with the Equihash binary kernel.
May 05, 2017, 03:01:04 AM
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?
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?
May 04, 2017, 06:05:54 PM
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...
I am running a stress test on the new Equihash kernel now. So far, so good...
May 04, 2017, 03:20:09 PM
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.
May 04, 2017, 03:10:44 PM
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.
May 04, 2017, 01:08:35 PM
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!
May 04, 2017, 04:00:01 AM
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.
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.
May 03, 2017, 05:08:34 PM
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!
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.
May 03, 2017, 10:41:20 AM
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!
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!
May 03, 2017, 04:11:25 AM
Quote from: 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.
May 03, 2017, 03:35:57 AM
Quote from: zawawa
Oh, there will be a lot of goodies coming for both NVIDIA and AMD users.
What about Linux users?
May 03, 2017, 01:21:32 AM
By the way, excavator turned out to be at least 5% faster than my open-source miner with Pascal on RX 480. Good stuff.
May 03, 2017, 01:17:30 AM
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...
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.
Jump to: