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.
Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 25. (Read 237261 times)
May 07, 2019, 06:30:36 AM
May 07, 2019, 03:51:11 AM
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...
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
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
May 07, 2019, 03:27:25 AM
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
+ 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.
- 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
+ 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
May 07, 2019, 03:07:58 AM
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
+ 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.
- 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
+ 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)
May 06, 2019, 07:12:17 PM
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?
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?
May 06, 2019, 07:12:44 AM
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
+ 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.
- 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
+ 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.
May 05, 2019, 11:59:52 AM
The latest version 1.8.7 works perfectly for upx2. CPU is not overloaded. On the contrary on the same rig running at the same time srbminer and xmrig.
Will try it out, i used the 1.8.6 version yesterday. Otherwise i will use the "old_mode" solution.
Thanks a lot:)
I tested the 1.8.7 version and the "old_mode" method and in my case none of them helped. Still the cpu is at 99% and it's throttling my gpu's. With "old_mode" : true the hashrate drops even further, around 22kh/s per card. Is there anything else i can do?
Doctor, did you found out what's causing the cpu overload?
Nah, not really possible that with old mode enabled still 99%. Yes, hashrate is little lower on some algos with it enabled because more work is done on the GPU, and almost none on the CPU.
I exactly know why it's giving more load on the cpu, because upx job round is done in less than 100ms, and a 1,2,4mb scratchpaded job is done in ~2s.
Rewriting some stuff to use intrinsics, so cpu load will be lower. But still old mode enabled should decrease your cpu load a lot.
Fixed the issue, my config was not properly structured and it didn't initialize old_mode. Now the hashrate is great and the cpu workload is around 55%.
Great job doctor.
Currently i achieved to lower the cpu usage by around 40% without the old_mode enabled, still working on it, maybe i can lower it more.
Weak CPU + lot of GPU's in rig + low difficulty can really make your CPU sweat.
I am surprised that your cpu usage is 55% with old_mode, that must be some really weak CPU in there
Checked again after a while and it's down to 30-35%. It's a Intel Celeron G3900, the most affordable one for mining. Sold my Ryzens.
As far as i read this ann, there's a lot of improvement for Vega cards but almost none for the RX series. Is there any juice left for you to squeeze out of them or should i start considering buying Vega's now when they are cheap?
May 05, 2019, 06:20:32 AM
Hi,
doktor83 is there some parameter to disable a gpu in config or in START.BAT like keyboard shortcuts but will remain after miner restarts? I have a gpu that I'd like to disable for a while.
doktor83 is there some parameter to disable a gpu in config or in START.BAT like keyboard shortcuts but will remain after miner restarts? I have a gpu that I'd like to disable for a while.
May 04, 2019, 12:04:58 PM
What driver recommend for new version 1.8.5?
Are we need to apply memory timing after that?
Are we need to apply memory timing after that?
I still think that 18.6.1 creates the fastest code, if you are compiling.
If you have Vegas you can use the built in 'tweaking profiles' or use ElioVP's tool but first disable SRB tweaking with --disabletweaking switch
I like your api remote
My Vega56 hynix reaches 2100+, so you should do much better
Hey, can you post what driver you are using and what ODN settings? I know you wrote "just pushed mem up to 940mhs and P7 to 925mV."
But can you please elaborate a little bit on how you achieved that?
Cheers
Here's a video for you :
https://youtu.be/QyJzAhdDnPg
hi dok,
in the video, how can u have so low temp with 2300 rmp
i have 4 vega 56 with stock bios and i reach like 65-70°...
what is the light mode with ODT that u mentioned in this video ?
i use 1.8.7 srbminer with 18.6.1 without softpowerplay table
JG
May 04, 2019, 10:52:18 AM
How do I enable tweaking on my VII... eavery time i start miner it sais tweaking: disabled
Run as admin, its in the readme
I did. it still shows disabled
Are you running version 1.8.7 ?
If so, look at the log file at the beginning theres more info why is tweaking disabled, if not running 1.8.7 then thats the problem
May 04, 2019, 09:58:41 AM
How do I enable tweaking on my VII... eavery time i start miner it sais tweaking: disabled
Run as admin, its in the readme
I did. it still shows disabled
May 04, 2019, 09:55:54 AM
How do I enable tweaking on my VII... eavery time i start miner it sais tweaking: disabled
Run as admin, its in the readme
May 04, 2019, 09:53:04 AM
How do I enable tweaking on my VII... eavery time i start miner it sais tweaking: disabled
May 04, 2019, 04:11:15 AM
Hi doktor83.
After upgrade on version 1.8.7 because i catch error "- Fixed a bug with pool reconnect on job timeout" on version 1.8.6
Now after miner start i always have in log mesage.
[2019-05-04 10:33:56] hashrate: GPU0: 0 H/s [T:48c][BUS:1]
[2019-05-04 10:33:56] hashrate: GPU1: 0 H/s [T:46c][BUS:4]
[2019-05-04 10:33:56] hashrate: GPU2: 0 H/s [T:41c][BUS:6]
[2019-05-04 10:33:56] hashrate: GPU3: 0 H/s [T:49c][BUS:8]
[2019-05-04 10:33:56] hashrate: GPU4: 0 H/s [T:48c][BUS:9]
[2019-05-04 10:33:56] hashrate: GPU5: 0 H/s [T:46c][BUS:10]
[2019-05-04 10:33:56] hashrate: GPU6: 0 H/s [T:43c][BUS:11]
[2019-05-04 10:33:56] hashrate: GPU7: 0 H/s [T:50c][BUS:12]
[2019-05-04 10:33:56] hashrate: GPU8: 0 H/s [T:42c][BUS:13]
[2019-05-04 10:33:56] hashrate: GPU9: 0 H/s [T:40c][BUS:14]
[2019-05-04 10:33:56] hashrate: GPU10: 0 H/s [T:45c][BUS:15]
[2019-05-04 10:33:56] hashrate: GPU11: 0 H/s [T:37c][BUS:16]
[2019-05-04 10:33:56] hashrate: GPU12: 0 H/s [T:39c][BUS:17]
[2019-05-04 10:33:56] hashrate: Total: 0 H/s
After this, the speed is normalized and working several minutes. And then message with all card is 0H/s repeat and computer restart. This behaviour on 2 my rig.
Log here
https://pastebin.com/uyxj7wmq
After upgrade on version 1.8.7 because i catch error "- Fixed a bug with pool reconnect on job timeout" on version 1.8.6
Now after miner start i always have in log mesage.
[2019-05-04 10:33:56] hashrate: GPU0: 0 H/s [T:48c][BUS:1]
[2019-05-04 10:33:56] hashrate: GPU1: 0 H/s [T:46c][BUS:4]
[2019-05-04 10:33:56] hashrate: GPU2: 0 H/s [T:41c][BUS:6]
[2019-05-04 10:33:56] hashrate: GPU3: 0 H/s [T:49c][BUS:8]
[2019-05-04 10:33:56] hashrate: GPU4: 0 H/s [T:48c][BUS:9]
[2019-05-04 10:33:56] hashrate: GPU5: 0 H/s [T:46c][BUS:10]
[2019-05-04 10:33:56] hashrate: GPU6: 0 H/s [T:43c][BUS:11]
[2019-05-04 10:33:56] hashrate: GPU7: 0 H/s [T:50c][BUS:12]
[2019-05-04 10:33:56] hashrate: GPU8: 0 H/s [T:42c][BUS:13]
[2019-05-04 10:33:56] hashrate: GPU9: 0 H/s [T:40c][BUS:14]
[2019-05-04 10:33:56] hashrate: GPU10: 0 H/s [T:45c][BUS:15]
[2019-05-04 10:33:56] hashrate: GPU11: 0 H/s [T:37c][BUS:16]
[2019-05-04 10:33:56] hashrate: GPU12: 0 H/s [T:39c][BUS:17]
[2019-05-04 10:33:56] hashrate: Total: 0 H/s
After this, the speed is normalized and working several minutes. And then message with all card is 0H/s repeat and computer restart. This behaviour on 2 my rig.
Log here
https://pastebin.com/uyxj7wmq
Happens because kernel precompilation takes a lot of time on those slow cards so watchdog triggers in the mean time. This v4 precompilation It also fu**s up the min_rig_speed.
Disable watchdog or set it to disable mode - temporary fix. I will try to do something with this..
May 04, 2019, 03:48:27 AM
Hi doktor83.
After upgrade on version 1.8.7 because i catch error "- Fixed a bug with pool reconnect on job timeout" on version 1.8.6
Now after miner start i always have in log mesage.
[2019-05-04 10:33:56] hashrate: GPU0: 0 H/s [T:48c][BUS:1]
[2019-05-04 10:33:56] hashrate: GPU1: 0 H/s [T:46c][BUS:4]
[2019-05-04 10:33:56] hashrate: GPU2: 0 H/s [T:41c][BUS:6]
[2019-05-04 10:33:56] hashrate: GPU3: 0 H/s [T:49c][BUS:8]
[2019-05-04 10:33:56] hashrate: GPU4: 0 H/s [T:48c][BUS:9]
[2019-05-04 10:33:56] hashrate: GPU5: 0 H/s [T:46c][BUS:10]
[2019-05-04 10:33:56] hashrate: GPU6: 0 H/s [T:43c][BUS:11]
[2019-05-04 10:33:56] hashrate: GPU7: 0 H/s [T:50c][BUS:12]
[2019-05-04 10:33:56] hashrate: GPU8: 0 H/s [T:42c][BUS:13]
[2019-05-04 10:33:56] hashrate: GPU9: 0 H/s [T:40c][BUS:14]
[2019-05-04 10:33:56] hashrate: GPU10: 0 H/s [T:45c][BUS:15]
[2019-05-04 10:33:56] hashrate: GPU11: 0 H/s [T:37c][BUS:16]
[2019-05-04 10:33:56] hashrate: GPU12: 0 H/s [T:39c][BUS:17]
[2019-05-04 10:33:56] hashrate: Total: 0 H/s
After this, the speed is normalized and working several minutes. And then message with all card is 0H/s repeat and computer restart. This behaviour on 2 my rig.
Log here
https://pastebin.com/uyxj7wmq
After upgrade on version 1.8.7 because i catch error "- Fixed a bug with pool reconnect on job timeout" on version 1.8.6
Now after miner start i always have in log mesage.
[2019-05-04 10:33:56] hashrate: GPU0: 0 H/s [T:48c][BUS:1]
[2019-05-04 10:33:56] hashrate: GPU1: 0 H/s [T:46c][BUS:4]
[2019-05-04 10:33:56] hashrate: GPU2: 0 H/s [T:41c][BUS:6]
[2019-05-04 10:33:56] hashrate: GPU3: 0 H/s [T:49c][BUS:8]
[2019-05-04 10:33:56] hashrate: GPU4: 0 H/s [T:48c][BUS:9]
[2019-05-04 10:33:56] hashrate: GPU5: 0 H/s [T:46c][BUS:10]
[2019-05-04 10:33:56] hashrate: GPU6: 0 H/s [T:43c][BUS:11]
[2019-05-04 10:33:56] hashrate: GPU7: 0 H/s [T:50c][BUS:12]
[2019-05-04 10:33:56] hashrate: GPU8: 0 H/s [T:42c][BUS:13]
[2019-05-04 10:33:56] hashrate: GPU9: 0 H/s [T:40c][BUS:14]
[2019-05-04 10:33:56] hashrate: GPU10: 0 H/s [T:45c][BUS:15]
[2019-05-04 10:33:56] hashrate: GPU11: 0 H/s [T:37c][BUS:16]
[2019-05-04 10:33:56] hashrate: GPU12: 0 H/s [T:39c][BUS:17]
[2019-05-04 10:33:56] hashrate: Total: 0 H/s
After this, the speed is normalized and working several minutes. And then message with all card is 0H/s repeat and computer restart. This behaviour on 2 my rig.
Log here
https://pastebin.com/uyxj7wmq
May 03, 2019, 07:31:29 AM
The latest version 1.8.7 works perfectly for upx2. CPU is not overloaded. On the contrary on the same rig running at the same time srbminer and xmrig.
Will try it out, i used the 1.8.6 version yesterday. Otherwise i will use the "old_mode" solution.
Thanks a lot:)
I tested the 1.8.7 version and the "old_mode" method and in my case none of them helped. Still the cpu is at 99% and it's throttling my gpu's. With "old_mode" : true the hashrate drops even further, around 22kh/s per card. Is there anything else i can do?
Doctor, did you found out what's causing the cpu overload?
Nah, not really possible that with old mode enabled still 99%. Yes, hashrate is little lower on some algos with it enabled because more work is done on the GPU, and almost none on the CPU.
I exactly know why it's giving more load on the cpu, because upx job round is done in less than 100ms, and a 1,2,4mb scratchpaded job is done in ~2s.
Rewriting some stuff to use intrinsics, so cpu load will be lower. But still old mode enabled should decrease your cpu load a lot.
Fixed the issue, my config was not properly structured and it didn't initialize old_mode. Now the hashrate is great and the cpu workload is around 55%.
Great job doctor.
Currently i achieved to lower the cpu usage by around 40% without the old_mode enabled, still working on it, maybe i can lower it more.
Weak CPU + lot of GPU's in rig + low difficulty can really make your CPU sweat.
I am surprised that your cpu usage is 55% with old_mode, that must be some really weak CPU in there
May 03, 2019, 07:27:23 AM
The latest version 1.8.7 works perfectly for upx2. CPU is not overloaded. On the contrary on the same rig running at the same time srbminer and xmrig.
Will try it out, i used the 1.8.6 version yesterday. Otherwise i will use the "old_mode" solution.
Thanks a lot:)
I tested the 1.8.7 version and the "old_mode" method and in my case none of them helped. Still the cpu is at 99% and it's throttling my gpu's. With "old_mode" : true the hashrate drops even further, around 22kh/s per card. Is there anything else i can do?
Doctor, did you found out what's causing the cpu overload?
Nah, not really possible that with old mode enabled still 99%. Yes, hashrate is little lower on some algos with it enabled because more work is done on the GPU, and almost none on the CPU.
I exactly know why it's giving more load on the cpu, because upx job round is done in less than 100ms, and a 1,2,4mb scratchpaded job is done in ~2s.
Rewriting some stuff to use intrinsics, so cpu load will be lower. But still old mode enabled should decrease your cpu load a lot.
Fixed the issue, my config was not properly structured and it didn't initialize old_mode. Now the hashrate is great and the cpu workload is around 55%.
Great job doctor.
May 03, 2019, 06:18:51 AM
Greeting,
I have seen this little programmer for restart, but I do not know how to set it up. I tried to start the bat fail from the zip, but nothing happens. Do you need to add one of the desired 3 tracking scenarios at the start of the mining and how?
I'm new to this, I tried to find an instruction but I did not succeed and I can not program it
I have seen this little programmer for restart, but I do not know how to set it up. I tried to start the bat fail from the zip, but nothing happens. Do you need to add one of the desired 3 tracking scenarios at the start of the mining and how?
I'm new to this, I tried to find an instruction but I did not succeed and I can not program it
May 03, 2019, 12:41:58 AM
Hi Doktor!
Noriced when using gpureorder hashrate table and found share list are not equal.
Hashrate table is correct.
2019-05-02 13:33:42] GPU1[BUS:18] result 0x2AC35BCD accepted for job[7] [195ms]
[2019-05-02 13:33:42] GPU0 : 56304 H/s [T: 64c, RPM: 3302, CC: 1408 MHz, MC: 970 MHz][BUS:3]
[2019-05-02 13:33:42] GPU1 : 61957 H/s [T: 65c, RPM: 3499, CC: 1408 MHz, MC: 1100 MHz][BUS:8]
[2019-05-02 13:33:42] GPU2 : 61483 H/s [T: 63c, RPM: 3313, CC: 1408 MHz, MC: 1095 MHz][BUS:11]
[2019-05-02 13:33:42] GPU3 : 56613 H/s [T: 57c, RPM: 3635, CC: 1408 MHz, MC: 990 MHz][BUS:18]
[2019-05-02 13:33:42] GPU4 : 59985 H/s [T: 64c, RPM: 3724, CC: 1408 MHz, MC: 1075 MHz][BUS:22]
[2019-05-02 13:33:42] GPU5 : 67075 H/s [T: 60c, RPM: 3295, CC: 1408 MHz, MC: 1075 MHz][BUS:25]
[2019-05-02 13:33:42] Total: 363417 H/s
[2019-05-02 13:33:46] GPU0[BUS:3] result 0x156FBE0E accepted for job[7] [201ms]
[2019-05-02 13:33:47] GPU5[BUS:11] result 0xD5726E9D accepted for job[7] [195ms]
[2019-05-02 13:33:47] GPU3[BUS:8] result 0x801D62F8 accepted for job[7] [194ms]
[2019-05-02 13:33:54] GPU3[BUS:8] result 0x9575D679 accepted for job[7] [200ms]
[2019-05-02 13:33:56] GPU4[BUS:25] result 0xAACF5A44 accepted for job[7] [201ms]
[2019-05-02 13:33:58] GPU1[BUS:18] result 0x401FDA9E accepted for job[7] [201ms]
[2019-05-02 13:34:08] GPU3[BUS:8] result 0x80274AAD accepted for job[7] [195ms]
[2019-05-02 13:34:10] GPU2[BUS:22] result 0x557C5F8A accepted for job[7] [194ms]
[2019-05-02 13:34:12] GPU2[BUS:22] result 0x6AD29592 accepted for job[7] [195ms]
[2019-05-02 13:34:15] GPU2[BUS:22] result 0x557EBD5A accepted for job[7] [195ms]
[2019-05-02 13:34:17] GPU5[BUS:11] result 0xD5802A03 accepted for job[7] [194ms]
[2019-05-02 13:34:17] GPU3[BUS:8] result 0x95807C9D accepted for job[7] [201ms]
[2019-05-02 13:34:34] GPU2[BUS:22] result 0x6ADC6630 accepted for job[7] [194ms]
[2019-05-02 13:34:35] GPU1[BUS:18] result 0x2AD9FDCB accepted for job[7] [194ms]
Also, parameters configured in gpu config applies to unexpected GPUs.
ver. 1.8.7
Noriced when using gpureorder hashrate table and found share list are not equal.
Hashrate table is correct.
2019-05-02 13:33:42] GPU1[BUS:18] result 0x2AC35BCD accepted for job[7] [195ms]
[2019-05-02 13:33:42] GPU0 : 56304 H/s [T: 64c, RPM: 3302, CC: 1408 MHz, MC: 970 MHz][BUS:3]
[2019-05-02 13:33:42] GPU1 : 61957 H/s [T: 65c, RPM: 3499, CC: 1408 MHz, MC: 1100 MHz][BUS:8]
[2019-05-02 13:33:42] GPU2 : 61483 H/s [T: 63c, RPM: 3313, CC: 1408 MHz, MC: 1095 MHz][BUS:11]
[2019-05-02 13:33:42] GPU3 : 56613 H/s [T: 57c, RPM: 3635, CC: 1408 MHz, MC: 990 MHz][BUS:18]
[2019-05-02 13:33:42] GPU4 : 59985 H/s [T: 64c, RPM: 3724, CC: 1408 MHz, MC: 1075 MHz][BUS:22]
[2019-05-02 13:33:42] GPU5 : 67075 H/s [T: 60c, RPM: 3295, CC: 1408 MHz, MC: 1075 MHz][BUS:25]
[2019-05-02 13:33:42] Total: 363417 H/s
[2019-05-02 13:33:46] GPU0[BUS:3] result 0x156FBE0E accepted for job[7] [201ms]
[2019-05-02 13:33:47] GPU5[BUS:11] result 0xD5726E9D accepted for job[7] [195ms]
[2019-05-02 13:33:47] GPU3[BUS:8] result 0x801D62F8 accepted for job[7] [194ms]
[2019-05-02 13:33:54] GPU3[BUS:8] result 0x9575D679 accepted for job[7] [200ms]
[2019-05-02 13:33:56] GPU4[BUS:25] result 0xAACF5A44 accepted for job[7] [201ms]
[2019-05-02 13:33:58] GPU1[BUS:18] result 0x401FDA9E accepted for job[7] [201ms]
[2019-05-02 13:34:08] GPU3[BUS:8] result 0x80274AAD accepted for job[7] [195ms]
[2019-05-02 13:34:10] GPU2[BUS:22] result 0x557C5F8A accepted for job[7] [194ms]
[2019-05-02 13:34:12] GPU2[BUS:22] result 0x6AD29592 accepted for job[7] [195ms]
[2019-05-02 13:34:15] GPU2[BUS:22] result 0x557EBD5A accepted for job[7] [195ms]
[2019-05-02 13:34:17] GPU5[BUS:11] result 0xD5802A03 accepted for job[7] [194ms]
[2019-05-02 13:34:17] GPU3[BUS:8] result 0x95807C9D accepted for job[7] [201ms]
[2019-05-02 13:34:34] GPU2[BUS:22] result 0x6ADC6630 accepted for job[7] [194ms]
[2019-05-02 13:34:35] GPU1[BUS:18] result 0x2AD9FDCB accepted for job[7] [194ms]
Also, parameters configured in gpu config applies to unexpected GPUs.
ver. 1.8.7
Going to check this out, thanks for reporting.
Bus is always the right one, i adjust the gpu number related to bus id.
May 03, 2019, 12:41:23 AM
hi Dok,
if i have ElioVP tool open in windows, SRB miner starts without tweak_profiles and i cant enable them. Vice versa if i start SRB miner i cant open ElioVP GUI tool, gives error and it crashes. Is that intended as tweak profiles are basically those suggested timings on the elioVP topic on bitcointalk?
if i have ElioVP tool open in windows, SRB miner starts without tweak_profiles and i cant enable them. Vice versa if i start SRB miner i cant open ElioVP GUI tool, gives error and it crashes. Is that intended as tweak profiles are basically those suggested timings on the elioVP topic on bitcointalk?
Intended - you even get a message about it in the log, and no, the timings are not predefined, the values are calculated based on your values found at the moment of miner start.
Jump to: