To follow up my own post about pool switching, currently, pool switching causes hashrate fluctuations (at least for Cryptonight Heavy), although technically it shouldn't be much different from getting a new job from the same pool as far as performance is concerned. The fact that there are fluctuations after switching could lead you to find the problem that causes the fluctuations to begin with, maybe it will make it easier to debug that.
Just half an hour ago SRB did an auto switch and the hasrate dropped by 500 mh/s, and it's very slowly recovering. A manual switch also causes hashrate drops.
Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 273. (Read 237280 times)
May 11, 2018, 01:51:41 PM
May 11, 2018, 08:48:39 AM
How much juice do you give the core to run it at 1525?? That's pretty high...
925mV on core. HWInfo64 reports 894-906mV fluctuating. May 11, 2018, 08:02:28 AM
How can i setup API to monitor my rig through url.
Super noob here, please provide step by step guide anyone.
btw great job Dok!, super stable miner.
thanks
Super noob here, please provide step by step guide anyone.
btw great job Dok!, super stable miner.
thanks
in your config.txt file make sure you have something like this:
Quote
"api_enabled" : true,
"api_rig_name" : "RX4708GB",
"api_port" : 4444,
of course you can change the rig name and port number.
from another workstation in your LAN you use the IP address of your rig followed by the port, so something like this:
Quote
where 192.168.1.100 is the address of your miner.
If you want to access from the internet you may have to open up the port 4444 on your router.
I dont see any line in config text file for api setup, you mean i have to type is my self at the end of text file? if you can share how to do it in context file . that will great. thanks in advance
Im using like this and its working
{
/* Type can be : normal, normalv7, lite, litev7, heavy, ipbc, artocash, alloy */
"cryptonight_type" : "heavy",
/* Intensity 0-> auto intensity, or value from 1-300 */
"intensity" : 0,
"api_enabled" : true,
"api_rig_name" : "RX570",
"api_port" : 4444,
May 11, 2018, 05:53:55 AM
How can i setup API to monitor my rig through url.
Super noob here, please provide step by step guide anyone.
btw great job Dok!, super stable miner.
thanks
Super noob here, please provide step by step guide anyone.
btw great job Dok!, super stable miner.
thanks
in your config.txt file make sure you have something like this:
Quote
"api_enabled" : true,
"api_rig_name" : "RX4708GB",
"api_port" : 4444,
of course you can change the rig name and port number.
from another workstation in your LAN you use the IP address of your rig followed by the port, so something like this:
Quote
where 192.168.1.100 is the address of your miner.
If you want to access from the internet you may have to open up the port 4444 on your router.
I dont see any line in config text file for api setup, you mean i have to type is my self at the end of text file? if you can share how to do it in context file . that will great. thanks in advance
May 11, 2018, 03:57:24 AM
I have three riggs for 5 gpu rx 550, in SRB the miner speed of each rig is 2400 mh\s, on the pool the speed of each rig is 2300 m\hs, is it normal that the srb miner shows inflated values?
May 11, 2018, 02:32:36 AM
If it can't connect to first specified pool, after 2 retries it goes to the second one, and so on.. When reached the last pool, it goes back to the first one.
Pressing 'p' will switch manually to the next pool.
Pressing 'p' will switch manually to the next pool.
Doktor, can you make "fast pool switch" not so fast? If you can add a 3-4 second delay ("switching to pool: xxxxx in 3 seconds") while allowing the user to press p again to switch to the next pool, this would allow us to switch pools without connecting and disconnecting many times if we have many pools in pools txt, so I'd be able to press p three times to switch to the 4th in list, without connecting and disconnecting the first three, and the switch would be more graceful (without having to dispose the current job, connect, fire up the next job, only to dispose it again because I'm trying to connect to the other pool). Every key press would cancel the previous timeout, and add a new 3-4 seconds timeout.
May 11, 2018, 02:31:23 AM
How much juice do you give the core to run it at 1525?? That's pretty high...
925mV on core. HWInfo64 reports 894-906mV fluctuating. May 11, 2018, 01:15:50 AM
doktor
version 1.4.9 7 did not migrate from the backup pool to the main pool. 7 hours worked on the reserve.
version 1.4.9 7 did not migrate from the backup pool to the main pool. 7 hours worked on the reserve.
where did you read that it's supposed to do that ?
transfer in manual mode?
meaning then ?
If it can't connect to first specified pool, after 2 retries it goes to the second one, and so on.. When reached the last pool, it goes back to the first one.
Pressing 'p' will switch manually to the next pool.
Code:
[2018-05-11 09:03:30] stats: Average time to find share: 9 seconds
[2018-05-11 09:03:33] miner_result: Sending user result to pool
[2018-05-11 09:03:33] json_send: {"method":"submit","params":{"id":"75597012-29ec-44a4-90e1-fe8e8f19c728","job_id":"cX8eJtwEizLbuhJJ78wlevDX9ELp","nonce":"d69e0080","result":"5815276d2b2ff4deb0bba1f97a53c9f79989352b129bf7d9e600a77e28160000"},"id":1}
[2018-05-11 09:03:33] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-05-11 09:03:33] miner_result: Pool accepted result 0x00001628
[2018-05-11 09:03:37] User initiated pool switching
[2018-05-11 09:03:37] on_reconnect: Connecting to pool.miners.pro:3335
[2018-05-11 09:03:37] Connection to pool lost. Reconnecting in 5 seconds.
[2018-05-11 09:03:38] socket_error: Ҥ欠௯ 㼯שּׂ鳼 ﰥ𠶨 櫲嬠
[2018-05-11 09:03:38] Connection to pool lost. Reconnecting in 5 seconds.
[2018-05-11 09:03:43] on_reconnect: Connecting to pool.miners.pro:3335
[2018-05-11 09:03:43] json_send: {"method":"login","params":{"login":"41hMpaW77Eh1bmT1DdDngicHcA34toXdeH9SJHd291QRPCyMscFmScw3ZZXnNYQfUtgfGMbomMWSvVuY141Nupu","pass":"VEGA1","agent":"SRBMiner Cryptonight AMD GPU miner/1.4.9"},"id":1}
[2018-05-11 09:03:43] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"267504822812043","job":{"blob":"07078ee7d4d705c82ffe75ed004307b58d39effbcf15592644f80af30be7ab318c53e037b7cafc0000000087b340cd6608e335ef0c94363c7e8140570fc3c29863de6a085a66af126f0e0e02","job_id":"778978075762279","target":"b2df0000","id":"267504822812043"},"status":"OK"}}
[2018-05-11 09:03:43] sock_ready: User logged in
[2018-05-11 09:03:43] pool_have_job: Pool difficulty: 75000
[2018-05-11 09:03:43] pool_have_job: Pool sent a new job (ID: 778978075762279)
[2018-05-11 09:03:43] on_reconnect: Connecting to pool.miners.pro:3335
[2018-05-11 09:03:43] json_send: {"method":"login","params":{"login":"41hMpaW77Eh1bmT1DdDngicHcA34toXdAAWPtwqeH9SJHd291QRPCyMscFmScw3ZZXnNYQfUtgfGMWSvVuY141Nupu","pass":"VEGA1","agent":"SRBMiner Cryptonight AMD GPU miner/1.4.9"},"id":1}
[2018-05-11 09:03:44] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"606420595408417","job":{"blob":"07078ee7d4d705c82ffe75ed004307b58d39effbcf15592644f80af30be7ab318c53e037b7cafc00000000b552e265af6bb80cc8ceb52af1ff93d3669335eb2ef3d5874fbdab245bacddd302","job_id":"463760118954815","target":"b2df0000","id":"606420595408417"},"status":"OK"}}
[2018-05-11 09:03:44] sock_ready: User logged in
[2018-05-11 09:03:44] pool_have_job: Pool difficulty: 75000
[2018-05-11 09:03:44] pool_have_job: Pool sent a new job (ID: 463760118954815)
[2018-05-11 09:03:49] stats: Mining time: 0 days, 0 hours, 0 minutes, 58 seconds
[2018-05-11 09:03:49] stats: Pool: pool.miners.pro:3335
[2018-05-11 09:03:49] stats: Connected since: 2018-05-11 09:03:44
[2018-05-11 09:03:49] stats: GPU Target Temperature: 75
[2018-05-11 09:03:49] stats: Accepted/Total shares: 5/5
[2018-05-11 09:03:58] miner_result: Sending user result to pool
[2018-05-11 09:03:58] json_send: {"method":"submit","params":{"id":"606420595408417","job_id":"463760118954815","nonce":"a12d0040","result":"6d154e3dc89384933bdc50547d823dcaed30824eead6f8e343f9222cf18c0000"},"id":1}
[2018-05-11 09:03:58] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"OK"}}
[2018-05-11 09:03:58] miner_result: Pool accepted result 0x00008CF1
[2018-05-11 09:04:15] User initiated pool switching
[2018-05-11 09:04:15] on_reconnect: Connecting to pool.monero.hashvault.pro:7777
[2018-05-11 09:04:15] Connection to pool lost. Reconnecting in 5 seconds.
[2018-05-11 09:04:16] socket_error: Ҥ欠௯ 㼯שּׂ鳼 ﰥ𠶨 櫲嬠
[2018-05-11 09:04:16] Connection to pool lost. Reconnecting in 5 seconds.
[2018-05-11 09:04:21] on_reconnect: Connecting to pool.monero.hashvault.pro:7777
[2018-05-11 09:04:21] on_reconnect: Connecting to pool.monero.hashvault.pro:7777
[2018-05-11 09:04:21] json_send: {"method":"login","params":{"login":"41nujo2JithhQHT4yQMDaf3iSJtuHfkrodNXwvki7dxCXqiqBQTsy6i4TRkrkARAFAaoCsUs5DK5xoC34PFw7D6ExWMbp+100000","pass":"VEGA1","agent":"SRBMiner Cryptonight AMD GPU miner/1.4.9"},"id":1}
[2018-05-11 09:04:21] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"f275ada7-2f33-4f63-85cd-56da47c9d452","job":{"blob":"07078ee7d4d705c82ffe75ed004307b58d39effbcf15592644f80af30be7ab318c53e037b7cafc000000008e279d80fcbb75c7bc75d71171592f6092409919f1d712096c180fdc5891dbf902","job_id":"QUirVbuOnv+u3a+py3d7tFrrkBuZ","target":"c5a70000","id":"f275ada7-2f33-4f63-85cd-56da47c9d452","algo":"cn","variant":1},"extensions":["algo"],"status":"OK"}}
[2018-05-11 09:04:21] sock_ready: User logged in
[2018-05-11 09:04:21] json_send: {"method":"login","params":{"login":"41nujo2JithhQHT4yQMDaf3iSJtuHfkrodNXwvki7dxCXqiqBQTsy6i4TRkrkGARAFAaoV5DK5xoC34PFw7D6ExWMbp+100000","pass":"VEGA1","agent":"SRBMiner Cryptonight AMD GPU miner/1.4.9"},"id":1}
[2018-05-11 09:04:21] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"id":"521f3445-cc02-4c30-9653-4208b0934ab9","job":{"blob":"07078ee7d4d705c82ffe75ed004307b58d39effbcf15592644f80af30be7ab318c53e037b7cafc0000000034888e2495328b7513c8420a1662725d93bf5617c0378328648b0de0b564897c02","job_id":"y3CyyumqvTuJAHmw7ydcSeEB8XR2","target":"c5a70000","id":"521f3445-cc02-4c30-9653-4208b0934ab9","algo":"cn","variant":1},"extensions":["algo"],"status":"OK"}}
[2018-05-11 09:04:21] sock_ready: User logged in
[2018-05-11 09:04:21] pool_have_job: Pool difficulty: 100001
[2018-05-11 09:04:21] pool_have_job: Pool sent a new job (ID: QUirVbuOnv+u3a+py3d7tFrrkBuZ)
[2018-05-11 09:04:21] pool_have_job: Pool sent a new job (ID: y3CyyumqvTuJAHmw7ydcSeEB8XR2)
socket_error ?
May 11, 2018, 01:07:03 AM
doktor
version 1.4.9 7 did not migrate from the backup pool to the main pool. 7 hours worked on the reserve.
version 1.4.9 7 did not migrate from the backup pool to the main pool. 7 hours worked on the reserve.
where did you read that it's supposed to do that ?
transfer in manual mode?
meaning then ?
If it can't connect to first specified pool, after 2 retries it goes to the second one, and so on.. When reached the last pool, it goes back to the first one.
Pressing 'p' will switch manually to the next pool.
May 11, 2018, 12:59:20 AM
doktor
version 1.4.9 7 did not migrate from the backup pool to the main pool. 7 hours worked on the reserve.
version 1.4.9 7 did not migrate from the backup pool to the main pool. 7 hours worked on the reserve.
where did you read that it's supposed to do that ?
transfer in manual mode?
meaning then ?
May 11, 2018, 12:56:41 AM
doktor
version 1.4.9 7 did not migrate from the backup pool to the main pool. 7 hours worked on the reserve.
version 1.4.9 7 did not migrate from the backup pool to the main pool. 7 hours worked on the reserve.
where did you read that it's supposed to do that ?
May 11, 2018, 12:16:33 AM
doktor
version 1.4.9 7 did not migrate from the backup pool to the main pool. 7 hours worked on the reserve.
version 1.4.9 7 did not migrate from the backup pool to the main pool. 7 hours worked on the reserve.
May 10, 2018, 09:26:24 PM
Just started mining heavy algo for the first time on one of my rigs (RX 570).
Used to have ~950h/s per card on normalv7, now ~725h/s on heavy. Can somebody confirm this is about right? I set intensity to 0 to start with (had it set at 56 on normalv7 but that crashed almost instantly on heavy - what approximate value should I set it at in heavy mode? Half that?).
Heavy doubles the thread size, so you can:Used to have ~950h/s per card on normalv7, now ~725h/s on heavy. Can somebody confirm this is about right? I set intensity to 0 to start with (had it set at 56 on normalv7 but that crashed almost instantly on heavy - what approximate value should I set it at in heavy mode? Half that?).
- halve the intensity and keep 2 threads
or
- Keep intensity (or increase a little) and disable 2 threads
Here the best results are at 60 intensity and just one thread. At 1230/2020 I can reach 775~785H/s in my RX570 4GB 4GB Elpida.
How much voltage on memory and on core please?
May 10, 2018, 06:15:56 PM
Try Claymore 11.3 with -h 460 and -dmem 1.
As i know new algorithm has lower hashrate on the same videocards, so it is weird that you have this result
May 10, 2018, 05:36:03 PM
How much juice do you give the core to run it at 1525?? That's pretty high...
925mV on core. HWInfo64 reports 894-906mV fluctuating. May 10, 2018, 05:27:18 PM
Just started mining heavy algo for the first time on one of my rigs (RX 570).
Used to have ~950h/s per card on normalv7, now ~725h/s on heavy. Can somebody confirm this is about right? I set intensity to 0 to start with (had it set at 56 on normalv7 but that crashed almost instantly on heavy - what approximate value should I set it at in heavy mode? Half that?).
Used to have ~950h/s per card on normalv7, now ~725h/s on heavy. Can somebody confirm this is about right? I set intensity to 0 to start with (had it set at 56 on normalv7 but that crashed almost instantly on heavy - what approximate value should I set it at in heavy mode? Half that?).
4gb cards? if so 20-25% reduction in hashrates. It's 59 for me, single thread. CN-Heavy doesn't like dual thread for 4gb cards (performance is lower than single thread)
8gb cards actually got a boost in hashrate by 5-10%
Would I keep double threads and half intensity for Vega64 cards?
You can keep double threads for Vega. 14xx is the hashrate I get. Intensity 56, dual threads. Although Cryptonight-Heavy is weird. See my previous post 1-2 pages back. I did get 1560 H/s on similar clocks/settings. Can't keep it sustained though. perhaps it's just a bogus hashrate display
RX570 8gb + Vega 56 8gb.
Below is mine for 6xRX580, GPU0 is Hynix rest are Elpidas. (4gb cards)
hello,
used Cast_XMR for heavy and "only" got 680hs with my RX 570(stable last 24h)
now i tried SRBMiner and got 750hs with 60 intensity, 8 worksize and 1 Thread - but the miner crashed and card resets after 5 minutes. HWInfo dont show Meory errors or anything else - any idea whats the problem?
used Cast_XMR for heavy and "only" got 680hs with my RX 570(stable last 24h)
now i tried SRBMiner and got 750hs with 60 intensity, 8 worksize and 1 Thread - but the miner crashed and card resets after 5 minutes. HWInfo dont show Meory errors or anything else - any idea whats the problem?
Reduce intensity to 59 and mem clock. I observed GPU settings that might work fine with CN-V7 might not play well with CN-Heavy.
May 10, 2018, 03:58:55 PM
Doktor, what can you say about the random hash rate?
SRB does get the best hashrate, and I even managed 1000 mh/s for all my cards, in one run, but what happens is this:
e.g. Sometimes, GPU0 gives 920h/s, sometimes the same gpu, just by restarting miner, gives 1000 mh/s, but then some other card, e.g. GPU5 which gave 1000mh/s, may (or may not) do 920-940 mh/s.. The total may vary +/- 800 mh/s, and it doesn't change much during the run (it gets stabilized in a few minutes, stays that way)
Sometimes a gpu gets 0 hashrate, I restart, it fails on compilation phase. I use XMR-Stak to get it working back, switch back to SRB and it begins working (SRB cannot get it unstuck however many restarts!)
SRB does get the best hashrate, and I even managed 1000 mh/s for all my cards, in one run, but what happens is this:
e.g. Sometimes, GPU0 gives 920h/s, sometimes the same gpu, just by restarting miner, gives 1000 mh/s, but then some other card, e.g. GPU5 which gave 1000mh/s, may (or may not) do 920-940 mh/s.. The total may vary +/- 800 mh/s, and it doesn't change much during the run (it gets stabilized in a few minutes, stays that way)
Sometimes a gpu gets 0 hashrate, I restart, it fails on compilation phase. I use XMR-Stak to get it working back, switch back to SRB and it begins working (SRB cannot get it unstuck however many restarts!)
this is true only for heavy algo, and i haven't look into it yet. What error do you get when the kernel compile fails? And what do you mean by using xmr stak to get it back working?
For example, I start a run, and 1 or 2 gpu's produce 0 hashes, and this is warned in the console. I quit without waiting.. Start again, the first gpu which produced 0 hashrate cannot get past the compile, it just hangs, no errors. When this happens, the gpu never gets past the compile phase with SRB. I then run XMR-Stak, GPU is working, and I go back to SRB, the GPU passes compile and starts working, sort of like XMR-Stak gets it unstuck, maybe it does something different when initializing GPU's.
try lowering the intensity by 2-3 when it gets stuck, and try running it like that. But the problem is interesting anyways. Can you send me a log containing all of this?
Sure:
Log For Doktor
You can search for "hesido" where I added comments. There's not much meat though, it just hangs. Here you won't see retrying and stucking again becasue I either restarted after XMR-Stak or rebooted. You can also see the wildly varying hashrates for the same gpu's.
I Have Same issue sometimes , but i disable enable this gpu and start miner again , it happens on first launch of srb after restarting system , but after this i dont have this issue
May 10, 2018, 03:04:54 PM
Try Claymore 11.3 with -h 460 and -dmem 1.
As i know new algorithm has lower hashrate on the same videocards, so it is weird that you have this result
May 10, 2018, 01:25:02 PM
Anybody has radeon 270x? What is best value for intensity?
I have 270X 4Gb. On SRB old version (1.4.x) I can get max speed. On latest versions speed slower 5-10%.Best speed I have got on my 270X 4Gb is on Claymore 11.3 fee-free with -h460 and -dmem 1 options. It's gives speed higher than max speed that SRB gives on 5-10 h/s.
and what about ggs? thats your favorite miner no?
For 270X card I use Claymore 11.3.
I didn't have favorites. Just use miner that gives me max speed.
Anybody has radeon 270x? What is best value for intensity?
I have 270X 4Gb. On SRB old version (1.4.x) I can get max speed. On latest versions speed slower 5-10%.Best speed I have got on my 270X 4Gb is on Claymore 11.3 fee-free with -h460 and -dmem 1 options. It's gives speed higher than max speed that SRB gives on 5-10 h/s.
Mine is 370, and 355 on claymore 11.3.
But on old cryptonight protocol i had about 437 h/s without any overclocking.
P.S. 2GB version
cryptonightv7 must give the same speed as old cryptonight +/- 5 h/s. You must find right intensity.
Try Claymore 11.3 with -h 460 and -dmem 1.
May 10, 2018, 12:03:00 PM
Just started mining heavy algo for the first time on one of my rigs (RX 570).
Used to have ~950h/s per card on normalv7, now ~725h/s on heavy. Can somebody confirm this is about right? I set intensity to 0 to start with (had it set at 56 on normalv7 but that crashed almost instantly on heavy - what approximate value should I set it at in heavy mode? Half that?).
Used to have ~950h/s per card on normalv7, now ~725h/s on heavy. Can somebody confirm this is about right? I set intensity to 0 to start with (had it set at 56 on normalv7 but that crashed almost instantly on heavy - what approximate value should I set it at in heavy mode? Half that?).
4gb cards? if so 20-25% reduction in hashrates. It's 59 for me, single thread. CN-Heavy doesn't like dual thread for 4gb cards (performance is lower than single thread)
8gb cards actually got a boost in hashrate by 5-10%
Would I keep double threads and half intensity for Vega64 cards?
You can keep double threads for Vega. 14xx is the hashrate I get. Intensity 56, dual threads. Although Cryptonight-Heavy is weird. See my previous post 1-2 pages back. I did get 1560 H/s on similar clocks/settings. Can't keep it sustained though. perhaps it's just a bogus hashrate display
RX570 8gb + Vega 56 8gb.
Below is mine for 6xRX580, GPU0 is Hynix rest are Elpidas. (4gb cards)
hello,
used Cast_XMR for heavy and "only" got 680hs with my RX 570(stable last 24h)
now i tried SRBMiner and got 750hs with 60 intensity, 8 worksize and 1 Thread - but the miner crashed and card resets after 5 minutes. HWInfo dont show Meory errors or anything else - any idea whats the problem?
used Cast_XMR for heavy and "only" got 680hs with my RX 570(stable last 24h)
now i tried SRBMiner and got 750hs with 60 intensity, 8 worksize and 1 Thread - but the miner crashed and card resets after 5 minutes. HWInfo dont show Meory errors or anything else - any idea whats the problem?
Reduce intensity to 59 and mem clock. I observed GPU settings that might work fine with CN-V7 might not play well with CN-Heavy.
Jump to: