Was going to update previous post but there were more replies to the thread than I expected.
Environment is inside closed cases ambient temps are 72F
Neoscrypt hashrates using Klaust
Getting 1434KH/s Temp 70c on stock clocks 1080TI FE
Getting 1186KH/s Temp 78c using stock clocks on my Zotac Mini 1080
HSRminer hashrates:
1080TI FE
No adjustments 26.9% increase miner side
speed is 1933.92kH/s, Temp 69c, zPool.ca 45 Min average shows 2133KH/s
Zotac Mini 1080
No adjustments 8.86% loss miner side
speed is 1016.32kH/s, Temp 80c, zpool.ca 45 Min average shows 1216Kh/s
guessing miner hash is calculating after devfee adjustment.
Now I just need to be able to fetch ccminer style stats and I'm using it for my 1080TI
I need to clarify about devfee, there are two techniques implemented in miner, which one to choose miner decides itself during start:
1)2 stratum threads with 1% of CUDA threads running on dev
2)1 stratum thread running in cycle User-Dev-User (proportionally 99/1)
In Neoscrypt case only second variant avaliable regarding to kernel specification and during pool switches there are delays (sometimes 5-10 sec, depends on Dev pool and User pool load and connection stability). As average hashrate calculation is based not only on number of hashes, but also on the timeline (including connection delays), so after each cycle User-Dev-User switch average hashrate will be shown less than it actually is.
To sum up: check speed on pool or after 10-15 min from launch on miner side.
UPDATE: for 1060 3Gb and 6Gb users specifically, please, re-download binary from GitHub, fix for 6Gb version 1060's implemented.
Until any critical bug will be found or until I'll buy 1080Ti, Neoscrypt developement will be frozen from now, I'm switching to other algos.