HSRMINER Neoscrypt Fork by Justaminer - High Hashrate, API, all GPUs supported! - page 9.

The Godfather

newbie

Activity: 41

Merit: 0

Quote from: Just_a_miner on March 02, 2018, 01:26:33 PM

Quote from: The Godfather on March 02, 2018, 12:18:55 PM

so how much this miner gives on gtx 1070?

Depends on what GTX 1070 you are using. If it's very fast card, i.e. Msi Gtx 1070 Gaming X, the one I was using in benchmark - you can get 1350+ Kh/s even with medium OC setting: 80% PL, +100 core, +400 mem. I'm sure that it can go as high as 1400+ Kh/s if I overclock it to say 100-110% PL,+150-200 core, +500-600 mem.

Medium speed cards like Gigabyte 1070 G1 Gaming can reach 1250-1300 Kh/s.

i have msi gtx 1070 gaming x 8gb but i keep it at max 60% pl and max 65% TL...
core + 100~110 and mem max 600.. and i get it 1150 per card....

but what is max core this card can go.. 150 or 200 is to high.. or not ?

proteus7

newbie

Activity: 106

Merit: 0

Running on TitanXP and its working, but performance isn't quite as good as Excavator 1.4.4. The fork_hp version gets 2.05MH/card vs 2.17MH with Excavator (which also has no devfee).
Any settings you'd recommend tweaking?

Just_a_miner

jr. member

Activity: 325

Merit: 2

Quote from: andrewpuzoff on March 03, 2018, 01:32:31 PM

Plz, help!

I have 3 VGAs
How to reduce intencity for one of them?

It needs for other calculations time by time (jminer burstcoin)

Tell me what gpu's are you using so I will be able to tell you correct intensity values.

Then use for example:

hsrminer_neoscrypt_fork -d 0,1,2 -i 7,7,15

In this example GPUS 0 and 1 will use default intensity, and GPU 2 will use intensity 15.

andrewpuzoff

newbie

Activity: 25

Merit: 0

Plz, help!

I have 3 VGAs
How to reduce intencity for one of them?

It needs for other calculations time by time (jminer burstcoin)

Just_a_miner

jr. member

Activity: 325

Merit: 2

Quote from: The Godfather on March 02, 2018, 12:18:55 PM

so how much this miner gives on gtx 1070?

Depends on what GTX 1070 you are using. If it's very fast card, i.e. Msi Gtx 1070 Gaming X, the one I was using in benchmark - you can get 1350+ Kh/s even with medium OC setting: 80% PL, +100 core, +400 mem. I'm sure that it can go as high as 1400+ Kh/s if I overclock it to say 100-110% PL,+150-200 core, +500-600 mem.

Medium speed cards like Gigabyte 1070 G1 Gaming can reach 1250-1300 Kh/s.

The Godfather

newbie

Activity: 41

Merit: 0

so how much this miner gives on gtx 1070?

Just_a_miner

jr. member

Activity: 325

Merit: 2

Has anyone tested new version with Titan XP , V , X or GTX 950, 960 gpus?

giveen1

newbie

Activity: 70

Merit: 0

Quote from: Just_a_miner on March 01, 2018, 09:27:48 AM

Quote from: giveen1 on March 01, 2018, 08:43:37 AM

Quote from: Just_a_miner on January 16, 2018, 06:02:27 AM

~ Added 1 minute per hour devfee.

Enjoy!

I really dont mind paying dev fee's. I'm just amused that this was one of the things you raged about with the original one from plagin.

I do understand that you are actually improving it with your fork. 1.6% dev isn't bad.

This is not correct, first post was like that:

Quote from: Just_a_miner on January 16, 2018, 06:02:27 AM

Are you mad at Hsrminer_Neoscrypt because it tries to connect to dead pools for several hours, making your farms waste time and profits?
So am i, because i'm just another miner like you, and i want my rigs to work 24/7!

And here is my solution:

This is fork of Hsrminer for Neoscrypt miner.
....

Main problem that was bothering me was not devfee, but exactly lack of -r option, because of that miner was unreliable. Once I woke up in the morning and checked farm's status - all rigs with hsrminer were chilling, doing nothing because pool was dead for like 4 or 6 hours. That's what make me mad and motivated to solve this problem.

My bad, either way, I dont mind paying once a version comes out that I want to upgrade to that improves performance on my 1060's. Right now I'm on equihash.

Just_a_miner

jr. member

Activity: 325

Merit: 2

Quote from: Rocstar on February 28, 2018, 08:13:32 AM

Hey Just_a_miner, wondering if you know what's causing my HSR miner to crash. It happened on the original one and the same thing happens on your forked version. I'm running two mining rigs and one runs sweet, but the other always crashes after a few mintes with this error

'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.

The rig is running 6 Gigabyte gtx 1080 ti Aorus Waterforce video cards. I'm not doing any overclocking and have turned power down to 80%

It makes mining neoscrypt pointless. I'd really appreciate it if you could help.

I need some more info, you can PM me screenshot of error. Or at least describe how it happens - are there any accepted shares before error?

Just_a_miner

jr. member

Activity: 325

Merit: 2

Quote from: proteus7 on January 24, 2018, 03:05:20 AM

One more major issue. It won't run at all with Titan XP cards. My 1080ti rig works fine, but TitanXP just ends the program. The original HSRminer had a similar issue. No idea why, TitanXP=fully enabled 1080TI (with 12gb vs 11 and no crippled SM).

Try new version, Titan XP should work now.

Just_a_miner

jr. member

Activity: 325

Merit: 2

Quote from: jugger1028 on February 25, 2018, 01:57:46 PM

I know a couple of people that are waiting for the Titan update to try it on their cards.

Titan XP, Titan V, Titan X (Pascal) is now supported (later two would probably require some additional tweaking as it was done for 970+ GPUs).

Just_a_miner

jr. member

Activity: 325

Merit: 2

Quote from: giveen1 on March 01, 2018, 08:43:37 AM

Quote from: Just_a_miner on January 16, 2018, 06:02:27 AM

~ Added 1 minute per hour devfee.

Enjoy!

I really dont mind paying dev fee's. I'm just amused that this was one of the things you raged about with the original one from plagin.

I do understand that you are actually improving it with your fork. 1.6% dev isn't bad.

This is not correct, first post was like that:

Quote from: Just_a_miner on January 16, 2018, 06:02:27 AM

Are you mad at Hsrminer_Neoscrypt because it tries to connect to dead pools for several hours, making your farms waste time and profits?
So am i, because i'm just another miner like you, and i want my rigs to work 24/7!

And here is my solution:

This is fork of Hsrminer for Neoscrypt miner.
....

Main problem that was bothering me was not devfee, but exactly lack of -r option, because of that miner was unreliable. Once I woke up in the morning and checked farm's status - all rigs with hsrminer were chilling, doing nothing because pool was dead for like 4 or 6 hours. That's what make me mad and motivated to solve this problem.

Just_a_miner

jr. member

Activity: 325

Merit: 2

Quote from: dragonmike on March 01, 2018, 08:32:02 AM

Quote from: Just_a_miner on March 01, 2018, 07:44:27 AM

Quote from: dragonmike on February 28, 2018, 12:39:54 PM

Thanks for the colour. Have you got a bit more detail on the intensity levels that can be set (and their impact/relation to GPU mem)? Every miner use different intensity parameters...

EDIT: also, I tried your failover script with another miner but then realised you were using parameters only supported by your fork of hsrminer (-r, -R). Too bad, I'd have loved to be able to use your script with DSTM's equihash miner, or any random ccminer out there... Sad

What gpu type are you trying to tweak?

As for script, you can specify any parameter you want instead of -r, just edit the .au3, for dstm it would be like:

Code:

$cmdlineArray[0]="--server SERVER --port PORT --user ADDRESS.WORKER --time --noreconnect"

I'm trying to extract the most out of a handful of GTX 1080's!

Hmm, ok, thx for that, I'll give it a go. What is the difference between -r and -R by the way (as you got both in your line)?

-r N is a number of reconnection attempts in case of connection failure. -R N is pause in seconds before trying another connection attempt. Default value is 10 seconds, that is high value, so you can tweak it with -R

giveen1

newbie

Activity: 70

Merit: 0

Quote from: Just_a_miner on January 16, 2018, 06:02:27 AM

~ Added 1 minute per hour devfee.

Enjoy!

I really dont mind paying dev fee's. I'm just amused that this was one of the things you raged about with the original one from plagin.

I do understand that you are actually improving it with your fork. 1.6% dev isn't bad.

dragonmike

hero member

Activity: 1274

Merit: 556

Quote from: Just_a_miner on March 01, 2018, 07:44:27 AM

Quote from: dragonmike on February 28, 2018, 12:39:54 PM

Thanks for the colour. Have you got a bit more detail on the intensity levels that can be set (and their impact/relation to GPU mem)? Every miner use different intensity parameters...

EDIT: also, I tried your failover script with another miner but then realised you were using parameters only supported by your fork of hsrminer (-r, -R). Too bad, I'd have loved to be able to use your script with DSTM's equihash miner, or any random ccminer out there... Sad

What gpu type are you trying to tweak?

As for script, you can specify any parameter you want instead of -r, just edit the .au3, for dstm it would be like:

Code:

$cmdlineArray[0]="--server SERVER --port PORT --user ADDRESS.WORKER --time --noreconnect"

I'm trying to extract the most out of a handful of GTX 1080's!

Hmm, ok, thx for that, I'll give it a go. What is the difference between -r and -R by the way (as you got both in your line)?

Just_a_miner

jr. member

Activity: 325

Merit: 2

Quote from: Rocstar on February 28, 2018, 08:13:32 AM

Hey Just_a_miner, wondering if you know what's causing my HSR miner to crash. It happened on the original one and the same thing happens on your forked version. I'm running two mining rigs and one runs sweet, but the other always crashes after a few mintes with this error

'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.
'Cuda error in func 'neoscrypt_cpu_hash_1080' at line 1509 : the launch timed out and was termindated.

The rig is running 6 Gigabyte gtx 1080 ti Aorus Waterforce video cards. I'm not doing any overclocking and have turned power down to 80%

It makes mining neoscrypt pointless. I'd really appreciate it if you could help.

Hi, hard to say what's the problem for now, I will take a look.

Quote from: dragonmike on February 28, 2018, 12:39:54 PM

Thanks for the colour. Have you got a bit more detail on the intensity levels that can be set (and their impact/relation to GPU mem)? Every miner use different intensity parameters...

EDIT: also, I tried your failover script with another miner but then realised you were using parameters only supported by your fork of hsrminer (-r, -R). Too bad, I'd have loved to be able to use your script with DSTM's equihash miner, or any random ccminer out there... Sad

What gpu type are you trying to tweak?

As for script, you can specify any parameter you want instead of -r, just edit the .au3, for dstm it would be like:

Code:

$cmdlineArray[0]="--server SERVER --port PORT --user ADDRESS.WORKER --time --noreconnect"

Just_a_miner

jr. member

Activity: 325

Merit: 2

New version!

See 1st msg of the topic - added support for Titan XP, Titan V, Titan X (Pascal), GTX 950, GTX 960. Fork now contains 1 minute per hour devfee, which is still lower than 70 seconds per hour of original hsrminer.

dragonmike

hero member

Activity: 1274

Merit: 556

Quote from: Just_a_miner on February 27, 2018, 11:07:29 AM

Quote from: dragonmike on February 26, 2018, 03:19:34 PM

I have another problem now though...

After updating the rig to the fall creator's update - and new nVidia drivers 391.01 I lost 25% hashrate (from 1350 to 1040 kH/s). I have been running the high priority miner, using parameters -i 5 -c 4. I also now seem to get a lot of "Share rejected, invalid job ID" messages. No idea if related or what's going on. Any ideas?

By the way, when you specify any intensity below or equal 7 - miner will use default intensity anyway, so there is no point to use -i 5. Also if you are running high priority miner, it has -c 4 by default, so you also don't need to use this option.

Thanks for the colour. Have you got a bit more detail on the intensity levels that can be set (and their impact/relation to GPU mem)? Every miner use different intensity parameters...

EDIT: also, I tried your failover script with another miner but then realised you were using parameters only supported by your fork of hsrminer (-r, -R). Too bad, I'd have loved to be able to use your script with DSTM's equihash miner, or any random ccminer out there... Sad