Bitcoin Forum
May 23, 2019, 04:15:32 AM *
News: Latest Bitcoin Core release: 0.18.0 [Torrent] (New!)
 
   Home   Help Search Login Register More  
Pages: « 1 ... 293 294 295 296 297 298 299 300 301 302 303 304 305 306 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 »
  Print  
Author Topic: SRBMiner Cryptonight AMD GPU Miner V1.8.8 - native algo switching  (Read 204106 times)
doktor83
Hero Member
*****
Offline Offline

Activity: 1022
Merit: 582


View Profile WWW
May 06, 2019, 12:12:44 PM
Last edit: May 08, 2019, 11:01:48 AM by doktor83
 #6841

V1.8.8
- Reduced CPU usage up to ~50%, can be noticed on algos with small scratchpad
- User is now informed about tweaking status on the screen too, not just in log
- No more --gpureorder, device ordering by bus id is now the default/only display mode
- Added parameter --watchdogrounds , which controls after how many rounds will watchdog trigger
- min_rig_speed_duration default is 1 minute now, because of the new --watchdogrounds parameter
- Fixed a few cosmetical things on web stats


+ If not using 'old_mode', on weak CPU's the cpu usage could go boom on algos with small scratchpad (UPX2, Turtle). In this version i managed to lower the cpu usage up to ~50%.
This also brings a small hashrate increase for RX cards on UPX2 as a side effect Smiley

+ The default (and only) device ordering mode from now on is ascending by bus id, as it is in OverdriveNTool. Parameter --gpureorder is removed.
NOTE: if you are using gpu_conf or --cgpuid, please run --listdevices to check if you are using the right deviceid!

+ Because of some trouble with gpu/min_rig_speed watchdog and kernel precompilation on CN/R (V4), a new parameter --watchdogrounds was added, so you can control after how many check-rounds will the watchdog trigger.
The GPU crash watchdog has a fixed interval of 30 seconds = 1 round. That means it will trigger miner restart only after --watchdogrounds * 30 sec (default number of rounds is 5).
5 * 30 = 150 sec ~ 2.5 minutes. If gpu crashes and can't recover for 2.5 minutes, the miner will trigger the restart action.

min_rig_speed parameter is also affected by --watchdogrounds from now on. The 'min_rig_speed_duration' parameter default value is now 60 sec, this is the value as the above for the gpu crash watchdog, except that you can change the value of this to anything >= 30 sec.
Taking the default value of 60 seconds and 5 rounds, it is 5 * 60 = 300 sec = 5 minute, that means if for 5 minutes the 'min_rig_speed' < total hashing speed, then it will trigger miner restart.

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

Posts: 1558584932

View Profile Personal Message (Offline)

Ignore
1558584932
Reply with quote  #2

1558584932
Report to moderator
1558584932
Hero Member
*
Offline Offline

Posts: 1558584932

View Profile Personal Message (Offline)

Ignore
1558584932
Reply with quote  #2

1558584932
Report to moderator
1558584932
Hero Member
*
Offline Offline

Posts: 1558584932

View Profile Personal Message (Offline)

Ignore
1558584932
Reply with quote  #2

1558584932
Report to moderator
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, which will follow the rules of the network no matter what miners do. Even if every miner decided to create 1000 bitcoins per block, full nodes would stick to the rules and reject those blocks.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1558584932
Hero Member
*
Offline Offline

Posts: 1558584932

View Profile Personal Message (Offline)

Ignore
1558584932
Reply with quote  #2

1558584932
Report to moderator
clousian
Newbie
*
Offline Offline

Activity: 32
Merit: 0


View Profile
May 07, 2019, 12:12:17 AM
Last edit: May 07, 2019, 12:23:58 AM by clousian
 #6842

Anyone have any experience running SRB v1.8.7 as a client in minerstat? Whatever I do in the config file, it doesn't translate when I launch srb in minerstat.

My settings for monero:
{
"cryptonight_type" : “normalv4”,
"intensity" : 0,
"double_threads" : true,
"gpu_conf" :
[
   {
     "id" : 0,
     "intensity" : 106,
     "worksize" : 8,
     "threads" : 2,
     "old_mode" : true
   },
   {
     "id" : 1,
     "intensity" : 59,
     "worksize" : 8,
     "threads" : 2,
     "old_mode" : true
   },
   {
     "id" : 2,
     "intensity" : 106,
     "worksize" : 8,
     "threads" : 2,
     "old_mode" : true
   },
   {
     "id" : 3,
     "intensity" : 105,
     "worksize" : 8,
     "threads" : 2,
     "old_mode" : true
   },
   {
     "id" : 4,
     "intensity" : 105,
     "worksize" : 8,
     "threads" : 2,
     "old_mode" : true
   }
]
}

What srb in minerstat is stuck at:

id 0,2,3,4 at 71 intensity id: 1 at 56 intensity. What am I doing wrong in the normalv4 config?
optii
Newbie
*
Offline Offline

Activity: 21
Merit: 0


View Profile
May 07, 2019, 08:07:58 AM
 #6843

V1.8.8
- Reduced CPU usage up to ~50%, can be noticed on algos with small scratchpad
- User is now informed about tweaking status on the screen too, not just in log
- No more --gpureorder, device ordering by bus id is now the default/only display mode
- Added parameter --watchdogrounds , which controls after how many rounds will watchdog trigger
- min_rig_speed_duration default is 1 minute now, because of the new --watchdogrounds parameter
- Fixed a few cosmetical things on web stats


+ If not using 'old_mode', on weak CPU's the cpu usage could go boom on algos with small scratchpad (UPX2, Turtle). In this version i managed to lower the cpu usage up to ~50%.
This also brings a small hashrate increase for RX cards on UPX2 as a side effect Smiley

+ The default (and only) device ordering mode from now on is ascending by bus id, as it is in OverdriveNTool. Parameter --gpureorder is removed.

+ Because of some trouble with gpu/min_rig_speed watchdog and kernel precompilation on CN/R (V4), a new parameter --watchdogrounds was added, so you can control after how many check-rounds will the watchdog trigger.
The GPU crash watchdog has a fixed interval of 30 seconds = 1 round. That means it will trigger miner restart only after --watchdogrounds * 30 sec (default number of rounds is 5).
5 * 30 = 150 sec ~ 2.5 minutes. If gpu crashes and can't recover for 2.5 minutes, the miner will trigger the restart action.

min_rig_speed parameter is also affected by --watchdogrounds from now on. The 'min_rig_speed_duration' parameter default value is now 60 sec, this is the value as the above for the gpu crash watchdog, except that you can change the value of this to anything >= 30 sec.
Taking the default value of 60 seconds and 5 rounds, it is 5 * 60 = 300 sec = 5 minute, that means if for 5 minutes the 'min_rig_speed' < total hashing speed, then it will trigger miner restart.


hi, my vega 64 CN-R algo without tweaking Hashrate dropped from 2040 to 1970 moving from 187 to 188 , same config and same pool file and same coin. interesting is that my vega 56 didnt get affected. Im running low voltage settings on both cards (at the most stable possible setting)
Iamtutut
Member
**
Offline Offline

Activity: 462
Merit: 11


View Profile
May 07, 2019, 08:27:25 AM
 #6844

V1.8.8
- Reduced CPU usage up to ~50%, can be noticed on algos with small scratchpad
- User is now informed about tweaking status on the screen too, not just in log
- No more --gpureorder, device ordering by bus id is now the default/only display mode
- Added parameter --watchdogrounds , which controls after how many rounds will watchdog trigger
- min_rig_speed_duration default is 1 minute now, because of the new --watchdogrounds parameter
- Fixed a few cosmetical things on web stats


+ If not using 'old_mode', on weak CPU's the cpu usage could go boom on algos with small scratchpad (UPX2, Turtle). In this version i managed to lower the cpu usage up to ~50%.
This also brings a small hashrate increase for RX cards on UPX2 as a side effect Smiley

+ The default (and only) device ordering mode from now on is ascending by bus id, as it is in OverdriveNTool. Parameter --gpureorder is removed.

+ Because of some trouble with gpu/min_rig_speed watchdog and kernel precompilation on CN/R (V4), a new parameter --watchdogrounds was added, so you can control after how many check-rounds will the watchdog trigger.
The GPU crash watchdog has a fixed interval of 30 seconds = 1 round. That means it will trigger miner restart only after --watchdogrounds * 30 sec (default number of rounds is 5).
5 * 30 = 150 sec ~ 2.5 minutes. If gpu crashes and can't recover for 2.5 minutes, the miner will trigger the restart action.

min_rig_speed parameter is also affected by --watchdogrounds from now on. The 'min_rig_speed_duration' parameter default value is now 60 sec, this is the value as the above for the gpu crash watchdog, except that you can change the value of this to anything >= 30 sec.
Taking the default value of 60 seconds and 5 rounds, it is 5 * 60 = 300 sec = 5 minute, that means if for 5 minutes the 'min_rig_speed' < total hashing speed, then it will trigger miner restart.


I have an issue, my computer cashes because now SRB tries to use the Vega cores inside the Ryzen 2400G to mine, how could I disable the APU in your miner ?

Thanks
doktor83
Hero Member
*****
Offline Offline

Activity: 1022
Merit: 582


View Profile WWW
May 07, 2019, 08:51:11 AM
 #6845

hi, my vega 64 CN-R algo without tweaking Hashrate dropped from 2040 to 1970 moving from 187 to 188 , same config and same pool file and same coin. interesting is that my vega 56 didnt get affected. Im running low voltage settings on both cards (at the most stable possible setting)

This is interesting, yes, because on vega56 i do the testings, and nothing changed as you say.
Are you running the --resetvega parameter ? Also the same ODT as before?
Can you test it a few times, just to be sure that there is really a change in hashrate, because there shouldnt be... Smiley


I have an issue, my computer cashes because now SRB tries to use the Vega cores inside the Ryzen 2400G to mine, how could I disable the APU in your miner ?
Thanks

By now, you mean from v1.8.8 ? The ordering of the devices changed - they are now ordered by bus id so it is the same order as in ODT.
Run SRBMiner-CN.exe --listdevices in cmd and set device id's you use according to that

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

Activity: 21
Merit: 0


View Profile
May 07, 2019, 11:30:36 AM
 #6846

here are pics:

http://shrani.si/f/3s/2/8u1uY3v/187.png

http://shrani.si/f/I/7s/rW4cFxE/188.png

i dont use resetvega parameter and all settings are the same , i dont use start.bat at all, just running .exe file

now i noticed even vega 56 is affected.
doktor83
Hero Member
*****
Offline Offline

Activity: 1022
Merit: 582


View Profile WWW
May 07, 2019, 11:40:35 AM
 #6847

here are pics:

http://shrani.si/f/3s/2/8u1uY3v/187.png

http://shrani.si/f/I/7s/rW4cFxE/188.png

i dont use resetvega parameter and all settings are the same , i dont use start.bat at all, just running .exe file

now i noticed even vega 56 is affected.

Swap the intensities in 1.8.8 in gpu_conf, so :

id:1 = intensity 112
id:0 = intensity 122


You should be all back to normal Smiley

Check the post above yours

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

Activity: 21
Merit: 0


View Profile
May 07, 2019, 01:06:00 PM
 #6848

here are pics:

http://shrani.si/f/3s/2/8u1uY3v/187.png

http://shrani.si/f/I/7s/rW4cFxE/188.png

i dont use resetvega parameter and all settings are the same , i dont use start.bat at all, just running .exe file

now i noticed even vega 56 is affected.

Swap the intensities in 1.8.8 in gpu_conf, so :

id:1 = intensity 112
id:0 = intensity 122


You should be all back to normal Smiley

Check the post above yours

perfect, it works fine now, thanks Smiley
NCarter84
Jr. Member
*
Offline Offline

Activity: 96
Merit: 1


View Profile
May 07, 2019, 10:54:20 PM
 #6849

For the life of me, I cannot get 1.8.8 to run on any algo.... Whenever I hit H or S, I get nothing... Very slow response times... Compute Errors and GPU Crashes. I've tried on CN-GPU and CN-HOSP.

I'm using command line to run the miner, as I always have... Did something change here that I missed? 1.8.6 runs fine.

--ccryptonighttype hospital --cpool [Server]:[Port] --cwallet [User] --cpassword [Password] --apienable
doktor83
Hero Member
*****
Offline Offline

Activity: 1022
Merit: 582


View Profile WWW
May 08, 2019, 05:16:30 AM
 #6850

For the life of me, I cannot get 1.8.8 to run on any algo.... Whenever I hit H or S, I get nothing... Very slow response times... Compute Errors and GPU Crashes. I've tried on CN-GPU and CN-HOSP.

I'm using command line to run the miner, as I always have... Did something change here that I missed? 1.8.6 runs fine.

--ccryptonighttype hospital --cpool [Server]:[Port] --cwallet [User] --cpassword [Password] --apienable

Which gpu's and driver?

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

Activity: 2
Merit: 0


View Profile
May 08, 2019, 07:26:02 AM
 #6851

why my computer restart and hang if use tweak.......i get messages ur computer sight out Angry Angry Angry
jimmyD30
Newbie
*
Offline Offline

Activity: 34
Merit: 0


View Profile
May 08, 2019, 09:39:37 PM
 #6852

Hello, anyone know why I’m seeing this message (in light grey) after the miner been running for a while (not just right after startup)?

“Precompiling program [Bus...”
“Program finished precompiling [Bus...”

Huh

Win10 / Vega64 / v1.8.8 / Monero
doktor83
Hero Member
*****
Offline Offline

Activity: 1022
Merit: 582


View Profile WWW
May 08, 2019, 10:06:35 PM
 #6853

Hello, anyone know why I’m seeing this message (in light grey) after the miner been running for a while (not just right after startup)?

“Precompiling program [Bus...”
“Program finished precompiling [Bus...”

Huh

Win10 / Vega64 / v1.8.8 / Monero

Its all good, just thar from 1.8.8 user can see these messages, before it wasnt displayed.

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

Activity: 34
Merit: 0


View Profile
May 08, 2019, 10:39:08 PM
 #6854

Hello, anyone know why I’m seeing this message (in light grey) after the miner been running for a while (not just right after startup)?

“Precompiling program [Bus...”
“Program finished precompiling [Bus...”

Huh

Win10 / Vega64 / v1.8.8 / Monero

Its all good, just thar from 1.8.8 user can see these messages, before it wasnt displayed.

Ok, thank you. I switched pools at the same time I upgraded to v1.8.8, so wasn’t sure what was going on.
NCarter84
Jr. Member
*
Offline Offline

Activity: 96
Merit: 1


View Profile
May 09, 2019, 12:02:27 AM
 #6855

For the life of me, I cannot get 1.8.8 to run on any algo.... Whenever I hit H or S, I get nothing... Very slow response times... Compute Errors and GPU Crashes. I've tried on CN-GPU and CN-HOSP.

I'm using command line to run the miner, as I always have... Did something change here that I missed? 1.8.6 runs fine.

--ccryptonighttype hospital --cpool [Server]:[Port] --cwallet [User] --cpassword [Password] --apienable

Which gpu's and driver?

I can't remmber which exact GPU I have 580/590 in this rig.... driver is 19.4.1

Other algos worked... I know WOW did fine... but for wow I had all the jazz added to the command line with the device id, intensity level, threads.
Fredeslim
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile
May 09, 2019, 02:09:14 PM
Last edit: May 09, 2019, 02:24:26 PM by Fredeslim
 #6856

V1.8.8
- Reduced CPU usage up to ~50%, can be noticed on algos with small scratchpad
- User is now informed about tweaking status on the screen too, not just in log
- No more --gpureorder, device ordering by bus id is now the default/only display mode
- Added parameter --watchdogrounds , which controls after how many rounds will watchdog trigger
- min_rig_speed_duration default is 1 minute now, because of the new --watchdogrounds parameter
- Fixed a few cosmetical things on web stats


+ If not using 'old_mode', on weak CPU's the cpu usage could go boom on algos with small scratchpad (UPX2, Turtle). In this version i managed to lower the cpu usage up to ~50%.
This also brings a small hashrate increase for RX cards on UPX2 as a side effect Smiley

+ The default (and only) device ordering mode from noo win 10 is ascending by bus id, as it is in OverdriveNTool. Parameter --gpureorder is removed.

+ Because of some trouble with gpu/min_rig_speed watchdog and kernel precompilation on CN/R (V4), a new parameter --watchdogrounds was added, so you can control after how many check-rounds will the watchdog trigger.
The GPU crash watchdog has a fixed interval of 30 seconds = 1 round. That means it will trigger miner restart only after --watchdogrounds * 30 sec (default number of rounds is 5).
5 * 30 = 150 sec ~ 2.5 minutes. If gpu crashes and can't recover for 2.5 minutes, the miner will trigger the restart action.

min_rig_speed parameter is also affected by --watchdogrounds from now on. The 'min_rig_speed_duration' parameter default value is now 60 sec, this is the value as the above for the gpu crash watchdog, except that you can change the value of this to anything >= 30 sec.
Taking the default value of 60 seconds and 5 rounds, it is 5 * 60 = 300 sec = 5 minute, that means if for 5 minutes the 'min_rig_speed' < total hashing speed, then it will trigger miner restart.


hi, my vega 64 CN-R algo without tweaking Hashrate dropped from 2040 to 1970 moving from 187 to 188 , same config and same pool file and same coin. interesting is that my vega 56 didnt get affected. Im running low voltage settings on both cards (at the most stable possible setting)

Im running into the same issue. what did you do to fix?    the vega's start up at 2190 k/h and then within 10 minutes it drops to 1950 k/h and runs hot but stable at that hashrate. 
19.4. drivers win 10  Vega 64  1.8.8 SRBminer.
p7 1100 900  P7 1400 900
twr tool  Beta4

19   28  12  5
44 12 12 12
3 3 4
18
6 4 9
 15
8
3 2 1 3
3 2 1 3
1 18
17000
8 15
 248
8
8 10 10
160 7
8 2 8
19 5 14 1
2
247
. Anyone see something wrong w these numbers on why it's not holding 2200?

doktor83
Hero Member
*****
Offline Offline

Activity: 1022
Merit: 582


View Profile WWW
May 09, 2019, 02:17:55 PM
 #6857

V1.8.8
- Reduced CPU usage up to ~50%, can be noticed on algos with small scratchpad
- User is now informed about tweaking status on the screen too, not just in log
- No more --gpureorder, device ordering by bus id is now the default/only display mode
- Added parameter --watchdogrounds , which controls after how many rounds will watchdog trigger
- min_rig_speed_duration default is 1 minute now, because of the new --watchdogrounds parameter
- Fixed a few cosmetical things on web stats


+ If not using 'old_mode', on weak CPU's the cpu usage could go boom on algos with small scratchpad (UPX2, Turtle). In this version i managed to lower the cpu usage up to ~50%.
This also brings a small hashrate increase for RX cards on UPX2 as a side effect Smiley

+ The default (and only) device ordering mode from now on is ascending by bus id, as it is in OverdriveNTool. Parameter --gpureorder is removed.

+ Because of some trouble with gpu/min_rig_speed watchdog and kernel precompilation on CN/R (V4), a new parameter --watchdogrounds was added, so you can control after how many check-rounds will the watchdog trigger.
The GPU crash watchdog has a fixed interval of 30 seconds = 1 round. That means it will trigger miner restart only after --watchdogrounds * 30 sec (default number of rounds is 5).
5 * 30 = 150 sec ~ 2.5 minutes. If gpu crashes and can't recover for 2.5 minutes, the miner will trigger the restart action.

min_rig_speed parameter is also affected by --watchdogrounds from now on. The 'min_rig_speed_duration' parameter default value is now 60 sec, this is the value as the above for the gpu crash watchdog, except that you can change the value of this to anything >= 30 sec.
Taking the default value of 60 seconds and 5 rounds, it is 5 * 60 = 300 sec = 5 minute, that means if for 5 minutes the 'min_rig_speed' < total hashing speed, then it will trigger miner restart.


hi, my vega 64 CN-R algo without tweaking Hashrate dropped from 2040 to 1970 moving from 187 to 188 , same config and same pool file and same coin. interesting is that my vega 56 didnt get affected. Im running low voltage settings on both cards (at the most stable possible setting)

Im running into the same issue. what did you do to fix?

Read back a few posts

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

Activity: 3
Merit: 0


View Profile
May 09, 2019, 02:29:13 PM
 #6858

V1.8.8
- Reduced CPU usage up to ~50%, can be noticed on algos with small scratchpad
- User is now informed about tweaking status on the screen too, not just in log
- No more --gpureorder, device ordering by bus id is now the default/only display mode
- Added parameter --watchdogrounds , which controls after how many rounds will watchdog trigger
- min_rig_speed_duration default is 1 minute now, because of the new --watchdogrounds parameter
- Fixed a few cosmetical things on web stats


+ If not using 'old_mode', on weak CPU's the cpu usage could go boom on algos with small scratchpad (UPX2, Turtle). In this version i managed to lower the cpu usage up to ~50%.
This also brings a small hashrate increase for RX cards on UPX2 as a side effect Smiley

+ The default (and only) device ordering mode from now on is ascending by bus id, as it is in OverdriveNTool. Parameter --gpureorder is removed.

+ Because of some trouble with gpu/min_rig_speed watchdog and kernel precompilation on CN/R (V4), a new parameter --watchdogrounds was added, so you can control after how many check-rounds will the watchdog trigger.
The GPU crash watchdog has a fixed interval of 30 seconds = 1 round. That means it will trigger miner restart only after --watchdogrounds * 30 sec (default number of rounds is 5).
5 * 30 = 150 sec ~ 2.5 minutes. If gpu crashes and can't recover for 2.5 minutes, the miner will trigger the restart action.

min_rig_speed parameter is also affected by --watchdogrounds from now on. The 'min_rig_speed_duration' parameter default value is now 60 sec, this is the value as the above for the gpu crash watchdog, except that you can change the value of this to anything >= 30 sec.
Taking the default value of 60 seconds and 5 rounds, it is 5 * 60 = 300 sec = 5 minute, that means if for 5 minutes the 'min_rig_speed' < total hashing speed, then it will trigger miner restart.


hi, my vega 64 CN-R algo without tweaking Hashrate dropped from 2040 to 1970 moving from 187 to 188 , same config and same pool file and same coin. interesting is that my vega 56 didnt get affected. Im running low voltage settings on both cards (at the most stable possible setting)

Im running into the same issue. what did you do to fix?

Read back a few posts
you suggest changing the intensity?
doktor83
Hero Member
*****
Offline Offline

Activity: 1022
Merit: 582


View Profile WWW
May 09, 2019, 04:07:40 PM
 #6859

you suggest changing the intensity?

No, i suggest reading the 1.8.8 release notes Smiley

Code:
No more --gpureorder, device ordering by bus id is now the default/only display mode [NOTE: if you are using gpu_conf or --cgpuid, please run --listdevices to check if you are using the right deviceid!]

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

Activity: 3
Merit: 0


View Profile
May 09, 2019, 05:03:04 PM
 #6860

you suggest changing the intensity?

No, i suggest reading the 1.8.8 release notes Smiley

Code:
No more --gpureorder, device ordering by bus id is now the default/only display mode [NOTE: if you are using gpu_conf or --cgpuid, please run --listdevices to check if you are using the right deviceid!]
oh you mean setup the config file as this examples shows.
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"gpu_conf" :
[
   {
     "id" : 0,
     "intensity" : 112,
     "worksize" : 16,
     "threads" : 2,
     "tweak_profile" : 3
   },
   {
     "id" : 1,
     "intensity" : 112,
     "worksize" : 16,
     "threads" : 2,
     "tweak_profile" : 4
   },
   {
     "id" : 2,
     "intensity" : 111,
     "worksize" : 16,
     "threads" : 2,
     "tweak_profile" : 4
   },
   {
     "id" : 3,
     "intensity" : 110,
     "worksize" : 16,
     "threads" : 2,
     "tweak_profile" : 5
   }

]
}
Pages: « 1 ... 293 294 295 296 297 298 299 300 301 302 303 304 305 306 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 »
  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!