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

[Bimmber]

dropky, new Nvidia drivers have been released, 390.77 on 29th of January. Should we update or keep previous drivers?

[dropky]

dropky, new Nvidia drivers have been released, 390.77 on 29th of January. Should we update or keep previous drivers?

I didn't have a chance to test them out yet. There shouldn't be any significant difference in performance though. Hopefully, I'll have some time to try them out in the next couple of days. You can update them and if they turned out to be unstable, you can always downgrade to an older version.

[dropky]

As promised I uploaded a simple benchmark script for excavator - https://github.com/nicehash/excavator/blob/master/excavator-benchmark.py

Python 3 is required!

Examples:

1. benchmark algorithm 1 on device 0
python excavator-benchmark.py --excavator path_to_excavator -a algo1 -d 0 -b

2. benchmark all algorithms on all devices
python excavator-benchmark.py --excavator path_to_excavator -b

3. benchmark on nicehash pool (default is eu server)
python excavator-benchmark.py --excavator path_to_excavator -u btc_address

Default time for benchmark is 300 seconds per algorithm, you can modify it with -t parameter.

[dropky]

does anyone have an example of a command.json file with multiple algorithms and multiple GPU's? I have updated the config but it doesn't seem to recognize after restarting.

Here is an example - running daggerhashimoto on first GPU and neoscrypt on second and third.

Code:

[
	{"time":0,"commands":[
		{"id":1,"method":"algorithm.add","params":["daggerhashimoto","daggerhashimoto.eu.nicehash.com:3353","btc_addr.algo0"]},
		{"id":1,"method":"algorithm.add","params":["neoscrypt","neoscrypt.eu.nicehash.com:3341","btc_addr.algo1"]}
	]},
	{"time":3,"commands":[
		{"id":1,"method":"worker.add","params":["0","0"]},
		{"id":1,"method":"worker.add","params":["1","1"]},
		{"id":1,"method":"worker.add","params":["1","2"]}
	]},
	{"time":10,"loop":10,"commands":[
		{"id":1,"method":"algorithm.print.speeds","params":[]}
	]},
	{"time":15,"commands":[
		{"id":1,"method":"worker.reset","params":["0"]},
		{"id":1,"method":"worker.reset","params":["1"]},
		{"id":1,"method":"worker.reset","params":["2"]}
	]}
]

[Kompik]

Any speed improvements in the new version today?

[dropky]

Any speed improvements in the new version today?

Unfortunately, no The main purpose of today's release was support for TITAN V.

[sir_blacks]

Any speed improvements in the new version today?

Unfortunately, no The main purpose of today's release was support for TITAN V.

no offense, sorry to say but better to try to fix & make miner stable & reliable first how it was in past before 9.1 cuda & driver came, see my feedback on github

cheers & hoping to see agen excavator stable as a rock how it was !!!

[Kompik]

Excavator is amazing, stable and the speeds are usually very competitive. It will not last long and it will be the best miner out there for most of the algos.

[sir_blacks]

Excavator is amazing, stable and the speeds are usually very competitive. It will not last long and it will be the best miner out there for most of the algos.

a litle correction
- Excavator it have potential to become amazing = true
- Stable = sorry negative on equihash algoritm is like play rusion rulet now it work, now it crash for no particulary reason
- Speeds = dev yes they work to tune & make it competitive

but if miner is unstable & unrilable part with best miner out of discution, no offense

today test run "1.4.3 alpha", hoping with "bug fixes & improvements" equihash was fix & nop same problem what i say from few version agow

Code:

- Test Excavator Start
    [[2018-02-02 12:44:36.164770] [thread=0x000010d8] [info]]
- Miner Stall > Crash (i check log & see moment when speed was drop)
    [[2018-02-02 13:00:47.461761] [thread=0x00000a10] [info]]
- I stop manually miner seen him stall, coming back to pc, from what i was need to do in house
    [[2018-02-02 13:10:51.452607] [thread=0x000010d8] [info]]
    Shutting down
- Open / Start Excavator agen
- Crash agen
[[2018-02-02 13:53:57.508518] [thread=0x000011e0] [info]]

yup very stable ... but my be excavator he not like me after abandon him from 1.3.2a & switch to other miner, because speed competition if we can joke
cheers

[Kayfolom]

The first release of the MinerPro for Nicehash is published. Very interested in your opinion about the application.

https://github.com/EvgeniyKorepov/MinerPro-for-NiceHash

Short demo video https://youtu.be/zN5rWmuU2mc

You must download and run the Excavator yourself on your farms. The application does not start the excavator, it controls local or remote instances of the miner.

Features

• The calculation of profits is made taking into account the cost of electricity. Including different cost of electricity during the day.
• Individual overclocking GPUs for each algorithm.
• Fine-tuning the parameters of algorithms.
• Ability to change parameters of the overclocking during operation.
• Fast, less than one second, switch between algorithms.
• Failover - switching to other locations when the stratum server fails.
• Dev fee 0.8% (one minute in two hours).

[sir_blacks]

because usual i like to find a fix to a problem, after reading more about https://github.com/nicehash/excavator/tree/master/api i was say hey let try to use "device.set.power_limit" setting my be i will make Excavator to be stable & work nice agen!!! so i set 86W limit (this is my target set already in Afterburner) to be sure it will never exceed that value & GPU Clock it will never goo more that 1860 Mhz. SURPRISE Excavator FAIL to obey / fallow his OWN fraking setting ending crashing GPU clock (2088 - 2216) => ending crashing himself !!! Way ?!?!? i will like to undestend but that's dev job to look in code & see way is out of control, way he can't fallow his own setting ... way can't be stable

Setting extra add in json:

Code:

	{"time":5,"commands":[
		{"id":1,"method":"device.set.power_limit","params":["0","86"]}
	]},

i make a image to show working stable miner & unstable one on crash moment see below

[Kompik]

Excavator is amazing, stable and the speeds are usually very competitive. It will not last long and it will be the best miner out there for most of the algos.

a litle correction
- Excavator it have potential to become amazing = true
- Stable = sorry negative on equihash algoritm is like play rusion rulet now it work, now it crash for no particulary reason
- Speeds = dev yes they work to tune & make it competitive

but if miner is unstable & unrilable part with best miner out of discution, no offense

today test run "1.4.3 alpha", hoping with "bug fixes & improvements" equihash was fix & nop same problem what i say from few version agow

Code:

- Test Excavator Start
    [[2018-02-02 12:44:36.164770] [thread=0x000010d8] [info]]
- Miner Stall > Crash (i check log & see moment when speed was drop)
    [[2018-02-02 13:00:47.461761] [thread=0x00000a10] [info]]
- I stop manually miner seen him stall, coming back to pc, from what i was need to do in house
    [[2018-02-02 13:10:51.452607] [thread=0x000010d8] [info]]
    Shutting down
- Open / Start Excavator agen
- Crash agen
[[2018-02-02 13:53:57.508518] [thread=0x000011e0] [info]]

yup very stable ... but my be excavator he not like me after abandon him from 1.3.2a & switch to other miner, because speed competition if we can joke
cheers

I mean why would you even mine equihash with this miner? That is one of the algos that excavator is not competitive. Both DTSM or Bminer are much faster, even EWBF is faster

[DumaxFr]

because usual i like to find a fix to a problem, after reading more about https://github.com/nicehash/excavator/tree/master/api i was say hey let try to use "device.set.power_limit" setting my be i will make Excavator to be stable & work nice agen!!! so i set 86W limit (this is my target set already in Afterburner) to be sure it will never exceed that value & GPU Clock it will never goo more that 1860 Mhz. SURPRISE Excavator FAIL to obey / fallow his OWN fraking setting ending crashing GPU clock (2088 - 2216) => ending crashing himself !!! Way ?!?!? i will like to undestend but that's dev job to look in code & see way is out of control, way he can't fallow his own setting ... way can't be stable

Setting extra add in json:

Code:

	{"time":5,"commands":[
		{"id":1,"method":"device.set.power_limit","params":["0","86"]}
	]},

i make a image to show working stable miner & unstable one on crash moment see below
... img removed see orginal post ...

Your mistake is to believe that power_limit is an absolute power value. It's a ratio like in MSI afterburner : a value of 100 is equivalent to the max "official" TDP of your card.
Try with a value of 72 like the one you are using in MSI Afterburner and you shall be in line to compare.

Edit : didn't watched this API before nor using this miner, then saw there was a tdp method.
Did you try to read the value before applying a value (device.get.power_limit) ?

[sir_blacks]

@DumaxFr api it have 2 option power_limit = max power in W or tdp in % booth are yes relative value no GPU it will stay on exact value what it will be set & yes it will be +/- variation, but problem is when an application can't fallow his own setting & exceed to much like in my case, for that i will give you few scenario below:

- GPU TDP = 72% = ~86W = ~1860 Mhz = good ration = normal working
- GPU TPD = 72% = ~86W = ~2216 Mhz = miner it will crash & GPU it will to
- GPU TDP = 72% = ~88W = ~1888 MHz fine in range of max with +/-
- GPU TDP = 72% = ~90W = ~1847 Mhz = Bad aka application exceed limit result escape out of control

anyway no matter what Excavator it do something what make GPU to hit max with bad power ratio & ending booth screw up, so back to my point Excavator it need to be tech to be "good boy" because 1. it can fry equipment 2. it end not doing his job 3. it consume power for nothing

@Lexabush is a difference between that & yes @DumaxFr i read it before i use it
A. device.set.power_limit = string = New power limit in Watts.

https://github.com/nicehash/excavator/tree/master/api#-devicesetpower_limit
- so you set real W power what you want to be max

Code:

{"id":1,"method":"device.set.power_limit","params":["0","86"]}

B. device.set.tdp = string = New TDP limit %.
https://github.com/nicehash/excavator/tree/master/api#-devicesettdp

- so you set % of Power what you want to be use

Code:

{"id":1,"method":"device.set.tdp","params":["0","72"]}

[sir_blacks]

for who are confuse about TPD & Real W Power & GPU Clock Ration i made a picture

https://i.imgur.com/ejH72Yp.png


cheers

[DumaxFr]

for who are confuse about TPD & Real W Power & GPU Clock Ration i made a picture

https://i.imgur.com/ejH72Yp.png
https://i.imgur.com/ejH72Yp.png

cheers

Oh You complicate everything

If you need "Power Limit" MSI Afterburner 72% in Excavator you must write:
{"id":1,"method":"device.set.tdp","params":["0","72"]}

MSI Afterburner "Power Limit" = Excavator "device.set.tdp" understandably ?

Agree !

I would add that, as an old school overclocker, I don't use TDP/Power/Temp limits as adjustment variables but only as a security.
If you set the proper Core Freq / Voltage to reach stability you won't be bothered with sampling issues of the power limiter.

[Dr_Thrax]

Is there a way to use excavator without .json files? Just the batch file like other miners like ccminer, sgminer or claymore

[Yenbus]

As promised I uploaded a simple benchmark script for excavator - https://github.com/nicehash/excavator/blob/master/excavator-benchmark.py

Python 3 is required!

Examples:

1. benchmark algorithm 1 on device 0
python excavator-benchmark.py --excavator path_to_excavator -a algo1 -d 0 -b

2. benchmark all algorithms on all devices
python excavator-benchmark.py --excavator path_to_excavator -b

3. benchmark on nicehash pool (default is eu server)
python excavator-benchmark.py --excavator path_to_excavator -u btc_address

Default time for benchmark is 300 seconds per algorithm, you can modify it with -t parameter.

Any way to edit the script to use multiple workers?  It would be nice if this could be dynamic based on the algo.

[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

[Dragstar]

Which is better this or hsr?