Bitcoin Forum
April 30, 2024, 10:43:10 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 [53] 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 ... 164 »
1041  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 16, 2018, 09:23:57 AM
580/8 srbminer 1.7.0 1230/2100 (880mv) - 1135-1140h/s
"gpu_conf" :
[
   { "id" : 0, "intensity" : 58, "worksize" : 8, "fragments" : 1, "threads" : 2},
   { "id" : 1, "intensity" : 58, "worksize" : 8, "fragments" : 1, "threads" : 2},
   { "id" : 2, "intensity" : 58, "worksize" : 8, "fragments" : 1, "threads" : 2},
   { "id" : 3, "intensity" : 58, "worksize" : 8, "fragments" : 1, "threads" : 2},
   { "id" : 4, "intensity" : 58, "worksize" : 8, "fragments" : 1, "threads" : 2},
   { "id" : 5, "intensity" : 58, "worksize" : 8, "fragments" : 1, "threads" : 2},
]
}

So after setting the fragments in gpu_conf, you get higher hashrate than on 1.6.7 ?
1042  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 15, 2018, 04:28:48 PM

Same here epic failure  for r9 280 Dual-x  (compute errors, 0 h/s, red everywhere, no need to ask drivers, oc, compute, lock memory pages all ok! i have a Vega 56 rig too doing better but still 100w more for V8 than V7 and 100h/s less...
)
i dont want to be disrespectful with your awesome work and support (really) but:

As you ask on your 1.7.0 release post: NO! WE DONT WANT USELESS EXTRA TUNING GADGETS to mine 10h/s more but screwing up 50% of our gpu's and all pasts benchmarks.

I mean of course if it's usefull, like very usefull i'm ok but:
i MINE : CryptoNight ,CryptoNightAlloy, CryptoNightArto, CryptoNightB2N, CryptoNightFast   ,CryptoNightHaven ,CryptoNightHeavy   ,CryptoNightItalo , CryptoNightLiteV7, CryptoNightSaber, CryptoNightStelliteV4,   CryptoNightV7, CryptoNightV8 with a profitability switcher that i coded
if i need to bench (x8)²x508x48 possible settings/cards/algo on every release i'll rather to stop using a tool that will makes me spend more time to bench and set up than to mine ...

SO PLEASE YOUR PROGRAM IS GREAT!= new goodies or i dont know how do you call this (fragments, bralock, aes) and all these ****** settings which makes me pull my hairs off for 1 week to earn what: 10h/s or 0========E X I T !


very easy fix, use old version that good on r9 280 und problem solved

my vega & rx rigs thank you for 1.7.0 doktor!

I use minerstat switcher for this rig (this is my PC in fact...) which cannot reach old api requirements (which change on every release too)....

API in SRB changed on every release?

Hello !
Is it possible to set up a forcerestart windows 10 when the miner crash? Every miner crash I lost remote access (teamviewer, google remote) to the mining RIG and I need to acces physically to the rig for shutdown.

Well if windows hangs then you can't do anything else but restart the machine physically.
Maybe you should lower a little bit your overclocking settings so it won't hang ?

I tried but my Vega ( 56 reference blower) are already running at low speed 1395 / 925 . Miner crash every couples of days  (5-6) , there is only 1-2 compute error per card after one week running. I don't know how to identify the bad one.


No i'm wrong (fast answer... i was deleting my post.sorry..) just minerstat default value didn't match with the new/old 1.6.8
"(- API parameters now have to be set in start.bat (--apienable, --apiport, --apirigname) , removed them from config.txt)"

I use 1.6.8 for r9 280 dx, i need to check when minerstat auto-update miners to force it to roll back/downgrade....it's ok for a 10€/month miner not for my 3x6 Vega 56 (Sapphire Pulse 56 nano PCB which are amazing...btw!)

1.7.0 for my 56s running ok with default settings, it seems to draw less power than 1.6.9 and prev'
<=1.6.9 :220w of the wall OC 1508/950 Cv8 2000H/s
1.7.0 :190w; gpu-z says 130w/150w= 2000H/s Cv8. (Cv7= 2100H/S)

This my settings if some people want to share there values for general improvement this is mine: (suggestion; add a page on SRBMiner site to compare best settings/card/model/SRBMiner Version, looking for a precise information on this forum is sometimes ...tricky! exemple: XMRStak - https://www.xmrstak.com/category/xmr-stak-amd-configurations/amd-vega-56/)

- Windows 10 Business 1809 November - Lock pages - NordVpn
- u/hellae .Reg PPT
- Windows Optimizer https://github.com/hellzerg/optimizer/releases
- Sapphire RX Vega 56 Pulse Stock Bios HBM2 off @ P7:1508/1000, P3: 950/905, Samsung Memory, 160w-180w/card (of the wall)
- SRBMiner 1.7.0 multi pool/algos
- MinerStat Profit Switcher Windows

Hashrates (Stock config files: I=0 T=2):

heavy/haven : 1750 H/s
bittubev2 (saber) : 1650 H/s
italo : 1700 H/s
v7/stellitev7 : 2060 H/s
v8: 1950 H/s
fast : 3950 H/s
lite/litev7 : 4450 H/s
alloy : 1050 H/s
artocash : 1610 H/s
marketcash : 2710 H/s

questions? comments?! ,  improvements?! ,  your settings (I, W, F, A)....

@ Doktor83: i apologize, i have been disrespectful with your work (even if i didn't want to be)! sorry again. you do an awesome job with this tool which is my favorite since quite a while...keep going dude!

There is a DOC maintained by users here : https://docs.google.com/spreadsheets/d/1pH326fwnYWC5Jef2FdF4KnJ4CLj0cwDDtGjrlgekk1A/edit#gid=514064850 it contains settings for various cards.
It can be found on the first page , under the Tips section.

No problem i got used to angry people  Grin
What is really making me confused sometimes is that some complain on XY gpu new version is a lot worse, while others for that same XY gpu say the new version is a lot better. Smiley

I know something got 'lost' for older cards on the road, in the next version i will again add a 'useless extra tuning gadget', which will maybe bring back what got lost for those older cards.
1043  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 15, 2018, 02:39:55 PM

Same here epic failure  for r9 280 Dual-x  (compute errors, 0 h/s, red everywhere, no need to ask drivers, oc, compute, lock memory pages all ok! i have a Vega 56 rig too doing better but still 100w more for V8 than V7 and 100h/s less...
)
i dont want to be disrespectful with your awesome work and support (really) but:

As you ask on your 1.7.0 release post: NO! WE DONT WANT USELESS EXTRA TUNING GADGETS to mine 10h/s more but screwing up 50% of our gpu's and all pasts benchmarks.

I mean of course if it's usefull, like very usefull i'm ok but:
i MINE : CryptoNight ,CryptoNightAlloy, CryptoNightArto, CryptoNightB2N, CryptoNightFast   ,CryptoNightHaven ,CryptoNightHeavy   ,CryptoNightItalo , CryptoNightLiteV7, CryptoNightSaber, CryptoNightStelliteV4,   CryptoNightV7, CryptoNightV8 with a profitability switcher that i coded
if i need to bench (x8)²x508x48 possible settings/cards/algo on every release i'll rather to stop using a tool that will makes me spend more time to bench and set up than to mine ...

SO PLEASE YOUR PROGRAM IS GREAT!= new goodies or i dont know how do you call this (fragments, bralock, aes) and all these ****** settings which makes me pull my hairs off for 1 week to earn what: 10h/s or 0========E X I T !


very easy fix, use old version that good on r9 280 und problem solved

my vega & rx rigs thank you for 1.7.0 doktor!

I use minerstat switcher for this rig (this is my PC in fact...) which cannot reach old api requirements (which change on every release too)....

API in SRB changed on every release?

Hello !
Is it possible to set up a forcerestart windows 10 when the miner crash? Every miner crash I lost remote access (teamviewer, google remote) to the mining RIG and I need to acces physically to the rig for shutdown.

Well if windows hangs then you can't do anything else but restart the machine physically.
Maybe you should lower a little bit your overclocking settings so it won't hang ?
1044  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 15, 2018, 02:13:50 PM

Same here epic failure  for r9 280 Dual-x  (compute errors, 0 h/s, red everywhere, no need to ask drivers, oc, compute, lock memory pages all ok! i have a Vega 56 rig too doing better but still 100w more for V8 than V7 and 100h/s less...
)
i dont want to be disrespectful with your awesome work and support (really) but:

As you ask on your 1.7.0 release post: NO! WE DONT WANT USELESS EXTRA TUNING GADGETS to mine 10h/s more but screwing up 50% of our gpu's and all pasts benchmarks.

I mean of course if it's usefull, like very usefull i'm ok but:
i MINE : CryptoNight ,CryptoNightAlloy, CryptoNightArto, CryptoNightB2N, CryptoNightFast   ,CryptoNightHaven ,CryptoNightHeavy   ,CryptoNightItalo , CryptoNightLiteV7, CryptoNightSaber, CryptoNightStelliteV4,   CryptoNightV7, CryptoNightV8 with a profitability switcher that i coded
if i need to bench (x8)²x508x48 possible settings/cards/algo on every release i'll rather to stop using a tool that will makes me spend more time to bench and set up than to mine ...

SO PLEASE YOUR PROGRAM IS GREAT!= new goodies or i dont know how do you call this (fragments, bralock, aes) and all these ****** settings which makes me pull my hairs off for 1 week to earn what: 10h/s or 0========E X I T !


very easy fix, use old version that good on r9 280 und problem solved

my vega & rx rigs thank you for 1.7.0 doktor!

I use minerstat switcher for this rig (this is my PC in fact...) which cannot reach old api requirements (which change on every release too)....

API in SRB changed on every release?
1045  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 15, 2018, 01:48:01 PM

which algo is best for you on 1.68 , and what gpu's ?

Right now I am mining haven with 1.68 using gpu:

1. Asus rog  rx 580 8gb ==> 1.7.0 lower hashrate (1010 vs 1050)
2. Sapphire Nitro/Pulse 570/580 8GB ==> 1.7.0 lower hashrate (8xx-9xx vs 9xx-10xx)
3. Sapphire Nitro 470/480 4GB ==> not tested, I think the result will be the same
4. Asus rog rx 480 8gb ==> not tested
5. MSI Gaming 470 4GB ==> not tested
6. XFX 470 4GB ==> not tested

what I like on v1.7.0 is a lot stable compared to 1.6.8, but the hashrate is lower.

Thanks doctor


4gb ellesmere cards are better on 170, only the 8Gb cards do that magical hashrate game.
On previous versions you had sometimes to wait for a few hours to get all cards hashing at for example 1100hs, and even then sometimes they never reached to that maximum.
For some the gpu-z tricks worked, for some not. I managed to make that hashrate 90% stable on 170, so no need to start the miner X times to maybe reach a maximum hashrate, and no need for gpu-z tricks.
So you get a little lower hashing speed, but it is much more stable.
1046  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 15, 2018, 09:32:33 AM
Hi doctor,

since v1.68 is  the best for my rig, will you in the next release (1.71 maybe) to add an argument to run SRBminer to choose optimization 1 (1.68) , 2 (1.69), 3 (1.7.0), so everybody happy ... can use all program improvements you have made and mining new algos? OR better if you can make combined optimization from 1.68 1.69 1.70 with the best result for all   Smiley Smiley

thanks

which algo is best for you on 1.68 , and what gpu's ?
1047  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 15, 2018, 06:39:15 AM

Same here epic failure  for r9 280 Dual-x  (compute errors, 0 h/s, red everywhere, no need to ask drivers, oc, compute, lock memory pages all ok! i have a Vega 56 rig too doing better but still 100w more for V8 than V7 and 100h/s less...
)
i dont want to be disrespectful with your awesome work and support (really) but:

As you ask on your 1.7.0 release post: NO! WE DONT WANT USELESS EXTRA TUNING GADGETS to mine 10h/s more but screwing up 50% of our gpu's and all pasts benchmarks.

I mean of course if it's usefull, like very usefull i'm ok but:
i MINE : CryptoNight ,CryptoNightAlloy, CryptoNightArto, CryptoNightB2N, CryptoNightFast   ,CryptoNightHaven ,CryptoNightHeavy   ,CryptoNightItalo , CryptoNightLiteV7, CryptoNightSaber, CryptoNightStelliteV4,   CryptoNightV7, CryptoNightV8 with a profitability switcher that i coded
if i need to bench (x8)²x508x48 possible settings/cards/algo on every release i'll rather to stop using a tool that will makes me spend more time to bench and set up than to mine ...

SO PLEASE YOUR PROGRAM IS GREAT!= new goodies or i dont know how do you call this (fragments, bralock, aes) and all these ****** settings which makes me pull my hairs off for 1 week to earn what: 10h/s or 0========E X I T !


very easy fix, use old version that good on r9 280 und problem solved

my vega & rx rigs thank you for 1.7.0 doktor!

Why do i always have to repeat myself : i don't have every amd card to test against, so yes, it may happen that an optimisation for one is not working out for the other, especially this is related to older cards.
The extra gadgets don't take off from your hashrate, but they can gain you if 10hs then 10hs, but they won't screw 50% of gpu's as you say.

I agree with dingdongtobias, if there is an older version that works good for you, then why not use that instead?
Further optimisations will be all towards newer cards in the future, those i got and can test with.
1048  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 14, 2018, 06:47:40 PM
I could use some advice! My hashrate for RX 570 4GB cards on windows 10 64 bit has dropped to about 300 H/s mining monero.

I was getting over 700 H/s on these 2 days ago. I woke up to windows restarted and reverted back to 17 Relive drivers that I used to have installed for mining a few months ago. Now all the cards are only mining at 300 and I get warnings that they are dropping to 0 at some points.
I reinstalled with a clean install of 18.6.1 drivers and still have the same issue. I tried again with 18.11.1 and only 1 card, same issue. I'm using 1x risers and have backed off of any clock changes to stock, same problems.
I have an EVGA 1000 watt GQ PSU and only installed Comodo security on this computer. Other than trying to reinstall windows, I'm not sure what else could be the issue. Any tips would be appreciated! Thanks!

My first thought is to ask if you put each GPU in Compute Mode in Radeon Settings?

Thanks! I assumed because the setcompute command completed without error it must have been enabled, but in the Radeon settings it wasn't.
Looks like my rig is pooched in some way which caused the driver to completely crash.

--setcomputemode has to be run as admin
1049  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 13, 2018, 07:56:58 PM
Ayone have problems with benchmarking ? (120 secont timeout),,, ??

[2018-11-13 20:52:40] Releasing GPU resources...
[2018-11-13 20:52:40] This can take a while, please be patient
[2018-11-13 20:52:41] Device BUS_ID[4] thread0 resources released
[2018-11-13 20:52:41] Device BUS_ID[4] thread1 resources released
[2018-11-13 20:52:41] Device BUS_ID[5] thread2 resources released
[2018-11-13 20:52:41] Device BUS_ID[5] thread3 resources released
[2018-11-13 20:52:41] Device BUS_ID[3] thread4 resources released
[2018-11-13 20:52:41] Device BUS_ID[3] thread5 resources released
[2018-11-13 20:52:41] Loading heavy kernel for DEVICE BUS_ID[4] ...
[2018-11-13 20:52:41] Loading heavy kernel for DEVICE BUS_ID[4] ...
[2018-11-13 20:52:42] Loading heavy kernel for DEVICE BUS_ID[5] ...
[2018-11-13 20:52:42] Loading heavy kernel for DEVICE BUS_ID[5] ...
[2018-11-13 20:52:42] Loading heavy kernel for DEVICE BUS_ID[3] ...
[2018-11-13 20:52:42] Loading heavy kernel for DEVICE BUS_ID[3] ...
[2018-11-13 20:52:42] ADL initialised successfully!
[2018-11-13 20:52:42] Benchmarking algo 'heavy', please wait
[2018-11-13 20:52:55] Speed:    3044.0 H/S
[2018-11-13 20:53:08] Speed:    3136.0 H/S
[2018-11-13 20:53:21] Speed:    3083.0 H/S
[2018-11-13 20:53:34] Speed:    3132.0 H/S

Startup monitor detected that GPU's could not be initialised in 120 seconds!
Doing a forced restart...

Restarting miner...Uno momento

yup, it is a bug, it's going to be fixed
1050  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 12, 2018, 07:08:33 PM
to the question what is it in 1.7.0
pitcairn r7 370 2 gb 1000/1400 - gpu / mem algorithm stelite v4
srb 1.6.9 intensity: 30, "worksize": 8, "threads": 2
driver 18.6.1 windows 10 pro --- 485h / s
There are pitching errors on pitcairn, lower intensity changes, lower frequencies of gpu, memory do not allow getting rid of errors, also tried different versions of the drivers, the result is approximately the same, the latest version without errors is 1.6.4 on it and stopped
in the new version 1.7.0 a catastrophic hash rate drop was added,
srb 1.7.0 intensity: 30, "worksize": 8, "threads": 2 --- 226h / s
tried fragment, aes --- minor changes in the results

On v8 algorithm I use two different miners
on rx460 - srb 1.6.9
on pitcairn r7 370 2 gb alternative for old gpu

the question is which algo was without errors on 1.6.4, and on which algo you have the catastrophic hash drop?
because you talk about stellite which is a v7 variant, then you say you use 2 miners for v8.
1051  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 12, 2018, 04:58:25 PM
Bro, can you tell me you settings about RX560 - v1.6.9 = 613H/s, my cards only 550H/s
Oтвeт нa твoй вoпpoc бyдeт нижe...
See answer for your question below...

Okay, so some of you said that the hashrate on Rx560 4g is lower on 1.7.0 vs 1.6.9 on heavy algos (said Haven) - HERE
I took some time and made some tests :

[overquoting skipped]

So as you can see i can't reproduce the huge -100hs drop you said. As a matter of fact, i can only produce + hash, not -  Smiley
Something really strange going on. Made a few benchmarks...
The card and driver:

Memory is micron MT51J256M3, BIOS is flashed with this strap in all above the 1750:
777000000000000022AA1C00EF615C41B0551016BA0D96060060060004061420EA8940AA030004C 01914292E692E3B16

Every miner version has compiled kernels by it's own. Every test duration is 6+ min. ODT reset and re-apply settings before each miner start.
And all of these tests is on haven algo. I think, for heavy will be the same config.

Parameters, used in config.txt:
i - intensity
w - worksize
t - threads
f - fragments
Core/mem clocks are 1200/2025

Results:
i29w16t2f1
v1.6.9 - 512
v1.7.0 - 499
i29w16t2f32
v1.6.9 - 610
v1.7.0 - 505
i29w16t2f16
v1.6.9 - 526
v1.7.0 - 502
i29w8t2f1
v1.6.9 - 539
v1.7.0 - 502
i29w8t2f16
v1.6.9 - 612
v1.7.0 - 505
i29w8t2f32
v1.6.9 - 608
v1.7.0 - 506
i29w8t2f64
v1.6.9 - 606
v1.7.0 - 513

Question 1: how to calculate starting intensity to tune the card? Somewhere I've found a formula, that best intensity = (shaders-64)/2, but all of my cards are producing compute errors on such values, so for each card I need to go down for 128-256 points, to get rid of errors...

Question2: how the intensity value is correlated with vmem size? For example, if RX560 2Gb card have max hashrate at intensity 16, is it possible for RX560 4Gb card to have bigger hashrate at bigger intensity? And how much is "tuning window" for 4Gb model, comparing to 2Gb? (assuming, that # of shaders and CU are the same on both cards)

Question3: is there a way to set intensity per-thread for each card? So, I mean, for example, 2 threads per 1 card, but 1st thread with i54, and the 2nd thread with i56? (maybe feature request for future ver?..)

I will introduce a few modes for heavy algos in next version, so everyone can find the one that works for him best.

1. Optimal intensity can sometimes differ even for the same brand cards, so i don't really know how to calculate the best value. Unfortunately its a try-fail game until you find the best one. It's not always the highest intensity that gives the best results.

2. Intensity = number of global threads (in other miners that value is SRB intensity x 16). Now when you do scratchpad size * global threads you get the approx size of memory that will be used.
example for heavy : 56 * 16 * 4 = 3584mb.

3. There is, check the first page Smiley (--enableduplicategpuid (enables the usage of the same gpu id in gpu_conf multiple times))
1052  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 12, 2018, 03:59:12 PM
Very happy with this miner and I no longer have issues with connecting to dev's pools since changing all DNS servers to 8.8.8.8 from Open DNS servers.

FINALLY!

you won't believe how glad i am that you finally resolved that issue.
1053  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 12, 2018, 12:49:14 PM
Hello
I have a problem with my VEGA miner since Monero V8. With v7 all my 8 Cards where running properly. But since V8, if only running one card, everything is good but as soon as I activate a second one, i get kernel power 41 and the rig reset.
I already tested the ram, the disk and reinstalled the complete Windows with no change. Also changed PSU but no help
I have ASrock BTC+ Pro
8GB RAM
Sapphire Vega64
Driver 18.5.2, HBCC of, Crossfire disabled
Win10

Any idea? Thanks for helping.

are you sure your psu has enough juice?
V8 needs more power than V7
1054  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 12, 2018, 11:10:37 AM
distinguished developer
one question
do you still support old pitcairn video cards ?
After the test of your latest version 1.7.0 I am at a loss?
srb 1.6.9 pitcairn 370 2 gb stelite v4 --- 485h / s
srb 1.7.0 ---- 226h / s
total failure
Hi i got  less hashes with 1.7.0 on my tahiti too. Can you share your 1.6.9 miner settings for pitcairn? Thank you.

Need more info, like is it stellite only or EVERY algo? same settings? what have you tried beside running new version with old config ?

I dont have every possible gpu to try out when coding, sometimes what pushes one card, takes off another, so dont be immediately mad bros  Cheesy
Absolutely no complaints, just results. In my case, for tahiti the most productive version is still 1.6.8, 1.6.9 is a little slower, 1.7.0 much slower. ( same settings, algo v8)

which card specifically, and what was the hashrate on 1.6.8 and what it is on 1.7.0 ?
I want to try to fix this issue.
1055  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 12, 2018, 10:14:21 AM
distinguished developer
one question
do you still support old pitcairn video cards ?
After the test of your latest version 1.7.0 I am at a loss?
srb 1.6.9 pitcairn 370 2 gb stelite v4 --- 485h / s
srb 1.7.0 ---- 226h / s
total failure
Hi i got  less hashes with 1.7.0 on my tahiti too. Can you share your 1.6.9 miner settings for pitcairn? Thank you.

Need more info, like is it stellite only or EVERY algo? same settings? what have you tried beside running new version with old config ?

I dont have every possible gpu to try out when coding, sometimes what pushes one card, takes off another, so dont be immediately mad bros  Cheesy
1056  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 11, 2018, 04:04:03 PM
On 1.7.0 I am getting better hashrate
my rx 580 4gb get about 10 H/s more on v8 (from 990 to 1000)
but my rx 570 4gb get about 40 H/s more on v8 (from 945 to 985)

For 5 cards (3x570 and 2x580) my hashrate went up for about 140 H/s compared to 1.6.9 with same settings but power consumption also increased for about 30W (from 630W to 660W).
Also my 570's are getting to much memory errors now, so I will need to lower intensity on v8.
For fast algo I am getting about 200H/s less compared to 1.6.9. with same settings.

play with fragments (its enough to try 0,1,2,4,8,16) and see which one gives the best results for that particular card.
also try aes 0,1 or 2 .
Fast algo is V7 variant nothing has changed in code for v7 and variants Smiley
my guess is that the default fragment value isn't optimal for your cards.

also in the next version i will also return the 'old' code for heavy, that was in 1.6.7, and some of you say it was better for you than the one now.
So with a new parameter (yes, again), you can choose which mode for heavy you want to use.

That way everyone will be happy  Grin
1057  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 11, 2018, 12:43:54 PM
My firsts tests with RX 580 cards V8 algo:

v1.6.8 4gb = 1000 H/s
v1.6.8 8gb = 935 H/s

v1.6.9 4gb = 985 H/s  Angry
v1.6.9 8gb = 975 H/s  Grin

v1.7.0 4gb = 1010 H/s  Grin
v1.7.0 8gb = 975 H/s  Roll Eyes

for 1.6.8 & previous best intensity for 4gb was 61 & 116 for 8gb
for 1.6.9 & 1.7.0 best intensity for 4gb is 54 & 100 for 8gb

Also say that with newer versions the card connected to monitor is much more sensitive to background programs loosing more than 200 H/s in some cases when with 1.6.8 & previous was loosing at most 30 H/s


Ok so obviously your 8G has some issue, maybe the strap, maybe just a bad card.
Anyways. You lowered the intensities and get same or better results. That's what i call a win  Cool
Probably lower power consumption with lower intensities.
1058  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 11, 2018, 12:30:51 PM
Okay, so some of you said that the hashrate on Rx560 4g is lower on 1.7.0 vs 1.6.9 on heavy algos (said Haven) - HERE
I took some time and made some tests :

Both cards are without bios mod.
Before every test i used the 'reset' button in ODT , just to be sure.
5 minute average result taken, same card, same clocks same driver same machine same everything.


RX550 4G:

Intensity : 15
Worksize : 12
Threads  : 2

1.6.9
Fragments 1   : 292 h/s
Fragments 32 : 270 h/s

1.7.0
Fragments 1   : 322 h/s
Fragments 32 : 304 h/s


RX560 4G:

Intensity : 15
Worksize : 8
Threads  : 2

1.6.9
Fragments 1   : 349 h/s
Fragments 32 : 340 h/s

1.7.0
Fragments 1   : 354 h/s
Fragments 32 : 356 h/s


So as you can see i can't reproduce the huge -100hs drop you said. As a matter of fact, i can only produce + hash, not -  Smiley
1059  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 11, 2018, 04:59:00 AM
what to do if you get compute errors?

also getting compute errors, can't shake them, on vega FEs, 18.q3.1-oct1 driver, Heavy

Try lowering you memory clock by 10mhs, and see if that helps
1060  Alternate cryptocurrencies / Mining (Altcoins) / Re: SRBMiner Cryptonight AMD GPU Miner V1.7.0 - native algo switching on: November 11, 2018, 04:57:29 AM
480 8gb samsung (strap Ubermax 3.1) 1300/2000/1.00v
Bittube
config:
{ "id" : 0, "intensity" : 59, "worksize" : 8, "threads" : 2}

srb 1.6.9 1169h  Cool
srb 1.7.0 1100h  Undecided

Quote
Speed increase on BitTube/Haven/Heavy/Italo algos up to ~10% (depends of gpu)
Houston we have a problem! Cry

Good for you if you had that speed on 1.6.9, continue using that version then Smiley

Hello

I found a bug with the new startup monitor option
If you run benchmark-algos.bat, the startup monitor will kick in and restart the miner every 120seconds and the benchmark never finishes
The .bat file needs "--disablestartupmonitor" OR make sure that "--benchmarkalgos" always disables all watchdogs
edit: one more! benchmark-algos doesn't benchmark "dark" nor "festival"

Thanks for reporting these, i will check it out


So... My RX 574 + 100H/s (v.1.6.9 = 750-770   v.1.7.0= 850-870) - nice! But RX 564 lower on new version (v.1.6.9 = 500   v.1.7.0= 450) bad! All cards same options at two versions.

distinguished developer
one question
do you still support old pitcairn video cards ?
After the test of your latest version 1.7.0 I am at a loss?
srb 1.6.9 pitcairn 370 2 gb stelite v4 --- 485h / s
srb 1.7.0 ---- 226h / s
total failure

Confirming the problem Sad On the RX560 cards there is big hashrate fall... (measured now on haven algo)
v1.6.9 = 613H/s
v1.7.0 = 501H/s
The settings, the driver version - all the same.
If I copy the kernel files, compiled on v1.6.9, to the .\Cache dir of v1.7.0, the RX560's hashrate is about 520-530H/s. But anyway - the problem is present Sad

P.S. RX570/580 have some hashrate increase, is about 30H/s

Could you guys try out other configurations, like change the intensity and fragments parameter?
Yes i know you would all like if always the same settings would work, but that is not possible unfortunately, one code has different effects on different gpu types.

For 560 4g try setting fragments in gpu_conf to 32 for haven algo (that was the value in the previous version), leave the intensity same for this test.
and clear the cache folder, don't copy binaries from older versions etc.
also please leave it work for minimum 5 minutes to get the 5 min average

EDIT:

Ok, my tests show this on Haven :

RX550 4G no mod :

Intensity : 15
Worksize : 12
Threads  : 2

5 minute average result

1.6.9
Fragments 1   : 292 h/s
Fragments 32 : 270 h/s

1.7.0
Fragments 1   : 322 h/s
Fragments 32 : 304 h/s

Later i will do this same test on my Rx560 4G and report back.
Pages: « 1 ... 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 [53] 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 ... 164 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!