Topic: [ANN][GRS][DMD][DGB] Pallas optimized groestl opencl kernels - page 19. (Read 61242 times)
September 28, 2014, 04:24:09 AM
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?
September 28, 2014, 02:33:57 AM
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
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
September 28, 2014, 02:26:05 AM
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
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.
September 28, 2014, 02:08:43 AM
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
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
September 25, 2014, 02:28:17 AM
@pallas
Any chance of you integrating your groestl kernel into the optimised X11 and X13 kernels on my BCT thread (in my sig)
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... :-/
September 24, 2014, 11:58:45 PM
@pallas
Any chance of you integrating your groestl kernel into the optimised X11 and X13 kernels on my BCT thread (in my sig)
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?
September 24, 2014, 03:21:07 PM
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
September 24, 2014, 03:18:21 PM
@pallas
Any chance of you integrating your groestl kernel into the optimised X11 and X13 kernels on my BCT thread (in my sig)
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.
September 24, 2014, 01:58:55 PM
@pallas
Any chance of you integrating your groestl kernel into the optimised X11 and X13 kernels on my BCT thread (in my sig)
Any chance of you integrating your groestl kernel into the optimised X11 and X13 kernels on my BCT thread (in my sig)
September 24, 2014, 01:29:22 PM
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. September 24, 2014, 12:58:15 PM
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...
September 24, 2014, 12:13:54 PM
Thanks. From a first look, I don't see anything I haven't tried yet :-)
Do you have some hashrate figures?
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 September 24, 2014, 02:06:02 AM
Thanks. From a first look, I don't see anything I haven't tried yet :-)
Do you have some hashrate figures?
September 23, 2014, 07:09:06 PM
Take a look at my groestl implementation 
September 20, 2014, 03:57:27 PM
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.
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 :-)
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.
September 20, 2014, 03:49:54 PM
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.
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 :-)
September 20, 2014, 03:02:24 PM
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.
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 :-)
September 20, 2014, 01:58:13 PM
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.
September 20, 2014, 04:49:22 AM
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.
September 20, 2014, 03:53:10 AM
Congratulations Pallas.
Do you have it on Github already?
Jump to: