V1.6.3
- More speed on Vega56 cards on every algo (probably on Vega64 and VegaFE too, i don't have them to test)
- Added parameter --enableduplicategpuid (used in start.bat), that enables to use the same gpu id in gpu_conf multiple times
- Removed useless kernels 3 and 4
- Removed useless CPU opencl support
+ Vega cards should get even more speed than in previous version (tested with adrenaline 18.3.4)
+ Added parameter --enableduplicategpuid (in .bat) which basically allows you to do something like this :
"gpu_conf" :
[
{ "id" : 0, "intensity" : 120, "worksize" : 8, "threads" : 1},
{ "id" : 0, "intensity" : 120.5, "worksize" : 8, "threads" : 1},
]
So instead of using the same settings for every thread on same GPU, you can define different intensity for example for one thread.
This way maybe you can squeeze out a little more hash from your GPU.
On initialisation this is displayed as DIFFERENT GPU'S, but on hashrate display threads of same gpu are merged, so a per gpu hashrate is still displayed, not a per thread speed.
+ Removed a few useless things like kernels 3&4, and CPU OpenCL support, nobody used these but they just took me more time when implementing something new
- More speed on Vega56 cards on every algo (probably on Vega64 and VegaFE too, i don't have them to test)
- Added parameter --enableduplicategpuid (used in start.bat), that enables to use the same gpu id in gpu_conf multiple times
- Removed useless kernels 3 and 4
- Removed useless CPU opencl support
+ Vega cards should get even more speed than in previous version (tested with adrenaline 18.3.4)
+ Added parameter --enableduplicategpuid (in .bat) which basically allows you to do something like this :
"gpu_conf" :
[
{ "id" : 0, "intensity" : 120, "worksize" : 8, "threads" : 1},
{ "id" : 0, "intensity" : 120.5, "worksize" : 8, "threads" : 1},
]
So instead of using the same settings for every thread on same GPU, you can define different intensity for example for one thread.
This way maybe you can squeeze out a little more hash from your GPU.
On initialisation this is displayed as DIFFERENT GPU'S, but on hashrate display threads of same gpu are merged, so a per gpu hashrate is still displayed, not a per thread speed.
+ Removed a few useless things like kernels 3&4, and CPU OpenCL support, nobody used these but they just took me more time when implementing something new
Hi doktor,
Nice job,
Testing version 1.6.3 with heavy and cryptov7 i got better hashes in vega (30hs more)
Using the bittube v2 algo i got a less hash , 900 hs.. instead of 15xx..
I tell about this problem some posts ago even in prevous version after a time the hash drop a lot , in bitube algo.
Can you check your kernel for this algo.
Im on 1709 windows version and using 18.6.1 amd drivers
Thanks