I tested the built-in ccminer vs Excavator (1.4.2.a) on AHashPool and found that Excavator is faster as follows:
Blake2s - 16% Faster
NeoScrypt - 30% Faster
These figures are nothing to joke about when it comes to dollars.
I hope the author seriously considers at least upgrading to the latest Excavator. Otherwise we are all loosing money big time.
(Note: I was able to configure the latest Excavator to run with AM, it can start/stop/monitor it, but does not report any metrics). And profit switching of course does not work.
Sadly, while some excavator support was added as 'External Miner", its pretty pointless for using with Profit switching.
If anyone is using these algos with built-in miner, then they are literally throwing money down the toilet. I simply can't use AM with this situation.
Only when he pointed out the miner chose him as ccminer, not excavator(latested)
Hashrefinery_NeoScrypt_1J6ERS9LjhRhXkifkVfdpbP56aY7TLqEoe_1.json
{
"time": 0,
"commands": [
{
"id": 1,
"method": "algorithm.add",
"params": [
"neoscrypt",
"204.27.59.90:4233",
"1J6ERS9LjhRhXkifkVfdpbP56aY7TLqEoe:home_video_card,c=BTC"
]
}
]
},
{
"time": 3,
"commands": [
{
"id": 1,
"method": "worker.add",
"params": [
"0",
"0"
]
}
]
},
{
"time": 3,
"commands": [
{
"id": 1,
"method": "worker.add",
"params": [
"0",
"1"
]
}
]
},
{
"time": 3,
"commands": [
{
"id": 1,
"method": "worker.add",
"params": [
"0",
"2"
]
}
]
},
{
"time": 3,
"commands": [
{
"id": 1,
"method": "worker.add",
"params": [
"0",
"3"
]
}
]
},
{
"time": 3,
"commands": [
{
"id": 1,
"method": "worker.add",
"params": [
"0",
"4"
]
}
]
},
{
"time": 3,
"commands": [
{
"id": 1,
"method": "worker.add",
"params": [
"0",
"5"
]
}
]
},
{
"time": 10,
"loop": 10,
"commands": [
{
"id": 1,
"method": "algorithm.print.speeds",
"params": [
"0"
]
}
]
}
]
how to make an analogy for this file to be for all pools and to take pools from AM