Lyra2REv2 low hashrate on pools

[Atexor]

Hi Few months ago I was trying to mine MonaCoin on Mining Pool Hub, but I noticed that pool detects ~30mh/s although the miner was showing ~50mh/s.

Few hours ago I wanted to check it again because someone had told me that it gives better results than ccminer for Lyra2REv2. So I downloaded latest version to mine Straks coin on datapaw pool and noticed the same issue: https://i.imgur.com/4HwTiP7.png

OS: Windows 10 PRO x64 GPU: ASUS ROG STRIX-GTX1080-O8G

Could you take a look on it? I'm using standard config with one worker:

[
    {"time":0,"commands":[
        {"id":1,"method":"algorithm.add","params":["lyra2rev2","pool.datapaw.net:4533","my_wallet"]}
    ]},
    {"time":3,"commands":[
        {"id":1,"method":"worker.add","params":["0","0"]}
    ]},
    {"time":10,"loop":20,"commands":[
        {"id":1,"method":"worker.print.speed","params":["0"]},
        {"id":1,"method":"algorithm.print.speeds","params":["0"]}
    ]}
]

[swamprunner7]

Same, using ccminer nanashi for now.

[Atexor]

Which graphics card do you have? The same as me? I'm using ccminer nanashi too.

Maybe it's issue only with our GPUs.

[swamprunner7]

1080ti, real 70Mh on nanashi, strange 74Mh on excavator in console but only ~half in the pool.

[t4nja]

Which version of excavator are you using?

[swamprunner7]

v1.4.4a

[Atexor]

1.4.4a too but noticed that issue on 1.3.8a version few months ago.

[swamprunner7]

Seems like when nicehash miner 2 using it, console showing same results like nanashi ~70

[t4nja]

This problem happens only on one pool? Which one? For which coin?

[swamprunner7]

Looked again, actually no, nicehashminer2 doing right now 74Mh on Lyra2v2, so something wrong with excavator for other pools, because pool instantly showing correct data from nanashi not from excavator.

[swamprunner7]

Tried xvg-lyra.suprnova.cc

[Atexor]

1.3.8a few months ago - Monacoin on https://miningpoolhub.com/ 1.4.4a now - Straks on https://datapaw.net/

Both coins using lyra2rev2 algo. Both pools detects ~50-60% of the hashrate in miner.

[t4nja]

I can't reproduce the same issue when using NiceHash stratum and since we recently dropped the support for other pools there isn't much I can do at the moment.

[Atexor]

I don't use stratum in excavator because I can't connect with it to any pool, even to nicehash {"id":1,"method":"algorithm.add","params":["lyra2rev2","stratum+tcp://lyra2rev2.eu.nicehash.com:3347","address.worker"]}

I don't know whether excavator supports it, hovewer I can check it with supported pools/connecting methods (with/without stratum). Just let me know how to configure it if you want.

[borzaka]

I'am experiencing the the same issue; lyra2rev2 pool side hashrate is almost half as shown in the miner.

I have a following setup:

• 3x 1080 Ti
• 3x 1070 Ti
• Excavator Version 1.4.4 alpha NVIDIA
• A Hash Pool lyra2v2 algo
• 395 MH/s lyra2rev2 performance with overclocks:

But on the pool side, my hashrate is fluctuating, and the average hashrate is almost half compared with the miner: And my earnings after 24 hour is almost half as well: whattomine 24 hour estimate. It was not even near.

What's the problem? When I was mining NeoScrypt with Excavator to the same pool, the graph was accurate, as my earnings.

This is my config: AHashPool_Lyra2RE2_config.txt

I know, that the new versions of Excavator doesn't support other pools, but this issue maybe still present.

[t4nja]

@Atexor

I don't use stratum in excavator because I can't connect with it to any pool, even to nicehash {"id":1,"method":"algorithm.add","params":["lyra2rev2","stratum+tcp://lyra2rev2.eu.nicehash.com:3347","address.worker"]}

Stratum URL has to be without stratum+tcp:// prefix. You should call algorithm.add method like this: {"id":1,"method":"algorithm.add","params":["lyra2rev2","lyra2rev2.eu.nicehash.com:3347","address.worker"]}

Let me know if you have any issues with the pool speed.

[t4nja]

@borzaka Try using one worker per device.

[swamprunner7]

I'm using gui by cTnko, and just pool address without protocol and get same result. Just tried 6 jobs for each card, speeds not correct too, and because job only for one card each time, seems like it's taking only low difficulty.

[Atexor]

@dropky I can't find any charts for my hashrate on nicehash, but it shows my 55-70 MH/s (I've ~52) there: https://www.nicehash.com/miner/my_address

So it looks that excavator works only on nicehash but on any others pools it's sadly broken. I realise that you said that others pools are unsupported hovewer it's really strange.

[swamprunner7]

neoscrypt working ok anywhere, just tried, on excavator

[Atexor]

Hovewer there are other algos too. There is a bug somewhere with lyra2rev2 so I reported it.

[swamprunner7]

Until it will be fixed, i trying other algos with neoscrypt :)

[borzaka]

@dropky I have tried with one worker per device. The results are the same; pool side hashrate is almost half.

Excavator reports that I have 394 MH/s:

A Hash Pool sees only half at average, and it's very fluctuating: ~12 hour testing

This is my one worker per device config: AHashPool_Lyra2RE2_1worker_config.txt

[swamprunner7]

I tried neoscrypt again for hour, seems like same stuff. On start doing great speed and pool showing it but after few minutes 5% rejected shares and speed drop.

[borzaka]

I have no problem with NeoScrypt on A Hash Pool, the pool side hashrate is same as shown in the miner as should be.

[apiontek]

I have experienced this problem as well. Tested and got the same results on both ahashpool and miningpoolhub.

I also have consistently about 15% lower results from excavator with Neoscrypt, as compared with KlausT ccminer.

[t4nja]

So it looks that excavator works only on nicehash but on any others pools it's sadly broken. I realise that you said that others pools are unsupported hovewer it's really strange.

I'm closing this issue since the problem can't be reproduced on NiceHash stratums (and support for other pools was dropped).