CCminer(SP-MOD) Modded GPU kernels.

[chrysophylax]

sp - is pluck part of this fork? ...

if not - will it be? ...

#crysx

[1714702954]

1714702954

[1714702954]

1714702954

[1714702954]

1714702954

[1714702954]

1714702954

[1714702954]

1714702954

[bathrobehero]

sp - is pluck part of this fork? ...

if not - will it be? ...

#crysx

Not yet but I hope soon. For the time being sgminer is much faster than ccminer for nvidia cards which pretty much screams for optimizations.

[sp_]

KlausT has added support in his fork:

https://github.com/KlausT/ccminer

[bathrobehero]

KlausT has added support in his fork:

https://github.com/KlausT/ccminer

There's no pluck there. DJM34 made a fork which runs at around 2.3kh/s per 750 Ti while sgminer does ~3.7kh/s.

[sp_]

yes there is:

https://github.com/KlausT/ccminer/commit/fa44f730b875489e7f1c5f7e72179dc3c960e86f

But I think the code is made by DJM34

[chrysophylax]

KlausT has added support in his fork:

https://github.com/KlausT/ccminer

There's no pluck there. DJM34 made a fork which runs at around 2.3kh/s per 750 Ti while sgminer does ~3.7kh/s.

kool ...

will get it all sorted tomorrow ...

i think the last time i tried to compile i was gettign errors - and djm34 pointed out that i needed to use the latest cuda 6.5 ...

if thats the case for the sgminer / ccminer compiles - i will have a bit of work to do to build another linux machine thats more up to date than the fedora 19 x64 that i have ...

:|

#crysx

[bathrobehero]

yes there is:

https://github.com/KlausT/ccminer/commit/fa44f730b875489e7f1c5f7e72179dc3c960e86f

But I think the code is made by DJM34

Oh right, branches.

[djm34]

KlausT has added support in his fork:

https://github.com/KlausT/ccminer

There's no pluck there. DJM34 made a fork which runs at around 2.3kh/s per 750 Ti while sgminer does ~3.7kh/s.

kool ...

will get it all sorted tomorrow ...

i think the last time i tried to compile i was gettign errors - and djm34 pointed out that i needed to use the latest cuda 6.5 ...

if thats the case for the sgminer / ccminer compiles - i will have a bit of work to do to build another linux machine thats more up to date than the fedora 19 x64 that i have ...

:|

#crysx

you just need to update cuda...

[djm34]

sp - is pluck part of this fork? ...

if not - will it be? ...

#crysx

Not yet but I hope soon. For the time being sgminer is much faster than ccminer for nvidia cards which pretty much screams for optimizations.

That's not that obvious... the program was optimized for memory access, then transposed to opencl and it seems that opencl does a better job with memory access than cuda. (I found a small difference in the code between the two and now the cuda version runs at 2.8kh/s for the 750ti and 9.2kh/s for the 980, but this is still below the perf of opencl).

To be honest I would be curious to look at the ptx generated by opencl (if there are a command to obtain it)...

Actually the main difference between the two, is that the cards on nvidia runs at 40% tdp while on sgminer it runs at 100%tdp...

ps: I think it would be interesting (but lengthy) to transpose the cuda neoscrypt to opencl and check how it does on nvidia 

[djm34]

nobody has been looking into that vanilla coin ? 

because it is nothing to code: you just need to xor the first 256bit of the whirlpool hash to the last 256bit 
I can't believed it stayed cpu only for 2 months  (it takes mostly 2 min, and 10 if you create a new algo in ccminer framework)

[PVmining]

I can't believed it stayed cpu only for 2 months...

*lol* ...but to late... amd is already there.

edit: and whirlpool seems not that slow on amd - 50mhash per r9 270

[tbearhere]

What multiplier do we need for Qubit?  
Im only getting half my hash report at pool...750ti.  Thx

[sp_]

Use release 39 and without a multiplier. should work. mine at yaamp.com (Hamsterpool is broken)

[chrysophylax]

I can't believed it stayed cpu only for 2 months...

*lol* ...but to late... amd is already there.

edit: and whirlpool seems not that slow on amd - 50mhash per r9 270

100MH/s+ on 270X.

wolf - we can never know whether you are quoting YOUR miner / optimizations - or the standard that is available to the public ...

so this figure you have quoted mate - yours or public? ...

#crysx

[chrysophylax]

KlausT has added support in his fork:

https://github.com/KlausT/ccminer

There's no pluck there. DJM34 made a fork which runs at around 2.3kh/s per 750 Ti while sgminer does ~3.7kh/s.

kool ...

will get it all sorted tomorrow ...

i think the last time i tried to compile i was gettign errors - and djm34 pointed out that i needed to use the latest cuda 6.5 ...

if thats the case for the sgminer / ccminer compiles - i will have a bit of work to do to build another linux machine thats more up to date than the fedora 19 x64 that i have ...

:|

#crysx

you just need to update cuda...

tanx mate ...

the cuda repo doesnt allow that update or upgrade ...

doing it manually means a crapload of work on our part for the farm - as the 'standardization' of the farm is incomplete ...

different motherboards - cpus and the like ...

im looking at an easier way of upgrading the whole farm to the latest cuda without a 'one by one' approach ...

ill build a fedora 20 x64 test machine - which will allow all this to happen ( and also finally allow testing of your neoscrypt miner ) which will make it easier to roll out when the hardware changes happen too ...

tanx again ...

#crysx

[chrysophylax]

I can't believed it stayed cpu only for 2 months...

*lol* ...but to late... amd is already there.

edit: and whirlpool seems not that slow on amd - 50mhash per r9 270

100MH/s+ on 270X.

wolf - we can never know whether you are quoting YOUR miner / optimizations - or the standard that is available to the public ...

so this figure you have quoted mate - yours or public? ...

#crysx

Mine - he pointed out it wasn't slow on AMD; he's right.

damn ...

and how to get hold of your one? with the appropriate settings? ...



#crysx

[chrysophylax]

I can't believed it stayed cpu only for 2 months...

*lol* ...but to late... amd is already there.

edit: and whirlpool seems not that slow on amd - 50mhash per r9 270

100MH/s+ on 270X.

wolf - we can never know whether you are quoting YOUR miner / optimizations - or the standard that is available to the public ...

so this figure you have quoted mate - yours or public? ...

#crysx

Mine - he pointed out it wasn't slow on AMD; he's right.

damn ...

and how to get hold of your one? with the appropriate settings? ...



#crysx

You know the answer to that. But, anyway, I'm working on something more epic.

The CUDA and OpenCL code for Whirlpool consists of lookups into huge tables - which sucks for the GPU; that's CPU code. Even with my current code, I've noticed beyond a certain point, it doesn't matter how high I clock, because it's stalling on memory accesses. Those tables have so got to go away.

I have gotten the reference implementation down in C - surprisingly hard, seeing as it appears there's no code anywhere for it. This consists of mostly the block cipher W that was created with Whirlpool, which is based on AES - and I know AES backwards and forwards. Small issue - it's got a 2048 byte table for the multiplication, then a 256 byte Sbox.

I took the 2048 byte table used for the multiplies and reduced it to one 8-byte table by doing them manually - then I got rid of that by inlining them as constants. The S-box I split into its parts - three S-boxes containing 16 entries of 4 bits each, and bitsliced them. Does valid hashes so far, but I have a bit further to go before it's really GPU-ready.

wow - so you have been a VERY busy lil wolfie then ... damn ...

so when will you expected final implementation come? ...

btw - pm for the 'you know the answer to that' situation with your idea of how that can be done ...

just trying to make the farm work THAT MUCH better - and that requires optimizations ... sooo - pm me please with what needs to be done on my end to get it organized ...

btw - the completion of the exchange from amd to nvidia is almost complete with the farm - so i can still run / test the optimizations with the gigabyte 280x oc cards left ( 16 of them currently ) ... once those are gone - the farm will be nothing but gigabyte 750ti oc lp cards ...

hence the reason for my interest in what / when / where / how / and how much ...

#crysx

[sp_]

Looks like the cuda implementation of wirlpool can use 8 times less memory access by a small rewrite.


If Wirlpoolx is just wirlpool with an extra xor pass I think alot of work is needed to get close to the Wolf0 speed.


the 750ti only does 4,4 MHASH on wirlpool. (this overview is a bit old, the latest miner is faster)

[chrysophylax]

Looks like the cuda implementation of wirlpool can use 8 times less memory access by a small rewrite.


If Wirlpoolx is just wirlpool with an extra xor pass I think alot of work is needed to get close to the Wolf0 speed.


the 750ti only does 4,4 MHASH on wirlpool.

would it be worth it though sp? ...

#crysx

[sp_]

would it be worth it though sp? ...
#crysx

Yes, because the same algo is used in x15 (the last of the hashing function) rewriting it will improve the x15 speed alot..