Topic: Feathercoin [FTC] - page 115. (Read 460641 times)
is secret for now...
3x 280x settings from few days ago without any kind of overclock.
Intensity ? 
3x 280x settings from few days ago without any kind of overclock.
7950's go almost as high as 280x's on your public kernal Wolf0... top work.
all 4 are built with hynix.
asus 280x with hynix does 170khs and elpidha 280x does 150khs. so the 7950 fits in rather nicely.
Can u give me ur config bat please for 280x
Thx in advance
Because i only get 115khs on r9 280x Toxic version
for 280x use 14.7 rc3 drivers as 14.9 seems to limit output of the card. -w 48 -i 13 -g 3. and fiddle with the core and memclocks to reach a comfortable stable speed. if you have hunix memory it would bring you past the 160khs mark, if its built with elpidha then between 144-150khs with my config.
How much electricity needed for neoscrypt compared to x11,x13,x15.?
My rigs are using about 13% more with neoscrypt over x11.
How much electricity needed for neoscrypt compared to x11,x13,x15.?
Since this seems to be the thread with the best Wolf0 Neoscrypt info, I figured I would share what I have been able to work out so far...
I am running 2, 6 x R9-290 mining rigs.
Mining x11, memclocks set to 967 (optimal imho), and powertune at -15 for power economics, they average around 32Mh @ 1210W each.
Mining Neoscrypt with Wolf0's Nov 2nd SGMiner5 build, I have been able to get around 1Mh (930avg) @ 1450W per miner. This unfortunately is "not" using his awesome personal neoscrypt.cl file or I am guessing I would be putting out about twice the hash with probably a bit less power usage. Since this is the unoptimized "release" cl file (yet still better than any other versions I have yet run across), with today's crypto values, it is still mining pretty close to break even power/profit wise so I needed to back the memclock setting down to 924 to save a few hundred watts for economics. The 924 setting does hold back the maximum available hashrate a small amount...
Using my own batch and conf file with fallbacks on the first miner, about the best I have been able to get looks something like this...
On the second miner, using just a batch file with Wolf0's settings that I pulled off of another thread, changing the worksize to 32, and bumping up the intensity just a touch;
It looks something like this...
This has taken me a couple of days of forum digging and configuration changes, weeding out crashes, rejects, and sick and dead cards so I hope it can help save someone else a little effort.
And I want to give a huge shout out to Wolf0 and give him props for his exceptional work. Not only on neoscrypt, but on all of the GPU algo's that he has spent his time on. While I sure wish I could get a hold of some of those personal optimized cl files he is holding back, there is no question in my mind that without his efforts and what he has already shared with us and other developers, there would already be a lot more GPU rigs headed for ebay and the scrap yard including mine. His work and that of savvy coin developers using the less ASIC/FPGA friendly algos, is helping to keep decentralized CPU and GPU mining alive. In my humble opinion, that decentralization is key to a fair crypto future.
That said, Wolf0, In appreciation of your efforts, I'd like send you a bounty of 10% of what I have mined with your neoscrypt software to date... I have been multiport mining on TMB with it, so its all in FTC and UFO... Can you list or PM me FTC/UFO addy's, or would you rather I convert em to BTC at todays market value and send to the LNc7w8HpAFJCnhbZqS3nmDwZP6h2Rrbqzn donation address?
Thanks again,
Hatch
(Updated 11/7; Bounty sent in FTC)
I am running 2, 6 x R9-290 mining rigs.
Mining x11, memclocks set to 967 (optimal imho), and powertune at -15 for power economics, they average around 32Mh @ 1210W each.
Mining Neoscrypt with Wolf0's Nov 2nd SGMiner5 build, I have been able to get around 1Mh (930avg) @ 1450W per miner. This unfortunately is "not" using his awesome personal neoscrypt.cl file or I am guessing I would be putting out about twice the hash with probably a bit less power usage. Since this is the unoptimized "release" cl file (yet still better than any other versions I have yet run across), with today's crypto values, it is still mining pretty close to break even power/profit wise so I needed to back the memclock setting down to 924 to save a few hundred watts for economics. The 924 setting does hold back the maximum available hashrate a small amount...
Using my own batch and conf file with fallbacks on the first miner, about the best I have been able to get looks something like this...
On the second miner, using just a batch file with Wolf0's settings that I pulled off of another thread, changing the worksize to 32, and bumping up the intensity just a touch;
Code:
color 0A
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
rem Intensity 15, worksize 64 for all
rem TC 16384 for 270X, 49152 for 280X & 290X, and 32768 for 7950
rem GPU threads 1 for 270X, 280X, and 7950, and 2 for 290X
sgminer.exe -k neoscrypt -o stratum+tcp://east01.us.trademybit.com:8880 -u "username" -p "password" -w 32 -I 18 --gpu-engine 924 --thread-concurrency 49152 --gpu-powertune -15 --gpu-threads 2 --no-submit-stale
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_USE_SYNC_OBJECTS 1
rem Intensity 15, worksize 64 for all
rem TC 16384 for 270X, 49152 for 280X & 290X, and 32768 for 7950
rem GPU threads 1 for 270X, 280X, and 7950, and 2 for 290X
sgminer.exe -k neoscrypt -o stratum+tcp://east01.us.trademybit.com:8880 -u "username" -p "password" -w 32 -I 18 --gpu-engine 924 --thread-concurrency 49152 --gpu-powertune -15 --gpu-threads 2 --no-submit-stale
It looks something like this...
This has taken me a couple of days of forum digging and configuration changes, weeding out crashes, rejects, and sick and dead cards so I hope it can help save someone else a little effort.
And I want to give a huge shout out to Wolf0 and give him props for his exceptional work. Not only on neoscrypt, but on all of the GPU algo's that he has spent his time on. While I sure wish I could get a hold of some of those personal optimized cl files he is holding back, there is no question in my mind that without his efforts and what he has already shared with us and other developers, there would already be a lot more GPU rigs headed for ebay and the scrap yard including mine. His work and that of savvy coin developers using the less ASIC/FPGA friendly algos, is helping to keep decentralized CPU and GPU mining alive. In my humble opinion, that decentralization is key to a fair crypto future.
That said, Wolf0, In appreciation of your efforts, I'd like send you a bounty of 10% of what I have mined with your neoscrypt software to date... I have been multiport mining on TMB with it, so its all in FTC and UFO... Can you list or PM me FTC/UFO addy's, or would you rather I convert em to BTC at todays market value and send to the LNc7w8HpAFJCnhbZqS3nmDwZP6h2Rrbqzn donation address?
Thanks again,
Hatch
(Updated 11/7; Bounty sent in FTC)
7950's go almost as high as 280x's on your public kernal Wolf0... top work.
all 4 are built with hynix.
asus 280x with hynix does 170khs and elpidha 280x does 150khs. so the 7950 fits in rather nicely.
Can u give me ur config bat please for 280x
Thx in advance
Because i only get 115khs on r9 280x Toxic version
for 280x use 14.7 rc3 drivers as 14.9 seems to limit output of the card. -w 48 -i 13 -g 3. and fiddle with the core and memclocks to reach a comfortable stable speed. if you have hunix memory it would bring you past the 160khs mark, if its built with elpidha then between 144-150khs with my config.
Thx it works
7950's go almost as high as 280x's on your public kernal Wolf0... top work.
all 4 are built with hynix.
asus 280x with hynix does 170khs and elpidha 280x does 150khs. so the 7950 fits in rather nicely.
Can u give me ur config bat please for 280x
Thx in advance
Because i only get 115khs on r9 280x Toxic version
for 280x use 14.7 rc3 drivers as 14.9 seems to limit output of the card. -w 48 -i 13 -g 3. and fiddle with the core and memclocks to reach a comfortable stable speed. if you have hunix memory it would bring you past the 160khs mark, if its built with elpidha then between 144-150khs with my config.
7950's go almost as high as 280x's on your public kernal Wolf0... top work.
all 4 are built with hynix.
asus 280x with hynix does 170khs and elpidha 280x does 150khs. so the 7950 fits in rather nicely.
Can u give me ur config bat please for 280x
Thx in advance
Because i only get 115khs on r9 280x Toxic version
7950's go almost as high as 280x's on your public kernal Wolf0... top work.
all 4 are built with hynix.
asus 280x with hynix does 170khs and elpidha 280x does 150khs. so the 7950 fits in rather nicely.
Can u give me ur config bat please for 280x
Thx in advance
7950's go almost as high as 280x's on your public kernal Wolf0... top work.
Same with my private one - 231kh/s out of Elpida 280X, 235kh/s out of Elpida 7950. Meaning, all the compute isn't being used, it's being limited by memory, and I therefore need to trade off memory usage for compute.
yea i noticed that when i was just reviewing your pic uploads, my clock/core speeds are nowhere near as high as yours thou.
Doesn't matter - those speeds I just quoted are at 1000 core.
ok my core speeds are somewhat higher then that lol....... between 1090 and 1135 between the 7950's and 280x's to achieve the speeds i have, along with my config. useing almost the same config for scrypt, go figure.
7950's go almost as high as 280x's on your public kernal Wolf0... top work.
Same with my private one - 231kh/s out of Elpida 280X, 235kh/s out of Elpida 7950. Meaning, all the compute isn't being used, it's being limited by memory, and I therefore need to trade off memory usage for compute.
yea i noticed that when i was just reviewing your pic uploads, my clock/core speeds are nowhere near as high as yours thou.
7950's go almost as high as 280x's on your public kernal Wolf0... top work.
all 4 are built with hynix.
asus 280x with hynix does 170khs and elpidha 280x does 150khs. so the 7950 fits in rather nicely.
Try reading the post, as well as the notepad in the screenshot for the confs. I've bolded the part above.
Anyway, those are kind of some sad-ass hashrates; took this screenshot earlier today - stable almost 7 hours (nsfw):
https://ottrbutt.com/miner/neoscryptwolf-11042014.png
One HELL of a lot better.
But that's not the kernel you shared, right? You've been getting all those hashrates with a custom kernel, not the one that was uploaded to your github? Anyway, those are kind of some sad-ass hashrates; took this screenshot earlier today - stable almost 7 hours (nsfw):
https://ottrbutt.com/miner/neoscryptwolf-11042014.png
One HELL of a lot better.
some of my stats:
all are running 13.35 drivers.
sapphire tri-x 290: basically the same scrypt config except intensity dropped down from 18 to 14 on the 3.7.5 cgminer version (win 7) and getting 110khs on each card.
"intensity" : "14",
"vectors" : "1",
"worksize" : "256",
"thread-concurrency" : "28456",
"gpu-dyninterval" : "7",
"gpu-threads" : "1"
msi 270: radically different config required compared to normal scrypt mining config. uses the 3.7.7b cgminer version (win 8.1) and getting 49khs on each card.
"intensity" : "14",
"vectors" : "1",
"worksize" : "32",
"thread-concurrency" : "0",
"gpu-dyninterval" : "7",
"gpu-threads" : "3"
and power draw from the wall is around 630W.
normally the 6 x 270 rig is on par with the 3 x 290 rig but with neoscrypt it pays to have the higher end unit but not by much (less than 10%)
all are running 13.35 drivers.
sapphire tri-x 290: basically the same scrypt config except intensity dropped down from 18 to 14 on the 3.7.5 cgminer version (win 7) and getting 110khs on each card.
"intensity" : "14",
"vectors" : "1",
"worksize" : "256",
"thread-concurrency" : "28456",
"gpu-dyninterval" : "7",
"gpu-threads" : "1"
msi 270: radically different config required compared to normal scrypt mining config. uses the 3.7.7b cgminer version (win 8.1) and getting 49khs on each card.
"intensity" : "14",
"vectors" : "1",
"worksize" : "32",
"thread-concurrency" : "0",
"gpu-dyninterval" : "7",
"gpu-threads" : "3"
and power draw from the wall is around 630W.
normally the 6 x 270 rig is on par with the 3 x 290 rig but with neoscrypt it pays to have the higher end unit but not by much (less than 10%)
Using SGMiner 5 on 14.9 - kernel is one I've worked on more since I released the 14.9 fix - mixed rig with a 270X, 280X, 290X, and 7950.
I particularly like how my 270X is doing 104kh/s solid. I have a screenshot showing the miner with hashrates, plus a notepad open with which GPU is which and their clocks.
(Warning, screenshot is nsfw): https://ottrbutt.com/miner/neoscryptwolf-11022014-3.png
how did manage to get above 200? can u share your confs?
some of my stats:
all are running 13.35 drivers.
sapphire tri-x 290: basically the same scrypt config except intensity dropped down from 18 to 14 on the 3.7.5 cgminer version (win 7) and getting 110khs on each card.
"intensity" : "14",
"vectors" : "1",
"worksize" : "256",
"thread-concurrency" : "28456",
"gpu-dyninterval" : "7",
"gpu-threads" : "1"
msi 270: radically different config required compared to normal scrypt mining config. uses the 3.7.7b cgminer version (win 8.1) and getting 49khs on each card.
"intensity" : "14",
"vectors" : "1",
"worksize" : "32",
"thread-concurrency" : "0",
"gpu-dyninterval" : "7",
"gpu-threads" : "3"
and power draw from the wall is around 630W.
normally the 6 x 270 rig is on par with the 3 x 290 rig but with neoscrypt it pays to have the higher end unit but not by much (less than 10%)
all are running 13.35 drivers.
sapphire tri-x 290: basically the same scrypt config except intensity dropped down from 18 to 14 on the 3.7.5 cgminer version (win 7) and getting 110khs on each card.
"intensity" : "14",
"vectors" : "1",
"worksize" : "256",
"thread-concurrency" : "28456",
"gpu-dyninterval" : "7",
"gpu-threads" : "1"
msi 270: radically different config required compared to normal scrypt mining config. uses the 3.7.7b cgminer version (win 8.1) and getting 49khs on each card.
"intensity" : "14",
"vectors" : "1",
"worksize" : "32",
"thread-concurrency" : "0",
"gpu-dyninterval" : "7",
"gpu-threads" : "3"
and power draw from the wall is around 630W.
normally the 6 x 270 rig is on par with the 3 x 290 rig but with neoscrypt it pays to have the higher end unit but not by much (less than 10%)
for 280x a config .bat please
some of my stats:
all are running 13.35 drivers.
sapphire tri-x 290: basically the same scrypt config except intensity dropped down from 18 to 14 on the 3.7.5 cgminer version (win 7) and getting 110khs on each card.
"intensity" : "14",
"vectors" : "1",
"worksize" : "256",
"thread-concurrency" : "28456",
"gpu-dyninterval" : "7",
"gpu-threads" : "1"
msi 270: radically different config required compared to normal scrypt mining config. uses the 3.7.7b cgminer version (win 8.1) and getting 49khs on each card.
"intensity" : "14",
"vectors" : "1",
"worksize" : "32",
"thread-concurrency" : "0",
"gpu-dyninterval" : "7",
"gpu-threads" : "3"
and power draw from the wall is around 630W.
normally the 6 x 270 rig is on par with the 3 x 290 rig but with neoscrypt it pays to have the higher end unit but not by much (less than 10%)
all are running 13.35 drivers.
sapphire tri-x 290: basically the same scrypt config except intensity dropped down from 18 to 14 on the 3.7.5 cgminer version (win 7) and getting 110khs on each card.
"intensity" : "14",
"vectors" : "1",
"worksize" : "256",
"thread-concurrency" : "28456",
"gpu-dyninterval" : "7",
"gpu-threads" : "1"
msi 270: radically different config required compared to normal scrypt mining config. uses the 3.7.7b cgminer version (win 8.1) and getting 49khs on each card.
"intensity" : "14",
"vectors" : "1",
"worksize" : "32",
"thread-concurrency" : "0",
"gpu-dyninterval" : "7",
"gpu-threads" : "3"
and power draw from the wall is around 630W.
normally the 6 x 270 rig is on par with the 3 x 290 rig but with neoscrypt it pays to have the higher end unit but not by much (less than 10%)
Hay, Anyone tried using a GTX770 and can share their setup?
Using cgminer 3.7.7b can only get to around 35k at best.
Using cgminer 3.7.7b can only get to around 35k at best.
Jump to: