Author

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

jr. member
Activity: 158
Merit: 5
@doktor83   I'm pretty sure that you are aware of all these occasions, I mean with the hashdrop.
Cards with 4gb memory dont have this issue, at least to me. They reach maximum hashspeed immediately.
The problem is with the 8gb cards.
Whenever I start your miner one of them, sometimes more, can go up to maximum, others no and they stay low all the time
even after 2,3,4 hours of mining.
Next time I'm starting your miner some other cards or card do the opposite thing. It's a random situation.
To help things out, you of course the developer of a great miner to me, I found out that running GPU-Z at the time your miner runs
and passing throu all cards one by one and then exiting, voula all cards running full speed. Problem solved.
But of course this is not a solution!!!
Maybe something with the interrupts?
I'm  trying to help!


I wanted to try this, and I got 1000 h/s across the board just by firing up GPU-Z.. Awesome. Wish I had known this earlier! The GPU-Z launch was unusually slow... Very strange! Whatever it is doing to the gpu's, SRB can do too, this gives me hope.

GPU-Z is 2.8.0, and I'm ignoring the update to 2.9.0 in case it works differently, lol.

newbie
Activity: 156
Merit: 0
Hi, thanks for API, its big PLUS.

Anyway, I am not able to set port. Everytime I try it gives me parse error in config. Anyone with functionad changed port? Thanks


{
"cryptonight_type" : "heavy",
"intensity" : 0,
"double_threads" : true,
"api_enabled" : true,
"api_rig_name" : "test",
"api_port" : 19999
}

You can get the json from 127.0.0.1:19999 (open in browser to see it)

Hello this doesnt work at all. Could you please write a guide how to use these optional parameters as whenever you try to add a line to the config file it comes with an error.


Thanks

don't say it's not working, when it is. You are incapable of setting it up.
newbie
Activity: 9
Merit: 0
Hi, thanks for API, its big PLUS.

Anyway, I am not able to set port. Everytime I try it gives me parse error in config. Anyone with functionad changed port? Thanks


{
"cryptonight_type" : "heavy",
"intensity" : 0,
"double_threads" : true,
"api_enabled" : true,
"api_rig_name" : "test",
"api_port" : 19999
}

You can get the json from 127.0.0.1:19999 (open in browser to see it)

Hello this doesnt work at all. Could you please write a guide how to use these optional parameters as whenever you try to add a line to the config file it comes with an error.


Thanks
hero member
Activity: 2548
Merit: 626
WARNING

On Anorak tech site there is a thread SRBMiner, with a link that is NOT SRBMiner.
Don't download from there, only from the link on the first page of this thread!
hero member
Activity: 2548
Merit: 626
V1.5.3
- ADL Overdrive5 now shows real time GPU clocks on hashrate display
- Bus reordering should now work as expected Smiley
- Miner should now use less memory when running for longer time (more resources cleaned)
- Some fixes in GPU disable/enable while mining

Nothing BIG in this release, mostly some fixes.

+ In previous version when using --gpureorder, and then setting up gpu's in gpu_conf, the GPU ID's did not match up with --listdevicesreordered order. This should now be fixed.
jr. member
Activity: 177
Merit: 2
Hi,

I am the developer of rig-monitor (see here: https://bitcointalk.org/index.php?topic=2128602.0;all ) and got some requests to support the SRBMiner. Could someone post an example call to the management API together with the json output?

Thanks

look this :

https://bitcointalksearch.org/topic/m.36205015

Awesome. Thank you
newbie
Activity: 24
Merit: 0
@doktor83

Doktore, i need again your help. I had to reinstall Windows 10, i have done all the steps to get it again going. But, when i start SRBminer, Im getting a lot slower hash speed than earlier. Intesity is also different, its 44 now and before was 59. Thats my biggest concern; why intesity has changed.

Everything is the same, cards are the same, Bios is the same, Core and Mem speed are the same, virtually everything.

RIG is 6x 570 4gb.

I was getting 700-720 hs per card with intesity 59. Now 500-550hs with intesity 44. I cannot elevate intesiti more than 44 it crashes.

I'm suspecting that you haven't switch your drivers to compute mode!
Am I right?
newbie
Activity: 156
Merit: 0
@doktor83

Doktore, i need again your help. I had to reinstall Windows 10, i have done all the steps to get it again going. But, when i start SRBminer, Im getting a lot slower hash speed than earlier. Intesity is also different, its 44 now and before was 59. Thats my biggest concern; why intesity has changed.

Everything is the same, cards are the same, Bios is the same, Core and Mem speed are the same, virtually everything.

RIG is 6x 570 4gb.

I was getting 700-720 hs per card with intesity 59. Now 500-550hs with intesity 44. I cannot elevate intesiti more than 44 it crashes.

which version did give you more hash (700) ? also are you using the same video drivers? which algorythm?
newbie
Activity: 156
Merit: 0
Hi,

I am the developer of rig-monitor (see here: https://bitcointalk.org/index.php?topic=2128602.0;all ) and got some requests to support the SRBMiner. Could someone post an example call to the management API together with the json output?

Thanks

look this :

https://bitcointalksearch.org/topic/m.36205015
newbie
Activity: 3
Merit: 0
@doktor83

Doktore, i need again your help. I had to reinstall Windows 10, i have done all the steps to get it again going. But, when i start SRBminer, Im getting a lot slower hash speed than earlier. Intesity is also different, its 44 now and before was 59. Thats my biggest concern; why intesity has changed.

Everything is the same, cards are the same, Bios is the same, Core and Mem speed are the same, virtually everything.

RIG is 6x 570 4gb.

I was getting 700-720 hs per card with intesity 59. Now 500-550hs with intesity 44. I cannot elevate intesiti more than 44 it crashes.
jr. member
Activity: 177
Merit: 2
Hi,

I am the developer of rig-monitor (see here: https://bitcointalk.org/index.php?topic=2128602.0;all ) and got some requests to support the SRBMiner. Could someone post an example call to the management API together with the json output?

Thanks
newbie
Activity: 156
Merit: 0
@doktor83   I'm pretty sure that you are aware of all these occasions, I mean with the hashdrop.
Cards with 4gb memory dont have this issue, at least to me. They reach maximum hashspeed immediately.
The problem is with the 8gb cards.
Whenever I start your miner one of them, sometimes more, can go up to maximum, others no and they stay low all the time
even after 2,3,4 hours of mining.
Next time I'm starting your miner some other cards or card do the opposite thing. It's a random situation.
To help things out, you of course the developer of a great miner to me, I found out that running GPU-Z at the time your miner runs
and passing throu all cards one by one and then exiting, voula all cards running full speed. Problem solved.
But of course this is not a solution!!!
Maybe something with the interrupts?
I'm  trying to help!


let me try this with gpu-z maybe i get more hash  Grin
when pool send new job it is normal that hashrate drops and slowly goes up.
newbie
Activity: 24
Merit: 0
@doktor83   I'm pretty sure that you are aware of all these occasions, I mean with the hashdrop.
Cards with 4gb memory dont have this issue, at least to me. They reach maximum hashspeed immediately.
The problem is with the 8gb cards.
Whenever I start your miner one of them, sometimes more, can go up to maximum, others no and they stay low all the time
even after 2,3,4 hours of mining.
Next time I'm starting your miner some other cards or card do the opposite thing. It's a random situation.
To help things out, you of course the developer of a great miner to me, I found out that running GPU-Z at the time your miner runs
and passing throu all cards one by one and then exiting, voula all cards running full speed. Problem solved.
But of course this is not a solution!!!
Maybe something with the interrupts?
I'm  trying to help!
jr. member
Activity: 31
Merit: 5
http://prntscr.com/jgvj1n

I did not make screenshots until this moment, I tried to overcome the problem myself. I changed the riser, power supplies, added RAM, changed the priorities of the processes, intensity, voltage, timings, danced around the computer and so on. But nothing helps Sad Hash changes to the heavy algorithm for + -100 and nothing can be done about it Sad
newbie
Activity: 156
Merit: 0
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.

Same problem. When you run the miner on a heavy algorithm, a hasht is random. The maximum can go out after 5 minutes and after 6 hours. After switching to another pool or developer pool, the hash may also decrease, or it may remain the same. Videocards radeon 588, if it helps to establish the cause.

https://i.imgur.com/5nikog1.jpg

no hashrate drop on pool switch
newbie
Activity: 65
Merit: 0
I am running 5x580+ at 1240/2200 with intensity 53 and I'm getting 1k per card! Been mining for the past couple of days like that and it has been a very pleasant and stable experience! I see that from time to time one or two card have a lower hashrate, but the results at the pool are always a bit higher like 5.3kh/s!
newbie
Activity: 21
Merit: 0
Have you tried other drivers , or lowering the intensity ?
There was a bug that made random app crashes, but that was fixed, that's why i asked if a crash window appears.
Been running the Hynix cards as I usually do (1350/2000) and no issues. The Samsung card is running at 1281/1750 and has been running for 2 days 22 hours +. I think it's just on me being too aggressive with OC. Sorry about that.

I'm also noticing that after coming out of devfee it sometimes has a few hashes of [2018-05-11 22:48:07] miner_result: Duplicate share protection kicked in!

Sometimes it's a few, sometimes none, and a couple of times over the ~2 weeks using it I've noticed it ran for a good couple of hours with duplicate shares. I'm not too concerned at this point but wanted to let you know.
copper member
Activity: 62
Merit: 1
Is there any way to specify a variable (such as password) from the command line?

I use awesome miner which just recently added support for srbminer.

The only problem is it updates the pool info from the pools you setup in awesome miner, where I can’t put a password because then each of my rigs would be named the same thing. This also means I can’t manually update the config file on my rigs because awesome miner then overwrites that file with the pool info when I start the miner.

Most of the pools I use seem to use the password field for worker name. With Cast XMR I could get around this by adding a -p switch in the CLI field & then the appropriate worker name behind it. This would start the miner with a bat file that overwrote the pool info with the switches entered in the CLI field.

Is there any way to do something similar with srbminer?
newbie
Activity: 33
Merit: 0
dears
i have about 1000h/s in 1.4.6 version

this hash decrease to800 on new version with same config

any help
jr. member
Activity: 31
Merit: 5
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.

Same problem. When you run the miner on a heavy algorithm, a hasht is random. The maximum can go out after 5 minutes and after 6 hours. After switching to another pool or developer pool, the hash may also decrease, or it may remain the same. Videocards radeon 588, if it helps to establish the cause.
Jump to: