[Dev] NeoScrypt GPU Miner - Public Beta Test
-
So, some new observations… My initial results with 3.7.8 were based on using the exact same settings I had used with the 3.7.7 series. Try starting over with your configs (ie: bump up -w, change intensity etc). My 7950 rig got even more performance with -w 64 and a higher intensity, which it couldn’t do with the 13.x bin files… I’ll keep playing.
Want my settings for different cards?
-
Absolutely… :) I’m getting pretty decent performance bumps from my 7950’s by tweaking the settings, but my 290’s aren’t doing much better than they already were.
-
Just in case some of you haven’t seen them before, my screenshots are NSFW.
My mixed card rig, Freya, with card types and settings shown (you won’t get the same hash, but the settings should work well): https://ottrbutt.com/miner/neoscryptwolf-11022014-2.png
-
Just in case some of you haven’t seen them before, my screenshots are NSFW.
My mixed card rig, Freya, with card types and settings shown (you won’t get the same hash, but the settings should work well): https://ottrbutt.com/miner/neoscryptwolf-11022014-2.png
Looks pretty uncluttered, except for those “want” icons… ;)
-
https://www.dropbox.com/s/fc6ufamv44140zl/NeoScrypt-3.7.8.zip?dl=0
Seeing a HUGE performance bump for the R9 290 - 100kh/s - 135-140Kh/s. Using native 14.9 drivers, no messing with 13.x bin files.
Thanks Wolf0 & Vehre… This is awesome.
Tested this with Nvidia 560m I’m see no improvement, actually I’m seeing a 1.02kh/s loss using 3.7.8
used same command line as I was with 3.7.7c, still testing will try new settings next.
–neoscrypt --no-submit-stale -s 1 --expiry 1 --queue 0 -I 10 -w 32
-
Tested this with Nvidia 560m I’m see no improvement, actually I’m seeing a 1.02kh/s loss using 3.7.8
It works - as for the loss, it’s not exactly intended for Nvidia; my main target is AMD Graphics Core Next - that is, every AMD card 7xxx series and up.
-
https://www.dropbox.com/s/fc6ufamv44140zl/NeoScrypt-3.7.8.zip?dl=0
Seeing a HUGE performance bump for the R9 290 - 100kh/s - 135-140Kh/s. Using native 14.9 drivers, no messing with 13.x bin files.
Thanks Wolf0 & Vehre… This is awesome.
On those 290’s, kick the core clock up to 1130 and the memory clock up to 1495, you will see a substantial boost in speed, and almost no change in temps.
I haven’t found a way to get my 290x (XFX) to accept overclocking settings from afterburner yet. But it without o/c settings, the 290x and the 2 290’s using those settings are running 150 kh each. 78c, 80, and 84c (the 84c is a on triple fan GPU that one of the fans fell off of at some point in time)
More tweaking later, gotta go mow the lawn.
Oh, and thanks Wolf0 for digging in and offering the improvements!!
-
It works - as for the loss, it’s not exactly intended for Nvidia; my main target is AMD Graphics Core Next - that is, every AMD card 7xxx series and up.
Yea late night, just woke a short while ago and setting in front of my laptop and haven’t made it to the shop yet to test on my R9 270’s or 6970’s.
I’m sure I will see some improvement with those once tested. Thanks for working with this project.
-
Haven’t tried playing with the clock speeds yet on my 290’s - however… I was able to get them up to 160kh/s using -I 15 and -w 48… (hynix cards, haven’t tried the elpida ones yet)
Not too shabby for stock clocks :)
-
Haven’t tried playing with the clock speeds yet on my 290’s - however… I was able to get them up to 160kh/s using -I 15 and -w 48… (hynix cards, haven’t tried the elpida ones yet)
Not too shabby for stock clocks :)
Yeah, the speed on neoscrypt is really picking up with cleaning up the code… ;D When I have some time to start playing with settings in 14.xx without having to use the 13.xx bins, I’ll start tinkering with the speeds again without overclocking and see where I can get. Probably tomorrow after work, as with the time change it’ll be dark when I’m heading home from work.
-
You can definitely tell that everyone just started using 3.7.8 - the network hash rate is up almost 40% and the diff with it.
-
SGMiner is now out! Buggy, but better than the current GPU miner which is based off shit-tier CGMiner - no Win bins for now, a guy I know did it, not me: https://github.com/sgminer-dev/sgminer – IT IS THE DEVELOP BRANCH.
You can definitely tell that everyone just started using 3.7.8 - the network hash rate is up almost 40% and the diff with it.
Haha, yeah. Release a faster miner and diff rises; but neoscrypt needed a working miner.
-
I’m getting more stable hashrate and better hash estimation on SG5.
-
Would be anyone so kind and compile the SG5 miner for windows and upload it?
-
I was playing with the sgminer and neoscrypt for few days but had one bug in *.cl file I wasn’t able to solve.
Where is the source I would like to try to compile. I don’t see anything neoscrypt related in that link Wolf0 posted.
-
I was playing with the sgminer and neoscrypt for few days but had one bug in *.cl file I wasn’t able to solve.
Where is the source I would like to try to compile. I don’t see anything neoscrypt related in that link Wolf0 posted.
My God, it has capital letters! Develop branch.
-
I was playing with the sgminer and neoscrypt for few days but had one bug in *.cl file I wasn’t able to solve.
Where is the source I would like to try to compile. I don’t see anything neoscrypt related in that link Wolf0 posted.
-
Ok found it trying to compile but have some strange problems on cygwin need more time.
-
Ok found it trying to compile but have some strange problems on cygwin need more time.
Cross-compiling from Linux I find is far easier.
-
Cross-compiling from Linux I find is far easier.
make[4]: *** No rule to make target ‘jansson_config.h’, needed by ‘all-am’. Stop.
make[4]: Leaving directory ‘/home/miner/s/submodules/jansson’
Makefile:365: recipe for target ‘all’ failed
make[3]: *** [all] Error 2
make[3]: Leaving directory ‘/home/miner/s/submodules/jansson’
Makefile:501: recipe for target ‘all-recursive’ failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory ‘/home/miner/s/submodules’
Makefile:1353: recipe for target ‘all-recursive’ failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory ‘/home/miner/s’
Makefile:613: recipe for target ‘all’ failed
make: *** [all] Error 2This is what I get in cygwin, I think that submodules is the problem.
No matter what compiling option I try it is the same.
