Mining... am I doing it right?

slim6y

Here is a screenshot of the opening responses when CCMiner is running.

https://drive.google.com/open?id=137OCCyC6kyFS-GH3ya3mPv1fVDJHVYtZ

Here is a copy of the CCMiner config (I just wrote “neoscrypt” where it says algo, is that ok to do?).

https://drive.google.com/open?id=1-tSQx6EoD_d2z8jXbSOVd7qJxNCjDBuW

But since beginning, this appears to be the usual output. With not many “Yes!” responses.

https://drive.google.com/open?id=1hSPigvGaYW8gZpsy8dun6SgfvBA2jGoP

What can you suggest?

ghostlander

NeoScrypt CUDAminer: https://github.com/ghostlander/cudaminer-neoscrypt

~800KH/s on a GTX 1060.

marecek666

change ccminer version, GTX1060 should give about 750-800kh/s in neoscrypt.

Check correct mining rates here:
https://forum.feathercoin.com/topic/9606/a-bit-of-a-noob-here/8

and the third screenshot is normal. There are some accepted shares, but there is not visible worker diff set from pool side. It is possible that pool set a bit higher worker/share diff for your miner so there is accepted share in longer period. Or if you are SOLO mining, it is normal too. Lines with accepted share (YES) are the blocks found by your miner.

If you use nvidia driver 384.xx then you should use ccminer alexis with intensity set to around 13.5 - 14 - 14.5, works great at almost every system.

Under ccminer you use there is 65536 cuda threads used (intensity 21). The same value you should find by tuning intesity under ccminer alexis. But do not be surprised, it will be different I- number. And 65536 is the max reasonable for GTX1060. My miner is doing 775kh/s with I-14 (16384 cuda threads, gpu temp is max 69) now, and the desktop is usable for work and browsing the Internet without problems.

ghostlander

It doesn’t matter much what driver version is in use. All CUDA miners have kernels built at the compile time by a specific CUDA toolkit.

marecek666

@ghostlander said in Mining... am I doing it right?:

It doesn’t matter much what driver version is in use. All CUDA miners have kernels built at the compile time by a specific CUDA toolkit.

but it does matter. eg, using alexis with driver newer than 184.xx gives only half of hashrate and does not matter how is intensity set. It has something to do with used CUDA version. I am windows user and I am not able to compile ccminer directly to my system, so I would depend on what is available on the internet.
If I use later driver than 184 and want to use alexis - it gives me max about 450kh/s.
Using tpruvot with the latest driver gives me back about 770kh/s.