HSRMINER Neoscrypt Fork by Justaminer - New Version!

[ruplikminer]

Gotta agree. Moved from KlausT to this miner and I had an nice increase. I went from a total of 27.9 average to 29.1 MH/s
not bad
Try to push it a bit moar!

[1714655647]

1714655647

[giveen1]

hp gives about 5-8 h/s more per card for me on my 1060's. Same settings I always use, but not at home to see what power consumption looks like on the kill-a-watt, but CPU did jump to 20% usage.

[Mpanda]

Ty dev, works well and nice for a change without dev fee. Thanks for being honest 

[yrk1957]

Nicehash Excavator is faster than this:

3.55 MH/s vs 3.40 MH/s with 2x1080Ti.

[Just_a_miner]

hp gives about 5-8 h/s more per card for me on my 1060's. Same settings I always use, but not at home to see what power consumption looks like on the kill-a-watt, but CPU did jump to 20% usage.

not much, you can just use normal version then to reduce load on gpus as hashrate remains almost same.

Ty dev, works well and nice for a change without dev fee. Thanks for being honest 

Thanks man, hope you like it, feedback any issues.

Nicehash Excavator is faster than this:

3.55 MH/s vs 3.40 MH/s with 2x1080Ti.

Wasn't able to get higher hashrates with Excavator, added benchmark result to 1st msg of the topic. Default settings gave me 1241 kh/s. When I manually run Excavator with Cuda 9.1 it gives more, about 1276 kh/s but still doesn't reach Hsrminer_neoscrypt_fork hashrate.

[yrk1957]

hp gives about 5-8 h/s more per card for me on my 1060's. Same settings I always use, but not at home to see what power consumption looks like on the kill-a-watt, but CPU did jump to 20% usage.

not much, you can just use normal version then to reduce load on gpus as hashrate remains almost same.

Ty dev, works well and nice for a change without dev fee. Thanks for being honest 

Thanks man, hope you like it, feedback any issues.

Nicehash Excavator is faster than this:

3.55 MH/s vs 3.40 MH/s with 2x1080Ti.

Wasn't able to get higher hashrates with Excavator, added benchmark result to 1st msg of the topic. Default settings gave me 1241 kh/s. When I manually run Excavator with Cuda 9.1 it gives more, about 1276 kh/s but still doesn't reach Hsrminer_neoscrypt_fork hashrate.

Maybe its card specific, as your tests are with 1070 and mine with 1080ti.

[jagauthier]

@just_a_miner

Are you able to make the "overall speed" messaging appear more frequently?

[Just_a_miner]

@just_a_miner

Are you able to make the "overall speed" messaging appear more frequently?

Probably yes, I will see what can be done.

Maybe its card specific, as your tests are with 1070 and mine with 1080ti.

It's very strange because users report ~1.9 mh/s hashrate for one 1080ti (and 17.05 mh/s for a rig with 9 cards), so with 2 cards you should get about 3.8 mh/s and not 3.55 or even 3.4.

[melpheos]

testing on my three rigs with high priority version.
Will check average hashrate on pool in a few hours to compare
Shown hashrate is definitively higher on rig but needs to wait report on the pool to confirm

edit : i can confirm that the average hashrate on the pool is higher by a factor of 1500M/hs going from 23400 -> 25000. This is real

[d5coupe]

Does other people pool speeds vary?  I see it vary greatly, from like 7MH/s to 25MH/sec

How to get average speed on nice hash?  anyone?

[melpheos]

Does other people pool speeds vary?  I see it vary greatly, from like 7MH/s to 25MH/sec

How to get average speed on nice hash?  anyone?

check the average, not the instantaneous figure which is far from accurate

[MaynardVII]

Confirmed the -d parameter works correctly now above 10 GPU's. I am dual mining with 12 now.

Justaminer, before I start playing with the new higher intensity program- can I ask what you are OC'ing your 1070's at with the new program, and getting stable results to get a starting benchmark?

[yrk1957]

@just_a_miner

Are you able to make the "overall speed" messaging appear more frequently?

Probably yes, I will see what can be done.

Maybe its card specific, as your tests are with 1070 and mine with 1080ti.

It's very strange because users report ~1.9 mh/s hashrate for one 1080ti (and 17.05 mh/s for a rig with 9 cards), so with 2 cards you should get about 3.8 mh/s and not 3.55 or even 3.4.

Those seem to be at 100% power level. My test were at 70%. Maybe that's why.

[SCSI2]

@JustAMiner: what was the idea behind making a special version with high priority?

I understand why someone might want to use hi-pri to boost the hashrate and on some rigs it does help, but even the original version had the -c parameter (--cpu-priority) which did the trick just fine and that's how I have been using it for a few weeks now.

Also, looks like the _hp version does nothing compared to the regular one. At least not on my 1080Ti rig I'm currently testing it on. Just starting the process with high priority is not enough and perhaps the original ccminer does some more magic to improve the efficiency. Just like it does not help to go into Task Manager and bump up the process priority to High. Might need to look into the original ccminer code to figure out what -c parameter does.

Otherwise, another solid release yet again. I love it! If it reports all the vitals in Awesome Miner via API, I will pay you for the effort.

-scsi

[SCSI2]

Confirming API now reporting vitals as expected in Awesome Miner. See screenshot below.

@Just_a_miner - PM me with your mailing address and I will send you one Delta 2400W server PSU for your effort.

[xxmetalmartyrxx]

Does this fix the deteriorating hashrate issue found with the regular HSR miner?

[SCSI2]

Does this fix the deteriorating hashrate issue found with the regular HSR miner?

In my experience the hashrate does not deteriorate at all even after being running for days non-stop. You sure it was not caused by high temperatures and GPU clock rate throttling in hsr miner?

[melpheos]

Does this fix the deteriorating hashrate issue found with the regular HSR miner?

Detetriorating hashrate is related to nvidia driver crashing and msi afterburner losing access to your card and resetting the o/c settings. Or your cards are temp throttling.
Check your windows log, they will have a nvidia driver error in it i guarantee it if it's not temp throttling

[Just_a_miner]

testing on my three rigs with high priority version.
Will check average hashrate on pool in a few hours to compare
Shown hashrate is definitively higher on rig but needs to wait report on the pool to confirm

edit : i can confirm that the average hashrate on the pool is higher by a factor of 1500M/hs going from 23400 -> 25000. This is real

Thanks for feedback.

Confirmed the -d parameter works correctly now above 10 GPU's. I am dual mining with 12 now.

Justaminer, before I start playing with the new higher intensity program- can I ask what you are OC'ing your 1070's at with the new program, and getting stable results to get a starting benchmark?

Intensity is the same, just miner process priority set to high. My benchmark was done with MSI GTX 1070 Gaming X with PL 90%/+100 core/+400 mem. It works stable. Actually it works even with 80-85pl%/+150 core/+400 mem , I just don't want stress card too much.

[Just_a_miner]

@JustAMiner: what was the idea behind making a special version with high priority?

I understand why someone might want to use hi-pri to boost the hashrate and on some rigs it does help, but even the original version had the -c parameter (--cpu-priority) which did the trick just fine and that's how I have been using it for a few weeks now.

Also, looks like the _hp version does nothing compared to the regular one. At least not on my 1080Ti rig I'm currently testing it on. Just starting the process with high priority is not enough and perhaps the original ccminer does some more magic to improve the efficiency. Just like it does not help to go into Task Manager and bump up the process priority to High. Might need to look into the original ccminer code to figure out what -c parameter does.

Otherwise, another solid release yet again. I love it! If it reports all the vitals in Awesome Miner via API, I will pay you for the effort.

-scsi

Idea was that not everybody know about -c option. Other user was asking how to pass -c under Nicehashminerlegacy, and so on. That's why I decide to set priority to high by default inside program and make it separate version.

As for ccminer, in my benchmark against it I was using highprio version of my fork but with default intensity, and ccminer was running with highpriority AND intensity set to 17 instead of default 15. So no magic.

Confirming API now reporting vitals as expected in Awesome Miner. See screenshot below.

@Just_a_miner - PM me with your mailing address and I will send you one Delta 2400W server PSU for your effort.

Thanks man, but it's too much. If you want to support me, you can send some 0.xx1 of btc or ltc to donation addresses.