[Dev] NeoScrypt GPU Miner - Public Beta Test
-
That’s exactly what I did:
git clone --recursive -b develop git(at)github.com:sgminer-dev/sgminer.git
configure
make all / make install
-
That’s exactly what I did:
git clone --recursive -b develop git(at)github.com:sgminer-dev/sgminer.git
configure
make all / make install
Odd - I have none of the issues you described.
-
can you try to mine on pool http://p2pool.neoscrypt.de:19327 ?
User= your wallet address or any other name
Pass= any
If you start the miner in text mode with -D and -P you will see, that the miner switches to long-poll, but does not use stratum.
If you force stratum with stratum+tcp://p2pool.neoscrypt.de:19327 and -fix-protocol you’ll see (or at least I see) a message ’ no pool to get work from’
The only difference I see for the rest of the problems is, that I have a NVidia 750ti, no AMD based card.
-
I’m using SGMiner 5 on yaamp.com right this minute. I’ll check the debug output, though.
Nope - I see gen_stratum_work() and all other kinds of stratum stuff.
-
and how about old cards 5800 6800 6900 series?
-
and how about old cards 5800 6800 6900 series?
It should run. Not gonna be great on them - the kernel code is pretty bad copy+pasted CPU code, except for what I edited, and 6xxx have hardware vectors, so they REALLY could use OpenCL-specific vector types in the kernel. Even better if you vectorize the algorithms; I haven’t thought much about Blake2S, but vectorizing salsa and chacha so that the card can execute 4 integer operations at once would be child’s play.
-
It should run. Not gonna be great on them - the kernel code is pretty bad copy+pasted CPU code, except for what I edited, and 6xxx have hardware vectors, so they REALLY could use OpenCL-specific vector types in the kernel. Even better if you vectorize the algorithms; I haven’t thought much about Blake2S, but vectorizing salsa and chacha so that the card can execute 4 integer operations at once would be child’s play.
What would it take to get you to vectorize the kernel for 6000 series cards? Pls Wolf. Pls. :)
-
What would it take to get you to vectorize the kernel for 6000 series cards? Pls Wolf. Pls. :)
I already gave you guys something; besides, I don’t have a pre-GCN card to test on.
-
It’s ok Wolf, you have already done so much.
insanid, the official team will look into that for you I hope.
Let’s see what we can do.
-
Wolf0, and how to get 270 kh/s on 280x as you (with SG v5 on win 7/8)?
-
Wolf0, and how to get 270 kh/s on 280x as you (with SG v5 on win 7/8)?
Rewrite pretty much all of the kernel; also, make sure the 280X has Hynix memory - Elpida seems to do less. Then again, I only have 2 280X cards, so it could be one just sucks, too - but I’d guess it’s the memory.
-
I already gave you guys something; besides, I don’t have a pre-GCN card to test on.
Thank you Wolf. We appreciate your work.
-
Rewrite pretty much all of the kernel
o_O
Wolf0, you said this:
Oddly, even on my own in-dev kernel, my 290X at 1125/1600 (memory type unknown) does 250kh/s, while my Hynix 280X does 255kh/s - 265kh/s at 1150/1500… weird.
And how this get on win7 with SG5?
255 kh/s )) I wanna it )
-
We all want Wolf’s personal kernels, but he’s said a few times that he won’t be giving them to us. He’s already done enough. Let the Wolf be free.
-
We all want Wolf’s personal kernels, but he’s said a few times that he won’t be giving them to us. He’s already done enough. Let the Wolf be free.
This is getting weird. I’m used to getting hated on, not used to being defended. :P
Anyway, maybe I’ll start a thread with those hashrates, as well as interesting info about Neoscrypt on a technical level - maybe some basic descriptions of what I did to it, as well, and things I’d like to do.
-
This is getting weird. I’m used to getting hated on, not used to being defended. :P
Anyway, maybe I’ll start a thread with those hashrates, as well as interesting info about Neoscrypt on a technical level - maybe some basic descriptions of what I did to it, as well, and things I’d like to do.
Yes, this is not bitcointalk :)
I wonder what the temperatures are on your cards.
-
Yes, this is not bitcointalk :)
I wonder what the temperatures are on your cards.
I’m quite surprised. Not in this forum not being Bitcointalk, but in people’s general attitude. I was becoming a little jaded, having most of my interactions with others in crypto on Bitcointalk - but maybe it’s limited to there. I’ve actually had Freya up and stable for 6h, so I’ll post a screenshot in a minute with all the different cards.
-
Okay, here you go (NSFW): https://ottrbutt.com/miner/neoscryptwolf-11042014.png
As you can see, every card is around mid-70C or below, except that 270X with the dead fan. What you don’t see is that all of them have a decent sized voltage bump, except that 270X, which is slightly undervolted to compensate for its lack of cooling. So, even at this hashrate, the cards are running quite cool - too cool, as my room is rather warm (probably from all three desktops with high end GPUs…) - so I need to trade off some of the memory usage for extra computations. Compute power is likely still plentiful, unused because of memory access times.
-
Okay, here you go (NSFW): https://ottrbutt.com/miner/neoscryptwolf-11042014.png
As you can see, every card is around mid-70C or below, except that 270X with the dead fan. What you don’t see is that all of them have a decent sized voltage bump, except that 270X, which is slightly undervolted to compensate for its lack of cooling. So, even at this hashrate, the cards are running quite cool - too cool, as my room is rather warm (probably from all three desktops with high end GPUs…) - so I need to trade off some of the memory usage for extra computations. Compute power is likely still plentiful, unused because of memory access times.
This is very impressive. Thank you for the settings you are using at least. I know I am going to try some of those settings on my GPUs.
LOL @ your NSFW screenshots. The legendary Wolf0 = no fucks given :)
Edit:
Sapphire 290x Vapor-x (Hynix) gets poor hashing performance with w64 I14 g2 tc32768. w48 I15 g2 tc32768 is the sweet spot for this card using the sgminer 5 you compiled for us.
-
This is very impressive. Thank you for the settings you are using at least. I know I am going to try some of those settings on my GPUs.
LOL @ your NSFW screenshots. The legendary Wolf0 = no fucks given :)
Pretty much; also, a Hynix 280X does quite a bit better than Elpida - I believe I’m getting 290+ kh/s from it. As I decreased memory fetching, useless code, and other stuff that can cause the GPU to stall, I found running LESS threads per GPU began getting far better hashrates. With the stock miner, running more threads may help, because the more threads you’re running, the more the GPU can hide that it’s waiting on a memory access. The idea is this: if a compute unit has the resources, and is stalling on a memory access, the card can schedule another wavefront to run on the CU - this means you’re hashing even when waiting for memory.
EDIT:
I should also note that --gpu-threads is a REALLY stupid name, your GPU is running at least tens of thousands of threads, --gpu-threads means spawn x amount of threads on the CPU, each giving work to the GPU.
