Re: [ANN] Kryptohash | Brand new PoW algo | 320bit hash | ed25519 | PID algo for dif
Current testing environment has ATI Radeon HD 5670 Graphics : http://www.amd.com/en-us/products/graphics/desktop/5000/5670
I also have other 3 R7 200 series to mine, but first I want to make it work on this one
Bitcoin, Litecoin, Doge, all are working with this card on GPU so Kryptohash should be okey from my point of view
I have tried the following scenarios :
--shaders 1 --shaders-mul 1
--shaders 400 --shaders-mul 1
--shaders 400 --shaders-mul 7
--shaders 128 --shaders-mul 7
everything seems to output error -54 Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)
I found that the param -w would solve the problem so right now I tried
-I 16 -g 2 -w 128 --shaders 400 --shaders-mul 7
in this case I get 3.5 Kh/s
for scrypt (litecoing) there is a param : --thread-concurrency , there is something similar here ? or any ideas to get that 3.5 value increased ? or where can I find a list with all accepted params for this version ?
Thanks
I also have other 3 R7 200 series to mine, but first I want to make it work on this one
Bitcoin, Litecoin, Doge, all are working with this card on GPU so Kryptohash should be okey from my point of view
I have tried the following scenarios :
--shaders 1 --shaders-mul 1
--shaders 400 --shaders-mul 1
--shaders 400 --shaders-mul 7
--shaders 128 --shaders-mul 7
everything seems to output error -54 Enqueueing kernel onto command queue. (clEnqueueNDRangeKernel)
I found that the param -w would solve the problem so right now I tried
-I 16 -g 2 -w 128 --shaders 400 --shaders-mul 7
in this case I get 3.5 Kh/s
for scrypt (litecoing) there is a param : --thread-concurrency , there is something similar here ? or any ideas to get that 3.5 value increased ? or where can I find a list with all accepted params for this version ?
Thanks
For Kryptohash, the thread concurrency is the combination of --shaders and --shaders-mul parameters.
Try something like this:
-w 128 --shaders 448 --shaders-mul 2
Then, increase the shaders-mul value until you find the max Kh/s
Also, try with -w 64 and see if you get better performance.