CCminer(SP-MOD) Modded GPU kernels.

[sp_]

joblo, does your quark optimisation work at the end? not sure I understand your conversation with sp_ fully: where does the +30% come from?

My private quark is +30% up from release 74. The buyable private is +5%

If you didn't work on SIMD, I'm suprised and disappointed.

If I did I wouldn't opensource it would I. What is the point? Why don't you opensource yours..

Because I didn't do it yet. And I don't want you to open source it - I just wanted confirmation that you worked on it.

Last opensource checkin in 9 december.
So Yes I have worked on it.
https://github.com/sp-hash/ccminer/commits/windows/x11/cuda_x11_simd512.cu

No, no, I wanted to know if some of your private optimizations that AREN'T for sale include optimizations to SIMD.

Why don't you disassemble it and check.

[sp_]

I can opensource my 5% faster miner, but then all the donators will be angry wouldn't they. Works on linux as well.

[sp_]

I said +30% in the quark algo. Quark doesn't have the SIMD512 and you should know it.

[Genoil]

Perhaps compile the ether miner for 32 bit's will help? Cached Pointersizes will go from 64bit to 32 (and double the tlb limit?) You need to remove the cpu verfication code because it use 64bit libraries I think..

Thought of that but it's going to be troublesome. You only have a 4GB address space, with windows already sucking up ~half. Then you have to load the 1.3 GB DAG from disk, and allocate 1.3GB of GPU RAM (which, AFAIK sits in the same space, although it isn't pinned to host). This doens't fit. So then you would have to read the DAG from disk in small chunks and copy it cover to GPU RAM. And when that's all done, you will have to pass on all solutions to a special light version of ethminer, that does light verification, is it can't load a DAG into RAM for the same reasons. Or you simply don't verify and risk some Boo's.

Then, when that's all done, you're not even sure if it fixes the problem. You could try getting a 32-bit version of dagSimCL to work.

I believe Epsylon3/tpruvot has been trying to get a 32-bit version of ethminer to work a while back. Can't find the source anymore.

Hi Genoil,

This is a small contribution from me to your work on ethminer --- 0xc3e7bda79b60fb4f34fbe467a8c3c3084e9008bbdc9014d8ade8e8c22cd1352a

I am using your miner and making some ETH and I thought that you deserve part of it (as I did with all devs improving the miners we are using).

Keep up the good work!

Thanks! Are you by any chance mining on Windows? Or if you built on Linux, can you find me the commit hash? I have an issue with 9x0 with the latest source, and I'm trying to figure out at which point it went wrong.

[sp_]

I said +30% in the quark algo. Quark doesn't have the SIMD512 and you should know it.

No shit - I assumed if you've got a private Quark, you've also got a private X11. If not, sorry, the question is pointless in that case.

Somebody does. X11 is not profitable with the public bins.

a wellcoded x11 should do 4-5MHASH on the 750ti

[sp_]

Faster but not profitable. I didn`t reach 5mhash yet

[sp_]

Faster but not profitable. I didn`t reach 5mhash yet

Well, did you modify SIMD in it? And if you feel like sharing, how much was gained from SIMD alone in X11 speed percentage?

Why don't you stick with AMD. Disassemble the kochur bins and check for yourself.

[crsminer]

Perhaps compile the ether miner for 32 bit's will help? Cached Pointersizes will go from 64bit to 32 (and double the tlb limit?) You need to remove the cpu verfication code because it use 64bit libraries I think..

Thought of that but it's going to be troublesome. You only have a 4GB address space, with windows already sucking up ~half. Then you have to load the 1.3 GB DAG from disk, and allocate 1.3GB of GPU RAM (which, AFAIK sits in the same space, although it isn't pinned to host). This doens't fit. So then you would have to read the DAG from disk in small chunks and copy it cover to GPU RAM. And when that's all done, you will have to pass on all solutions to a special light version of ethminer, that does light verification, is it can't load a DAG into RAM for the same reasons. Or you simply don't verify and risk some Boo's.

Then, when that's all done, you're not even sure if it fixes the problem. You could try getting a 32-bit version of dagSimCL to work.

I believe Epsylon3/tpruvot has been trying to get a 32-bit version of ethminer to work a while back. Can't find the source anymore.

Hi Genoil,

This is a small contribution from me to your work on ethminer --- 0xc3e7bda79b60fb4f34fbe467a8c3c3084e9008bbdc9014d8ade8e8c22cd1352a

I am using your miner and making some ETH and I thought that you deserve part of it (as I did with all devs improving the miners we are using).

Keep up the good work!

Thanks! Are you by any chance mining on Windows? Or if you built on Linux, can you find me the commit hash? I have an issue with 9x0 with the latest source, and I'm trying to figure out at which point it went wrong.

Sent you a PM.

[sp_]

Faster but not profitable. I didn`t reach 5mhash yet

Well, did you modify SIMD in it? And if you feel like sharing, how much was gained from SIMD alone in X11 speed percentage?

Why don't you stick with AMD. Disassemble the kochur bins and check for yourself.

I am, thanks. What I'm interested in is how much there is to be gained from SIMD. While the architecture is different, many things are similar - if there's an unexpectedly massive improvement from SIMD on Nvidia GPUs, it is quite likely there is on AMD.
Also, why so defensive? I have no intention of enroaching on your turf, here - I could do more CUDA if I wanted, but for now it does not interest me. You don't need to see me as a threat.

You are no competition to me...

[sp_]

Then why are you afraid?

I am not afraid, but I don't feel the need to help you. Perhaps if you opensource some of your work we can talk again..

[djm34]

I can opensource my 5% faster miner, but then all the donators will be angry wouldn't they. Works on linux as well.

If you don't want to answer the question, don't answer the question - but don't dodge it.

getting some popcorn  

ps: for once I am not involved in the trolling  

[djm34]

Then why are you afraid?

I am not afraid, but I don't feel the need to help you. Perhaps if you opensource some of your work we can talk again..

See? That's all you had to say - like I said, if you don't want to answer, I'm perfectly okay with that. Just be honest about it.

I can opensource my 5% faster miner, but then all the donators will be angry wouldn't they. Works on linux as well.

If you don't want to answer the question, don't answer the question - but don't dodge it.

getting some popcorn 

ps: for once I am not involved in the trolling 

Haha, djm34, I'm not trolling - I asked a question; he didn't wish to answer. It's all good.

never said you were, I was saying that usually I am the one getting into some argument with sp 

[MaxDZ8]

For example, I semi-recently not only did the ONLY open-source implementation of a CryptoNight AMD miner, but I didn't base it on existing code infected with the GPL. This means there's now a base that's not only open, but MIT/BSD licensed to work off of for others.

Kudos to you!

[pallas]

For example, I semi-recently not only did the ONLY open-source implementation of a CryptoNight AMD miner, but I didn't base it on existing code infected with the GPL. This means there's now a base that's not only open, but MIT/BSD licensed to work off of for others.

Kudos to you!

Thank you. Please, if you wish to, use that base publicly or privately for your own miner work - or take bits and pieces from it. A nice guy caught an oversight that I made - I should have used a pthread condition variable and didn't - so now the miner uses pretty much 0% CPU. I'm rather happy and proud that the rest of it was so nice and light.

I'll have a look as well, thanks for sharing and shame on me for not noticing it earlier

Found this runtime issue:

[15:54:44] Error -6 when calling clCreateCommandQueueWithProperties.
[15:54:44] Error -36 when calling clEnqueueWriteBuffer to fill input buffer.

EDIT: looks like it doesn't like the Fiji card but hashes fine on the Hawaii.

[pallas]

For example, I semi-recently not only did the ONLY open-source implementation of a CryptoNight AMD miner, but I didn't base it on existing code infected with the GPL. This means there's now a base that's not only open, but MIT/BSD licensed to work off of for others.

Kudos to you!

Thank you. Please, if you wish to, use that base publicly or privately for your own miner work - or take bits and pieces from it. A nice guy caught an oversight that I made - I should have used a pthread condition variable and didn't - so now the miner uses pretty much 0% CPU. I'm rather happy and proud that the rest of it was so nice and light.

I'll have a look as well, thanks for sharing and shame on me for not noticing it earlier

Found this runtime issue:

[15:54:44] Error -6 when calling clCreateCommandQueueWithProperties.
[15:54:44] Error -36 when calling clEnqueueWriteBuffer to fill input buffer.

EDIT: looks like it doesn't like the Fiji card but hashes fine on the Hawaii.

Works on mine. What's your settings file look like?

{
        "Algorithms":
        [
                {
                        "name": "CryptoNight",
                        "devices":
                        [
                                {
                                        "index": 0,
                                        "threads": 1,
                                        "rawintensity": 1336,
                                        "worksize": 16
                                },
                                {
                                        "index": 1,
                                        "threads": 1,
                                        "rawintensity": 1336,
                                        "worksize": 16
                                }
                        ],
                        "pools":
                        [
                                {
                                        "url": "XXXXXXXXXX",
                                        "user": "XXXXXXXXXXXX",
                                        "pass": "x"
                                }
                        ]
                }
        ]
}

[pallas]

Wolf0 I've found the issue. Fiji doesn't want to run with libopencl from APP SDK 3.0.
Fiji now works but it's slower than Hawaii, guess HSM is to blame.

[joblo]

joblo, does your quark optimisation work at the end? not sure I understand your conversation with sp_ fully: where does the +30% come from?

Mostly from more efficient management of the groestl ctx. Because quark can run groestl twice per round
and was running the init function twice every time the hash function was called and it was called in a scanhash loop.
That's  2* the number of hash calls for something that only needs to be done once. That was a big boost though I
don't recall exactly how much. The reduction in the number of inits also helped other algos like x11.

I also created a fast reinit function that skipped the constants.  So now a full init is done once when scanhash
is called and any subsequent reinits that are necessary are fast. That alone added another 5%.

I have another idea to factor out the full init from scanhash so the ctx will be fully initted only once, ever, before
entering the thread loop.

[joblo]

joblo, does your quark optimisation work at the end? not sure I understand your conversation with sp_ fully: where does the +30% come from?

Joblo's optimization impacts CPU validation of any found shares. This is usually insignificant, but since he's also mining with all CPU cores, it did have an impact for him. It was that his CPU mining was slowing down ccminer.

Joblo: You're invited for a beer over at #ccminer @freenode: there's friendlier dev talk there, some collaboration now and then, and certainly a lot less BS 

Thanks for the invite. I plan to join #ccminer (and github, and...) when things settle down, which they are beginning to do.
I've been so busy trying to get all the algos supported and delivering the quick optimizations that I'm only now starting to think
longer term.

I'm working on a design to modulerize algos that doesn't require any base code changes when adding a new algo.
But that's a big feature that requires a lot of thought. I have high standards and don't want to present a half-baked plan.

[joblo]

I was hoping to get a better response to my technical trolls but all I got was more bluster.
I was trying to find out if our skills were complementary. I am a complete noob when it comes
to cuda so I was hoping SP could implement some of my ideas with his knowledge of cuda.
When I provided a demonstration of my skills he respnded with sillly you that was cpu verification
code, and why don't you do better, without ever considering the technical merit or other
applications for the changes I made

He's more interested in selling what he has over and over again rather than providing anything new
that sells itself. I'm afraid SP has turned into a telemarketer.

[bensam1231]

Faster but not profitable. I didn`t reach 5mhash yet

Well, did you modify SIMD in it? And if you feel like sharing, how much was gained from SIMD alone in X11 speed percentage?

Why don't you stick with AMD. Disassemble the kochur bins and check for yourself.

I am, thanks. What I'm interested in is how much there is to be gained from SIMD. While the architecture is different, many things are similar - if there's an unexpectedly massive improvement from SIMD on Nvidia GPUs, it is quite likely there is on AMD.
Also, why so defensive? I have no intention of enroaching on your turf, here - I could do more CUDA if I wanted, but for now it does not interest me. You don't need to see me as a threat.

You are no competition to me...

Then why are you afraid?

Grills grills, there is plenty of optimizations to go around! Since wolf0 is hot stuff, he should make Eth better.

Oh, by the way, sp_ - the comment about open sourcing some of my work I think is a little unfounded. For example, I semi-recently not only did the ONLY open-source implementation of a CryptoNight AMD miner, but I didn't base it on existing code infected with the GPL. This means there's now a base that's not only open, but MIT/BSD licensed to work off of for others. And on top of this, the community around the coins using the CryptoNight PoW really needed it, because the only existing AMD miner for it before mine was Claymore's, which was closed-source with a fee, and WAS Windows-only for the longest time. I even forked my own project and made a CryptoNight-Lite miner for that PoW - Claymore refused to implement it. You can find my CryptoNight miner here: https://github.com/wolf9466/wolf-xmr-miner -- and my CryptoNight-Lite miner here: https://github.com/wolf9466/wolf-aeon-miner

Unless it's like 2x faster then Claymore, it's not worth mining with. Monero hasn't been profitable for sometime. Botnets consumed Cryptonote.


Quick check on Vanillacoin. I get about 2.9GH/s per 970, it doesn't appear to be more profitable then Ethereum right now, always nice to have options though.