Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 200. (Read 237247 times)

Quote from: doktor83 on July 09, 2018, 07:58:40 AM

my result vega64 1550/920, 1100/920 heavy algo.
Is it possible to make more than 1700hs?

Driver?

win10-64bit-radeon-software-adrenalin-edition-18.6.1-june13
https://thumb.ibb.co/diHN98/img_2018_07_09_12_10_23.png

what motherboard you use for connecting all the vegas?

UnclWish

sr. member

Activity: 1484

Merit: 253

Quote from: UnclWish on July 09, 2018, 07:51:31 AM

Quote from: doktor83 on July 09, 2018, 07:34:02 AM

Quote from: UnclWish on July 09, 2018, 07:51:31 AM

Allready trying... Please say in 1.6.3 on cn-v7 to got max speed need to wait some time? Or max speed is after start?

it should be in a few minutes max, on my hynix 580 8gb cards i get the same hash as on 1.6.0.
Also on 470 8gb.
Don't have samsung 580 8g to try.

What intensity you're use and what speed have?

Straps for ETH, 1150/2050 , 100w from the wall ~ 950hs on v7
56/8/2

yes it can be pushed way over 1000hs but im not looking for that, only using it for testing the miner.

With 1.6.3 the same situation as with 1.6.2... On cn-v7 RX 580 8Gb max speed is 1000 h/s on intensity 108, but not every launch. Miner needs to several starts to get this speed. Waiting up to 5 minutes not helps. Mostly speed is 985 h/s. On 1.6.0 speed is up to 1035-1040 h/s with intensity 116-117.

duyquang06

newbie

Activity: 154

Merit: 0

Doc, tks for 1.6.3

I still stick with Aug23. I will test and report the result. Hope it got buff hashrate too!!!

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: doktor83 on July 09, 2018, 07:34:02 AM

Quote from: doktor83 on July 09, 2018, 07:34:02 AM

Allready trying... Please say in 1.6.3 on cn-v7 to got max speed need to wait some time? Or max speed is after start?

it should be in a few minutes max, on my hynix 580 8gb cards i get the same hash as on 1.6.0.
Also on 470 8gb.
Don't have samsung 580 8g to try.

What intensity you're use and what speed have?

Straps for ETH, 1150/2050 , 100w from the wall ~ 950hs on v7
56/8/2

yes it can be pushed way over 1000hs but im not looking for that, only using it for testing the miner.

UnclWish

sr. member

Activity: 1484

Merit: 253

Quote from: doktor83 on July 09, 2018, 07:43:51 AM

Allready trying... Please say in 1.6.3 on cn-v7 to got max speed need to wait some time? Or max speed is after start?

it should be in a few minutes max, on my hynix 580 8gb cards i get the same hash as on 1.6.0.
Also on 470 8gb.
Don't have samsung 580 8g to try.

What intensity you're use and what speed have?

Amigo9881

newbie

Activity: 14

Merit: 0

Quote from: Amigo9881 on July 09, 2018, 07:13:25 AM

Dok, thanks for providing an awesome miner.

1. Can you please share you power play table file which you are using with 18.6.1 drivers + Overdrivetool settings for crytonightV7 algo

2. What are your settings for heavy algo in overdrivetool, have you tested yet ?

Thanks

1. powerplay table : https://files.fm/u/s68u78zx
Overdrivent: GPU 1450/925mV , MEM 950/910mV

Im not looking to get the max hash from the card, just set a value that is stable and works for my miner development.

2. Same settings, as im only using it for testing the miner

Thanks Alot

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: Amigo9881 on July 09, 2018, 07:13:25 AM

Dok, thanks for providing an awesome miner.

1. Can you please share you power play table file which you are using with 18.6.1 drivers + Overdrivetool settings for crytonightV7 algo

2. What are your settings for heavy algo in overdrivetool, have you tested yet ?

Thanks

1. powerplay table : https://files.fm/u/s68u78zx
Overdrivent: GPU 1450/925mV , MEM 950/910mV

Im not looking to get the max hash from the card, just set a value that is stable and works for my miner development.

2. Same settings, as im only using it for testing the miner

what i noticed is when connected with AnyDesk or TeamV the hashrate can't get to the max.
What i do is restart vega driver, start miner, disconnect from anydesk, connect back in 10 minutes to check hashrate and voila, it's good Cheesy

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: doktor83 on July 09, 2018, 07:02:44 AM

Allready trying... Please say in 1.6.3 on cn-v7 to got max speed need to wait some time? Or max speed is after start?

it should be in a few minutes max, on my hynix 580 8gb cards i get the same hash as on 1.6.0.
Also on 470 8gb.
Don't have samsung 580 8g to try.

Amigo9881

newbie

Activity: 14

Merit: 0

Dok, thanks for providing an awesome miner.

1. Can you please share you power play table file which you are using with 18.6.1 drivers + Overdrivetool settings for crytonightV7 algo

2. What are your settings for heavy algo in overdrivetool, have you tested yet ?

Thanks

UnclWish

sr. member

Activity: 1484

Merit: 253

Quote from: UnclWish on July 09, 2018, 07:02:00 AM

Quote from: UnclWish on July 09, 2018, 07:02:00 AM

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 (try with adrenaline 18.3.4 or adrenaline 18.6.1)

+ 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

What about cn-v7 algo on RX 5xx cards? You wanted to return speed from 1.6.0. On 1.6.1 and 1.6.2 cn-v7 algo on RX 580 is slower...

you should try

Allready trying... Please say in 1.6.3 on cn-v7 to got max speed need to wait some time? Or max speed is after start?

doktor83

hero member

Activity: 2548

Merit: 626

Quote from: mk111 on July 09, 2018, 06:58:31 AM

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 (try with adrenaline 18.3.4 or adrenaline 18.6.1)

+ 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

What about cn-v7 algo on RX 5xx cards? You wanted to return speed from 1.6.0. On 1.6.1 and 1.6.2 cn-v7 algo on RX 580 is slower...

you should try

doktor83

hero member

Activity: 2548

Merit: 626

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 (try with adrenaline 18.3.4 or adrenaline 18.6.1)

+ 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

Great stuff!
I am getting 40H/s extra per Vega 56 with V1.6.3

That is what i measured too, increase on V7 about ~35HS.
But listen i just installed 18.6.1 and got even more HS! +30 LOL

So nice, this is a huge boost Grin

UnclWish

sr. member

Activity: 1484

Merit: 253

Quote from: roma__11 on July 09, 2018, 05:12:34 AM

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 (try with adrenaline 18.3.4 or adrenaline 18.6.1)

+ 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

What about cn-v7 algo on RX 5xx cards? You wanted to return speed from 1.6.0. On 1.6.1 and 1.6.2 cn-v7 algo on RX 580 is slower...

livada

newbie

Activity: 417

Merit: 0

my result vega64 1550/920, 1100/920 heavy algo.
Is it possible to make more than 1700hs?

Driver?

win10-64bit-radeon-software-adrenalin-edition-18.6.1-june13
https://thumb.ibb.co/diHN98/img_2018_07_09_12_10_23.png

WOW- this is nice- how much does it spend on the wall?

gpu mv? mem mv? pls SS overdrive setup

mk111

jr. member

Activity: 230

Merit: 1

Quote from: roma__11 on July 09, 2018, 05:12:34 AM

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 (try with adrenaline 18.3.4 or adrenaline 18.6.1)

+ 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

Great stuff!
On heavy algo I am getting 40H/s extra per Vega 56 with V1.6.3

doktor83

hero member

Activity: 2548

Merit: 626

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

Don't copy new version of miner over old one, or if you do make sure you delete .srb files before running it!

yaya79

newbie

Activity: 6

Merit: 0

my result vega64 1550/920, 1100/920 heavy algo.
Is it possible to make more than 1700hs?

Driver?

win10-64bit-radeon-software-adrenalin-edition-18.6.1-june13
https://thumb.ibb.co/diHN98/img_2018_07_09_12_10_23.png

Thx! With 18.6.1 driver - 1730hs (1550 core).

roma__11

newbie

Activity: 115

Merit: 0