 Show Posts
|
|
Pages: [1]
|
|
The motherboard chipset has pcie lanes as well. The B250 has 12 lanes.
|
|
|
|
I want to say that I got around 710 with DSTM. I pretty much try them all as they release new versions. I end up sticking with Excavator due to better hash and no fees. I also get better hash with lyra2rev2. I run 3 workers with it.
Do you mean for your GPU, the excavator is faster than DSTM? How about the power consumption? When using same tdp and clocks, excavator will out performs. When comparing 2 different miners, I always use the same settings. I change up settings depending on different variables. I will go for max hash some days, others I go for max hash per watt. |
|
|
|
|
What hash rate should I expect from titan x pascal (2016 version). I have not found any miner better than excavator with same settings. I get around 760 h/s.
|
|
|
|
|
I want to say that I got around 710 with DSTM. I pretty much try them all as they release new versions. I end up sticking with Excavator due to better hash and no fees. I also get better hash with lyra2rev2. I run 3 workers with it.
|
|
|
|
|
@Kaan3000,
Give it a try using M=1 and 2 workers. I am using Titan X (pascal) from 2016 and get steady 755-760 h/s. I find pascal cards do better with 2 workers and maxwell with 1 worker.
|
|
|
|
|
Thanks for the information Dropky.
|
|
|
|
As promised I uploaded a simple benchmark script for excavator - https://github.com/nicehash/excavator/blob/master/excavator-benchmark.pyPython 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. |
|
|
|
Hey Nicehash,
I am starting to really enjoy using Excavator. Unless I am missing something, any thought on add the ability to device print speed? This would sum up all the workers for that device.
For doo that you need to edit json file like this: {"time":3,"commands":[
{"id":1,"method":"worker.add","params":["0","0","0"]},
{"id":1,"method":"worker.add","params":["0","0","0"]},
{"id":1,"method":"worker.add","params":["0","1","0"]},
{"id":1,"method":"worker.add","params":["0","1","0"]}
]},
{"time":10,"loop":10,"commands":[
{"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"worker.print.speed","params":["1"]},
{"id":1,"method":"algorithm.print.speeds","params":["0"]}
]}
this it will add 2 worker / 1 device in M-0 Mode Be ware it depend by what algoritm it is use ["0","0","0"] = 0 = Device 0, 0 = worker 0, 0 = M0 mining mode (remove if you want default M1) This section it will make miner to print speed at how many worker you was add first {"id":1,"method":"worker.print.speed","params":["0"]},
{"id":1,"method":"worker.print.speed","params":["1"]},
This is same as what I am doing. It prints speed for each worker, not total for the device. |
|
|
|
|
Using risers, the max will be 4.
|
|
|
|
|
Hey Nicehash,
I am starting to really enjoy using Excavator. Unless I am missing something, any thought on add the ability to device print speed? This would sum up all the workers for that device.
|
|
|
|
|
