[ANN][GRS][DMD][DGB] Pallas optimized groestl opencl kernels

[pallas]

Congratulations Pallas.

Do you have it on Github already?

Thanks.
No git yet. I was thinking it's not necessary for a single file, but now there are bins and maybe multiple versions so I may end up doing it.

[1714671546]

1714671546

[1714671546]

1714671546

[1714671546]

1714671546

[qwep]

Congratulations Pallas.

Do you have it on Github already?

Thanks.
No git yet. I was thinking it's not necessary for a single file, but now there are bins and maybe multiple versions so I may end up doing it.

congratulations excellent optimization, but what about the other algorithms

[pallas]

Congratulations Pallas.

Do you have it on Github already?

Thanks.
No git yet. I was thinking it's not necessary for a single file, but now there are bins and maybe multiple versions so I may end up doing it.

congratulations excellent optimization, but what about the other algorithms

I did work on other algorithms too (x11 components, m7 and others) but nothing ready for publication.
I'd need more time and lower kilowatt hour cost in order to go ahead :-)

[qwep]

Congratulations Pallas.

Do you have it on Github already?

Thanks.
No git yet. I was thinking it's not necessary for a single file, but now there are bins and maybe multiple versions so I may end up doing it.

congratulations excellent optimization, but what about the other algorithms

I did work on other algorithms too (x11 components, m7 and others) but nothing ready for publication.
I'd need more time and lower kilowatt hour cost in order to go ahead :-)

I understand that all miners are written C ++, and why not in C #, it is a bit faster than the C ++

[pallas]

Congratulations Pallas.

Do you have it on Github already?

Thanks.
No git yet. I was thinking it's not necessary for a single file, but now there are bins and maybe multiple versions so I may end up doing it.

congratulations excellent optimization, but what about the other algorithms

I did work on other algorithms too (x11 components, m7 and others) but nothing ready for publication.
I'd need more time and lower kilowatt hour cost in order to go ahead :-)

I understand that all miners are written C ++, and why not in C #, it is a bit faster than the C ++

Most miners are written in plain C but it doesn't matter that much unless you are mining with the CPU (still there is a good deal of assembly on some algorithms). GPU code is opencl or cuda instead.

[smolen]

Take a look at my groestl implementation

[pallas]

Take a look at my groestl implementation

Thanks. From a first look, I don't see anything I haven't tried yet :-)
Do you have some hashrate figures?

[smolen]

Take a look at my groestl implementation

Thanks. From a first look, I don't see anything I haven't tried yet :-)
Do you have some hashrate figures?

Sorry, no testing results, I'm away from all crypto stuff, that's rather abandoned project, collecting virtual dust on HDD...
I didn't quite grok all your tricks I only use 3 arrays of 32 integers for intermediate results, so memory usage should be almost minimal and such buffer reusing could be an independent optimization, quite sure you have tried the rest

[pallas]

I did the best I could to reduce register usage, but in the end using more 64 bits turned out to be faster. Probably private memory is not fully used...

[smolen]

in the end using more 64 bits turned out to be faster. Probably private memory is not fully used...

May be 64 bit math tricked AMD OpenCL compiler away from useless 'optimizations' I once get strange effect when inserting absolutely unrelated operations (well, it was copy protection) in the middle of big number crunching resulted in ~5% speed increase.

[utahjohn]

@pallas
Any chance of you integrating your groestl kernel into the optimised X11 and X13 kernels on my BCT thread (in my sig)

[pallas]

@pallas
Any chance of you integrating your groestl kernel into the optimised X11 and X13 kernels on my BCT thread (in my sig)

I'll have a look asap. Actually I don't have much free time now, so it may take a bit.

[pallas]

in the end using more 64 bits turned out to be faster. Probably private memory is not fully used...

May be 64 bit math tricked AMD OpenCL compiler away from useless 'optimizations' I once get strange effect when inserting absolutely unrelated operations (well, it was copy protection) in the middle of big number crunching resulted in ~5% speed increase.

Sometimes it looks random indeed! :-D
And sometimes compiling the same .cl file leads to different hashrates O_o

[istvandv]

@pallas
Any chance of you integrating your groestl kernel into the optimised X11 and X13 kernels on my BCT thread (in my sig)

I'll have a look asap. Actually I don't have much free time now, so it may take a bit.

while you are at it, how about myr-groestl? 

[pallas]

@pallas
Any chance of you integrating your groestl kernel into the optimised X11 and X13 kernels on my BCT thread (in my sig)

I'll have a look asap. Actually I don't have much free time now, so it may take a bit.

while you are at it, how about myr-groestl? 

I had a quick look some time ago: some of the tricks that work on this kernel do not make myr-groestl any faster, thus I'd need to re-tune it from scratch... :-/

[Spider07]

Hello
How do you do to have a such result ? I have only 6
My settings are wrong ?

sgminer.exe -k groestlcoin -o localhost:17772 -u XXXX -p XXXXXXXX -I 22 -w 256 -g 1 --thread-concurrency 24000 --gpu-engine 1100 --gpu-memclock 1250


Thanks

[pallas]

Hello
How do you do to have a such result ? I have only 6
My settings are wrong ?

sgminer.exe -k groestlcoin -o localhost:17772 -u XXXX -p XXXXXXXX -I 22 -w 256 -g 1 --thread-concurrency 24000 --gpu-engine 1100 --gpu-memclock 1250


Thanks

See the troubleshooting on the op.
Lower your memory clock, try the compiled binary.

[Spider07]

Oh
Tried to use the compiled binary - no more succes.....
 I paste your binary to my folder, copy the name of my  generate  .bin, delete my .bin and rename your .bin with the name of my.bin, run again my .bat
Is-it the good way to proceed ?

Also changed to --gpu-memclock 350 without any success
Thanks

[losk22]

 Replace groestlcoin.cl, diamond.cl and/or the kernel you want to use with this one (it's inside the "kernel" folder) You can read more?

[Spider07]

Replace groestlcoin.cl, diamond.cl and/or the kernel you want to use with this one (it's inside the "kernel" folder) You can read more?

Thanks for your help.

Sorry forgot to mention that I have done that.
To be sure , I deleted all files in kernel folder
I have only 1 file (groestlcoin-v1.cl renamed to groestlcoin.cl)

I can't reach 16 Mh/s.....   only 6.....