Bitcoin Forum
August 12, 2020, 04:27:16 AM *
News: Latest Bitcoin Core release: 0.20.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 [357] 358 359 360 361 362 363 364 365 366 »
  Print  
Author Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching  (Read 234010 times)
GodOfStars
Newbie
*
Offline Offline

Activity: 47
Merit: 0


View Profile
July 12, 2019, 09:51:21 AM
 #7121

Hi Doc, I find out that my Vegas 64 are all stable at memory tweak profile 8. How to apply it so it is already at 8 when restarting the miner, instead of manually pressing the + sign. Thank you
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
doktor83
Hero Member
*****
Offline Offline

Activity: 1400
Merit: 611


View Profile WWW
July 12, 2019, 10:35:34 AM
 #7122

Hi Doc, I find out that my Vegas 64 are all stable at memory tweak profile 8. How to apply it so it is already at 8 when restarting the miner, instead of manually pressing the + sign. Thank you

Try adding "tweak_profile" : 8 in config.txt, for example :

Code:
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"off_temperature" : 80,
"tweak_profile" : 8
}

SRBPolaris thread - HERE   |   SRBMiner-CN thread - HERE    |   SRBMiner-MULTI thread - HERE
http://www.srbminer.com
GodOfStars
Newbie
*
Offline Offline

Activity: 47
Merit: 0


View Profile
July 12, 2019, 11:54:49 AM
 #7123

Hi Doc, I find out that my Vegas 64 are all stable at memory tweak profile 8. How to apply it so it is already at 8 when restarting the miner, instead of manually pressing the + sign. Thank you

Try adding "tweak_profile" : 8 in config.txt, for example :

Code:
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"off_temperature" : 80,
"tweak_profile" : 8
}

Thanks Doc, for your fast response, it did work like a charm. But I will have to ask one more question though. Maybe i was thinking to do a fine tuning and isolate the weaker cards and put them one profile 8 and the rest on 9 or 10. How to do that? And last thing after updating to the latest SRB miner 1.9.1 I found out that it restarts the miner after 5 bad shares. One of my Vega VII apparently inst from the silicone lottery. I have memory at 1075 and clock at 1700 to avoid too many bad shares. I still get one bad share from time to time but its not a big deal, because I still get about 99.5%, but my question is how to disable the new option of restarting the miner after 5 bad shares or maybe to increase it to 20, in order down time due to restarts. I think I have 3-9 bad shares per 24 hours from that GPU. Thank you so much!
doktor83
Hero Member
*****
Offline Offline

Activity: 1400
Merit: 611


View Profile WWW
July 12, 2019, 02:12:15 PM
 #7124

Hi Doc, I find out that my Vegas 64 are all stable at memory tweak profile 8. How to apply it so it is already at 8 when restarting the miner, instead of manually pressing the + sign. Thank you

Try adding "tweak_profile" : 8 in config.txt, for example :

Code:
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"off_temperature" : 80,
"tweak_profile" : 8
}

Thanks Doc, for your fast response, it did work like a charm. But I will have to ask one more question though. Maybe i was thinking to do a fine tuning and isolate the weaker cards and put them one profile 8 and the rest on 9 or 10. How to do that? And last thing after updating to the latest SRB miner 1.9.1 I found out that it restarts the miner after 5 bad shares. One of my Vega VII apparently inst from the silicone lottery. I have memory at 1075 and clock at 1700 to avoid too many bad shares. I still get one bad share from time to time but its not a big deal, because I still get about 99.5%, but my question is how to disable the new option of restarting the miner after 5 bad shares or maybe to increase it to 20, in order down time due to restarts. I think I have 3-9 bad shares per 24 hours from that GPU. Thank you so much!

For per card configuration use gpu_conf array, here is an example :

Code:
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" :
[
{
  "id" : 0,
  "intensity" : 112,
  "worksize" : 16,
  "threads" : 2,
  "tweak_profile" : 8
},
{
  "id" : 1,
  "intensity" : 112,
  "worksize" : 16,
  "threads" : 2,
  "tweak_profile" : 10
}
]
}

You get the idea. Also on the first page or in the readme.txt you have more info.

Regarding the restart on 5 bad shares, well yes, i don't know myself why i didn't make that one optional  Grin
I will add a parameter that disables this in the next version in a few days.

SRBPolaris thread - HERE   |   SRBMiner-CN thread - HERE    |   SRBMiner-MULTI thread - HERE
http://www.srbminer.com
GodOfStars
Newbie
*
Offline Offline

Activity: 47
Merit: 0


View Profile
July 12, 2019, 02:56:45 PM
 #7125

Hi Doc, I find out that my Vegas 64 are all stable at memory tweak profile 8. How to apply it so it is already at 8 when restarting the miner, instead of manually pressing the + sign. Thank you

Try adding "tweak_profile" : 8 in config.txt, for example :

Code:
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"off_temperature" : 80,
"tweak_profile" : 8
}

Thanks Doc, for your fast response, it did work like a charm. But I will have to ask one more question though. Maybe i was thinking to do a fine tuning and isolate the weaker cards and put them one profile 8 and the rest on 9 or 10. How to do that? And last thing after updating to the latest SRB miner 1.9.1 I found out that it restarts the miner after 5 bad shares. One of my Vega VII apparently inst from the silicone lottery. I have memory at 1075 and clock at 1700 to avoid too many bad shares. I still get one bad share from time to time but its not a big deal, because I still get about 99.5%, but my question is how to disable the new option of restarting the miner after 5 bad shares or maybe to increase it to 20, in order down time due to restarts. I think I have 3-9 bad shares per 24 hours from that GPU. Thank you so much!

For per card configuration use gpu_conf array, here is an example :

Code:
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" :
[
{
  "id" : 0,
  "intensity" : 112,
  "worksize" : 16,
  "threads" : 2,
  "tweak_profile" : 8
},
{
  "id" : 1,
  "intensity" : 112,
  "worksize" : 16,
  "threads" : 2,
  "tweak_profile" : 10
}
]
}

You get the idea. Also on the first page or in the readme.txt you have more info.

Regarding the restart on 5 bad shares, well yes, i don't know myself why i didn't make that one optional  Grin
I will add a parameter that disables this in the next version in a few days.

God Bless, you are amazing!
KhorneFlake
Newbie
*
Offline Offline

Activity: 27
Merit: 0


View Profile
July 13, 2019, 09:47:57 AM
 #7126

Downloaded the latest 1.9.1 version and still the main GPU starts at 1000h/s and drops over time from there. Sniff, shame I cannot use the 1.8.0 anymore.
Topcd
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
July 13, 2019, 09:14:53 PM
 #7127

I've tested V1.9.1 on one of my Rigs with 6 RX VEGAs and it is stable after 1 day and a half of mining.
if it goes without any error for two or three days, then i will start to set it up on all of my Rigs.
proof: https://i.ibb.co/DW4XrYt/Monero-14-July.png
netmebtc
Newbie
*
Offline Offline

Activity: 72
Merit: 0


View Profile
July 14, 2019, 11:56:37 PM
 #7128

@doktor83, Hello, When will SRBminer support turtle's new algo "chukwa"   and loki's new algo "RandmXL"?
doktor83
Hero Member
*****
Offline Offline

Activity: 1400
Merit: 611


View Profile WWW
July 15, 2019, 11:23:51 AM
 #7129

@doktor83, Hello, When will SRBminer support turtle's new algo "chukwa"   and loki's new algo "RandmXL"?

I haven't decided yet what to do with the randomx algo family - it will suck on AMD gpus. Chukwa isn't in my plans atm.

SRBPolaris thread - HERE   |   SRBMiner-CN thread - HERE    |   SRBMiner-MULTI thread - HERE
http://www.srbminer.com
doktor83
Hero Member
*****
Offline Offline

Activity: 1400
Merit: 611


View Profile WWW
July 15, 2019, 12:15:23 PM
 #7130

V1.9.2
- Added parameter '--disablerestartonrejectedshares' to disable auto restart of miner on too many rejected shares
- Added parameter '--maxrejectedshares' to set the number of allowed rejected shares on a pool connection ( min 1, max 100, def. 15)
- Optimisations in OpenCL code, so tiny hashrate increase could be seen on Vegas and Ellesmere cards.
- Minor bug fixes


+ Previous version added a feature that restarts miner when there are too many rejected shares. This version adds a new parameter to disable this feature, '--disablerestartonrejectedshares'

+ Also previous version had a hardcoded number of 5 for the max allowed rejected shares, this is now changed to 15, or you can set your own value with '--maxrejectedshares' value

+ Vegas and Ellesmere cards can see some small hashrate increase on major algorithms

SRBPolaris thread - HERE   |   SRBMiner-CN thread - HERE    |   SRBMiner-MULTI thread - HERE
http://www.srbminer.com
Topcd
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
July 15, 2019, 01:59:19 PM
Last edit: July 16, 2019, 06:21:50 AM by Topcd
 #7131

@doktor83, Hello, When will SRBminer support turtle's new algo "chukwa"   and loki's new algo "RandmXL"?

I haven't decided yet what to do with the randomx algo family - it will suck on AMD gpus. Chukwa isn't in my plans atm.
RandomX is the good news for CPU miners and bad news for GPU miners, specially for RX Vega Owners like me as i've heard that the hash rate will drop off around 50% for Rx Vega on this new algorithm, but they say they are doing some optimizations to make it more acceptable.
Let's wait and see what happens! Undecided
GodOfStars
Newbie
*
Offline Offline

Activity: 47
Merit: 0


View Profile
July 15, 2019, 05:02:03 PM
 #7132

V1.9.2
- Added parameter '--disablerestartonrejectedshares' to disable auto restart of miner on too many rejected shares
- Added parameter '--maxrejectedshares' to set the number of allowed rejected shares on a pool connection ( min 1, max 100, def. 15)
- Optimisations in OpenCL code, so tiny hashrate increase could be seen on Vegas and Ellesmere cards.
- Minor bug fixes


+ Previous version added a feature that restarts miner when there are too many rejected shares. This version adds a new parameter to disable this feature, '--disablerestartonrejectedshares'

+ Also previous version had a hardcoded number of 5 for the max allowed rejected shares, this is now changed to 15, or you can set your own value with '--maxrejectedshares' value

+ Vegas and Ellesmere cards can see some small hashrate increase on major algorithms

Abut the rejected shares parameter, where do we write this code, in the config file or in the start.bat?
doktor83
Hero Member
*****
Offline Offline

Activity: 1400
Merit: 611


View Profile WWW
July 15, 2019, 05:55:05 PM
 #7133

V1.9.2
- Added parameter '--disablerestartonrejectedshares' to disable auto restart of miner on too many rejected shares
- Added parameter '--maxrejectedshares' to set the number of allowed rejected shares on a pool connection ( min 1, max 100, def. 15)
- Optimisations in OpenCL code, so tiny hashrate increase could be seen on Vegas and Ellesmere cards.
- Minor bug fixes


+ Previous version added a feature that restarts miner when there are too many rejected shares. This version adds a new parameter to disable this feature, '--disablerestartonrejectedshares'

+ Also previous version had a hardcoded number of 5 for the max allowed rejected shares, this is now changed to 15, or you can set your own value with '--maxrejectedshares' value

+ Vegas and Ellesmere cards can see some small hashrate increase on major algorithms

Abut the rejected shares parameter, where do we write this code, in the config file or in the start.bat?

Every parameter that starts with -- is a cmd parameter and goes to start.bat:

Code:
SRBMiner-CN.exe --config Config\config-normalv4.txt --pools pools.txt --maxrejectedshares 20

SRBPolaris thread - HERE   |   SRBMiner-CN thread - HERE    |   SRBMiner-MULTI thread - HERE
http://www.srbminer.com
GodOfStars
Newbie
*
Offline Offline

Activity: 47
Merit: 0


View Profile
July 15, 2019, 07:24:38 PM
 #7134

V1.9.2
- Added parameter '--disablerestartonrejectedshares' to disable auto restart of miner on too many rejected shares
- Added parameter '--maxrejectedshares' to set the number of allowed rejected shares on a pool connection ( min 1, max 100, def. 15)
- Optimisations in OpenCL code, so tiny hashrate increase could be seen on Vegas and Ellesmere cards.
- Minor bug fixes


+ Previous version added a feature that restarts miner when there are too many rejected shares. This version adds a new parameter to disable this feature, '--disablerestartonrejectedshares'

+ Also previous version had a hardcoded number of 5 for the max allowed rejected shares, this is now changed to 15, or you can set your own value with '--maxrejectedshares' value

+ Vegas and Ellesmere cards can see some small hashrate increase on major algorithms

Abut the rejected shares parameter, where do we write this code, in the config file or in the start.bat?

Every parameter that starts with -- is a cmd parameter and goes to start.bat:

Code:
SRBMiner-CN.exe --config Config\config-normalv4.txt --pools pools.txt --maxrejectedshares 20

Thank you Doc, for the update and you response. On another note perhaps an idea about the following update. Won't it be cool if let's say to automatically restart the miner every 2-3 days so at least the miner can insure a 24/7 undisturbed operation. For example if the GPUs are mining more than a week straight they start to become buggy at some point. Like, you won't able to close the miner whiteout a hard rig restart or power off, or one of the gpus will die and the miner wont be able to start it back again. So i was thinking if the miner automatically restarts every 2-3 days, of course optional input from the user, would simply amazing. Thaks ones again!
sky2018miner
Newbie
*
Offline Offline

Activity: 33
Merit: 0


View Profile
July 17, 2019, 04:39:54 AM
 #7135

Hello
I can not stop mining Rio
on Cryptonight Gpu
other algorithms work
I bring a log
[2019-07-16 23:26:22] Startup monitor attached
[2019-07-16 23:26:22] Miner version: 1.9.2
[2019-07-16 23:26:22] Windows version: 10.0 build 17763
[2019-07-16 23:26:22] Video driver version: 24.20.11021.1000
[2019-07-16 23:26:22] Please run miner as administrator to enable tweaking
[2019-07-16 23:26:32] AMD Platform ID: 0
[2019-07-16 23:26:32] AMD platform FOUND
[2019-07-16 23:26:32] Found 7 AMD devices
[2019-07-16 23:26:32] CPU AES-NI: FALSE
[2019-07-16 23:26:32] PREPARE DATA: FALSE
[2019-07-16 23:26:32] GPU0: AMD Radeon (TM) R7 370 Series [baffin] [2048 MB][CU: 14][I: 13.0][W: 8][T: 2][F: 0][BUS: 1]
[2019-07-16 23:26:32] GPU1: AMD Radeon (TM) R7 370 Series [baffin] [2048 MB][CU: 14][I: 13.6][W: 8][T: 2][F: 0][BUS: 3]
[2019-07-16 23:26:32] GPU2: AMD Radeon (TM) R7 370 Series [tonga] [2048 MB][CU: 28][I: 27.0][W: 8][T: 2][F: 4][BUS: 4]
[2019-07-16 23:26:32] GPU3: AMD Radeon (TM) R7 370 Series [baffin] [4096 MB][CU: 16][I: 15.5][W: 8][T: 2][F: 0][BUS: 8]
[2019-07-16 23:26:32] GPU4: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][CU: 16][I: 16.0][W: 8][T: 2][F: 0][BUS: 9]
[2019-07-16 23:26:32] GPU5: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][CU: 16][I: 16.0][W: 8][T: 2][F: 0][BUS: 10]
[2019-07-16 23:26:32] GPU6: AMD Radeon (TM) R7 370 Series [pitcairn] [2048 MB][CU: 16][I: 16.0][W: 8][T: 2][F: 0][BUS: 11]
[2019-07-16 23:26:32] ADL is enabled
[2019-07-16 23:26:32] Algorithm: Cryptonight Gpu
[2019-07-16 23:26:32] Algo switching: disabled
[2019-07-16 23:26:32] Coin forking: disabled
[2019-07-16 23:26:32] Gpu watchdog: enabled [normal mode]
[2019-07-16 23:26:32] Startup monitor: enabled
[2019-07-16 23:26:32] Tweaking: disabled
[2019-07-16 23:26:32] Socket initialiasation done
[2019-07-16 23:26:32] Starting init of gpu threads
[2019-07-16 23:26:32] Created OCL context
[2019-07-16 23:26:33] Created OCL input buffer for DeviceID 0 (Thread 0)
[2019-07-16 23:26:33] load_binary: Couldn't load default binary for DeviceID 0 (Thread 0)
[2019-07-16 23:26:33] ctx->headers[0] created for DeviceID 0 (Thread 0)
[2019-07-16 23:26:33] ctx->Program created for DeviceID 0 (Thread 0)
[2019-07-16 23:26:33] Compiling [gpu] kernel for DEVICE BUS_ID[1]
[2019-07-16 23:26:35] Binary kernel for DeviceID 0 (Thread 0) saved to disk
[2019-07-16 23:26:35] Created OCL input buffer for DeviceID 0 (Thread 1)
[2019-07-16 23:26:35] load_binary: Couldn't load default binary for DeviceID 0 (Thread 1)
[2019-07-16 23:26:35] Loading [gpu] kernel for DEVICE BUS_ID[1]
[2019-07-16 23:26:35] ctx->Program for DeviceID 0 (Thread 1) loaded
[2019-07-16 23:26:36] Created OCL input buffer for DeviceID 1 (Thread 2)
[2019-07-16 23:26:36] load_binary: Couldn't load default binary for DeviceID 1 (Thread 2)
[2019-07-16 23:26:36] Loading [gpu] kernel for DEVICE BUS_ID[3]
[2019-07-16 23:26:36] ctx->Program for DeviceID 1 (Thread 2) loaded
[2019-07-16 23:26:36] Created OCL input buffer for DeviceID 1 (Thread 3)
[2019-07-16 23:26:36] load_binary: Couldn't load default binary for DeviceID 1 (Thread 3)
[2019-07-16 23:26:36] Loading [gpu] kernel for DEVICE BUS_ID[3]
[2019-07-16 23:26:36] ctx->Program for DeviceID 1 (Thread 3) loaded
[2019-07-16 23:26:36] Created OCL input buffer for DeviceID 2 (Thread 4)
[2019-07-16 23:26:36] load_binary: Couldn't load default binary for DeviceID 2 (Thread 4)
[2019-07-16 23:26:36] ctx->headers[0] created for DeviceID 2 (Thread 4)
[2019-07-16 23:26:36] Error CL_COMPILE_PROGRAM_FAILURE when calling clCompileProgram [ctx->Program] for DeviceID 2 (Thread 4)
[2019-07-16 23:26:36] Error while creating GPU threads.. Stopping miner process.
[2019-07-16 23:26:36] Socket cleanup done
[2019-07-16 23:26:36] Shutting down miner...


please fix it
Turkish88
Full Member
***
Offline Offline

Activity: 672
Merit: 104



View Profile
July 17, 2019, 04:47:39 AM
 #7136

@doktor83, Hello, When will SRBminer support turtle's new algo "chukwa"   and loki's new algo "RandmXL"?

I haven't decided yet what to do with the randomx algo family - it will suck on AMD gpus. Chukwa isn't in my plans atm.
RandomX is the good news for CPU miners and bad news for GPU miners, specially for RX Vega Owners like me as i've heard that the hash rate will drop off around 50% for Rx Vega on this new algorithm, but they say they are doing some optimizations to make it more acceptable.
Let's wait and see what happens! Undecided

But its better then switching to asic friendly algo, because on this scenario RX Vega hashrates drops more.
Lets hope to the succes of randomX

HDD Recovery Services
Telegram: @hddrecoveryrepair
cas333
Newbie
*
Offline Offline

Activity: 45
Merit: 0


View Profile
July 17, 2019, 06:43:29 AM
Last edit: July 17, 2019, 12:02:59 PM by cas333
 #7137

One of the most stable versions. Thanks Dok!  Wink
just4u
Newbie
*
Offline Offline

Activity: 6
Merit: 0


View Profile
July 21, 2019, 05:18:01 AM
Last edit: July 21, 2019, 05:47:47 AM by just4u
 #7138

 It's been awhile since I've used SRB Miner.  Mining XMR  using 2x Strix Vega 56s with Hynix Memory (and latest drivers as I don't only mine with the system) Can't really go above tweak profile 2 without artifices, same goes if I raise mem clocks to high (930+)  Is there anything else I can try based on the information I am giving here?  I think it's fairly ok.. not sure what else I can do. Thanks for any advice.

GPU0 :    1780 H/s [T: 55c, RPM: 1998, CC: 1307 MHz, MC: 900 MHz][BUS:29]
GPU1 :    1796 H/s [T: 65c, RPM: 2446, CC: 1307 MHz, MC: 900 MHz][BUS:32]
Watts around 160 per card (GPUZ)


Batfile:

setx GPU_MAX_HEAP_SIZE 100   
setx GPU_MAX_USE_SYNC_OBJECTS 1   
setx GPU_SINGLE_ALLOC_PERCENT 100   
setx GPU_MAX_ALLOC_PERCENT 100   
setx GPU_MAX_SINGLE_ALLOC_PERCENT 100   
@echo off   
cd %~dp0   
   
cls   
SRBMiner-CN.exe --config Config\config-xmr.txt --pools Pools\pools-xmr.txt


Config file is fairly standard,

{   
"cryptonight_type" : "normalv4",   
"intensity" : 0,   
"double_threads" : true,
"persistent_memory" : false,
"gpu_conf" :
[
   {
     "id" : 0,
     "intensity" : 112,
     "worksize" : 16,
     "threads" : 2,
     "tweak_profile" : 2
   },
   {
     "id" : 1,
     "intensity" : 112,
     "worksize" : 16,
     "threads" : 2,
     "tweak_profile" : 2
   }
]
   
}

Topcd
Newbie
*
Offline Offline

Activity: 7
Merit: 0


View Profile
July 21, 2019, 10:46:21 AM
 #7139

It's been awhile since I've used SRB Miner.  Mining XMR  using 2x Strix Vega 56s with Hynix Memory (and latest drivers as I don't only mine with the system) Can't really go above tweak profile 2 without artifices, same goes if I raise mem clocks to high (930+)  Is there anything else I can try based on the information I am giving here?  I think it's fairly ok.. not sure what else I can do. Thanks for any advice.

GPU0 :    1780 H/s [T: 55c, RPM: 1998, CC: 1307 MHz, MC: 900 MHz][BUS:29]
GPU1 :    1796 H/s [T: 65c, RPM: 2446, CC: 1307 MHz, MC: 900 MHz][BUS:32]
Watts around 160 per card (GPUZ)


Batfile:

setx GPU_MAX_HEAP_SIZE 100   
setx GPU_MAX_USE_SYNC_OBJECTS 1   
setx GPU_SINGLE_ALLOC_PERCENT 100   
setx GPU_MAX_ALLOC_PERCENT 100   
setx GPU_MAX_SINGLE_ALLOC_PERCENT 100   
@echo off   
cd %~dp0   
   
cls   
SRBMiner-CN.exe --config Config\config-xmr.txt --pools Pools\pools-xmr.txt


Config file is fairly standard,

{   
"cryptonight_type" : "normalv4",   
"intensity" : 0,   
"double_threads" : true,
"persistent_memory" : false,
"gpu_conf" :
[
   {
     "id" : 0,
     "intensity" : 112,
     "worksize" : 16,
     "threads" : 2,
     "tweak_profile" : 2
   },
   {
     "id" : 1,
     "intensity" : 112,
     "worksize" : 16,
     "threads" : 2,
     "tweak_profile" : 2
   }
]
   
}



I recommend you to flash Vega 64 bios on your Vega 56s, so you will be able to get at least 1900 h/s per card in normal condition.
livada
Newbie
*
Offline Offline

Activity: 404
Merit: 0


View Profile WWW
July 21, 2019, 10:49:20 AM
 #7140

It's been awhile since I've used SRB Miner.  Mining XMR  using 2x Strix Vega 56s with Hynix Memory (and latest drivers as I don't only mine with the system) Can't really go above tweak profile 2 without artifices, same goes if I raise mem clocks to high (930+)  Is there anything else I can try based on the information I am giving here?  I think it's fairly ok.. not sure what else I can do. Thanks for any advice.

GPU0 :    1780 H/s [T: 55c, RPM: 1998, CC: 1307 MHz, MC: 900 MHz][BUS:29]
GPU1 :    1796 H/s [T: 65c, RPM: 2446, CC: 1307 MHz, MC: 900 MHz][BUS:32]
Watts around 160 per card (GPUZ)


Batfile:

setx GPU_MAX_HEAP_SIZE 100   
setx GPU_MAX_USE_SYNC_OBJECTS 1   
setx GPU_SINGLE_ALLOC_PERCENT 100   
setx GPU_MAX_ALLOC_PERCENT 100   
setx GPU_MAX_SINGLE_ALLOC_PERCENT 100   
@echo off   
cd %~dp0   
   
cls   
SRBMiner-CN.exe --config Config\config-xmr.txt --pools Pools\pools-xmr.txt


Config file is fairly standard,

{   
"cryptonight_type" : "normalv4",   
"intensity" : 0,   
"double_threads" : true,
"persistent_memory" : false,
"gpu_conf" :
[
   {
     "id" : 0,
     "intensity" : 112,
     "worksize" : 16,
     "threads" : 2,
     "tweak_profile" : 2
   },
   {
     "id" : 1,
     "intensity" : 112,
     "worksize" : 16,
     "threads" : 2,
     "tweak_profile" : 2
   }
]
   
}



I recommend you to flash Vega 64 bios on your Vega 56s, so you will be able to get at least 1900 h/s per card in normal condition.
hynix not good with 64 bios. Just use
 TRM
and you have 2100 with hynix or 2350Hr with samsung vega 56
Pages: « 1 ... 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 [357] 358 359 360 361 362 363 364 365 366 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!