Topic: [ANN] TeamRedMiner v0.10.10 - Ironfish/Kaspa/ZIL/Kawpow/Etchash and More - page 140. (Read 211877 times)

hi man, nice results! please can u share with me what cards are u using for each number? also maybe timings for elpida and sasmung? im not able to go above 950h/s or so...u have 4gb or 8gb?

Are you closing it down with the "X"? If so, try using CTRL+C and then typing "Y" + Enter.

If it still does, maybe your cards are not happy with the straps.


Also, the miner needs a good exit way. The old sgminer had "q" for exiting. The allocation would need to be cleared (have not actually checked if its doing so) when exiting. This can prevent crashes when re-launching the miner multiple times.


EDIT:


Performance tests:

1280/1950 Elpida
1300/2100 Samsung
1300/1950 Elpida
1300/1925 Elpida
At 0.95V
Doing 4260h/s at ~530W at wall.

1280/1950
1280/2100
1280/1950
1280/1925
At 0.925V
Doing 4180h/s at ~515W at wall.

1250/1950
1250/2100
1250/1950
1250/1925
At 0.925V
Doing 4060h/s at ~500W at wall.

I did not really try [email protected], performance loss seems to be going 1:1 with power consumption reduction below 1280 for me.

Compared to XMR-Stak: First decribed clocks at same voltage were giving me 4090h/s@520W on CNv7, and 3870h/s@570W on CNv8.

EDIT2: I saw something weird. Fails to connect to the Devpool for some reason.



Even after restarting the miner, its the same. Starts with the same message.

So I am meesing arround with settings...

7x vega 56 reference cards rig. 1408/875 1100/875

16+16 just hangs at launch
16+15 starts to work, but restarts rig after few minutes
16+14 works, but restarts rig after 30 mins or so. which never happend with other miners.14.3khs 1250w from wall
14+14 gives a little lower hashrate, but seems to be stable, also zero lost shares. 14.1khs  1250w from wall

Miner hangs the RIG when trying to close it.
Same problem on two different RIG's.
1- G3900 / ram 4gb / 4xRX570 4GB + 3 RX470 8GB / LTSB 14393 / 18.6.1
2- G3900 / ram 4gb / 7xRX470 4GB /  / LTSB 14393 / 18.6.1

Has anyone got this working on HiveOS?

Well, I predict a great future for your miner : )

I will look awesome miner and minerstats (this one I have not tried)

Thank you!!

Haha, no worries mate, after all we only added CNv8 less than a week ago!

The miner comes with a sgminer/cgminer compatible API. It's not the standard in the CN world, and we will build a little adapter that exposes an xmr stak-like http api and gui so all CN miners can just continue with what they were using earlier. We're still missing fans and temps though, needs to be added, and we will.

There are a number of tools which supports the API: Awesome Miner and MinerStats are two that have confirmed integration.

Cheers,
K

Hi

First of all excuse my ignorance, I have only used Srbminer to mine cryptonight.

What software could I use to monitor the miner?

regards!! : )

hello,

please can u share with me your timing and what voltage u used for core/mem?

thank you in advance

You know, I'm def not a mem strap wizard. For this particular 580, I'm quite sure it was a one click Pimp My Straps in the latest version of SRB PBE (the free one without any donation delays). I will check though, no worries!

I believe dragonmike managed to get his 470 4GB (Elpida) going in a nice way in the end, see if you can find his posts earlier in this thread.

yes im sure i have hynix and types i described above. most probably it is caused by the straps as im still around 850h/s with 8gb cards...4gb hash around 1000 and im using 1250core.
can u share with us some tips/timings/numbers u had with elpida? i have 4gb elpida cards, so curious about numbers and problems to avoid.

that might work,will try, but these are 8gb hynix,so will wait for new info about the strap used in your test scenario:)

The decimal representation of the difficulties are inherited from cgminer/sgminer, we wanted to keep it 100% compatible.

Next, the decimals come from a rounding effect. TL;DR is that everything is correct and the problem is that 30,000 isn't representable as a target _integer_, and what you're really mining against is pool diff 30,000.1208. The details follow below, might be a bit technical but you seem to be savvy enough to understand it!

So, when the pool says diff 30000, what it means is that (for CN) on average, every 30,000th hash should be eligible to submit to the pool. A hash is just a big random 256-bit number. To decide if a hash is good enough, we need another 256-bit number to compare it to. If a hash is lower than this number, we submit it to the pool.

Hence, we can't just compare a hash to the pool diff 30000, we need to convert it to a 256-bit integer first. Typically, you only compare the upper 32 or 64 (most common) bits of the hash. To produce a 32-bit number, we take 2^32 / 30000 = 143165.577. Here is the issue: this is not an integer, and we need to floor it rather than round it upwards or we will accept shares with diff 29999.999. So, the 32-bit number you compare with is 143165. This is the _true_ difficulty target we're comparing hashes against.

This number (143165) does not represent difficulty 30000. To convert it back, we do X = 2^32 / 143165 = 30,000.1208, which is the number you're seeing. The end result is that you are mining against diff 30,000.1208, because mining against exactly pool diff 30,000 is impossible, and that is why you're seeing this number everywhere in the api numbers.

Hope that helps!

The 580 8GB Hynix is one of our testing 580 8GB cards. Need to check the straps, and also make 100% sure it's Hynix so I wasn't lying . When you're at 1250 cclk and still at 855 h/s with a 580 8GB using 8+8 for config, it's clearly mem bound and better straps is the only thing you should look for. Hynix usually produces > 1000 h/s though, we've had more problems with Elpida.

Not sure if it works, but if you e.g. disable two other cards in the device manager, is card 11+12 moved down to 9+10 and visible in atiflash?

u were correct man, thank you for tip. i tried use different timings from srb and i was able to increase hash for my rx 580 4gb from 912 to 1015! still playing with 8gb cards.
btw do you know how to load bios for card more than 10? i have 11 and 12 cards too and cant go with atiflash above 0-9

EDIT: please can someone share with me timings for 8GB hynix H5GQ8H24MJR and H5GC8H24MJR?
i used 777000000000000022AA1C00B56A6D46C0551017BE8E060C006AE6000C081420EA8900AB0300000 01B162C31C0313F17 from pbe 1.6.9
and now using 999000000000000022559D0052626C48A0551214BC0D460B0048C4007D0714204A8900A00200712 419123138B42D3D17 from SRBpolaris v3.5
in first case 1250/2200 got 855
in second case i can go only 2150 and getting 878

in first article here, someone mentioned for rx 580 8gb hynix at 1250/2000 getting 1000+

Increase core clocks maybe? Or your memory straps are probably bad. Or both. At 1300/2100, a 580 4GB Samsung does ~1070h/s.



Also, the reported stats from the API... i kinda do not understand one thing from it:




Why the Share size is not an Integer number, instead, its Decimal O_o. This is, considering that i am using static difficulty of 30000. The Rejected Difficulty shows 60k, which is 2x30k shares, but there are some decimals appended. Same with Last Share Difficulty.

I have thought a number of times that I should write a primer on the math involved in the mining process so people can plug in numbers and verify certain situations. A super quick back-of-the-envelope calculation for you finding 300 shares when you maybe should have found 306 shares gives that this would happen with a little less than 40% probability, so really nothing out of the ordinary.

For the individual gpus, it's much too few trials to get a good read.

How is the poolside stats looking now, a few hours later?

Sorry so say we haven't tested on Win7 at all ourselves, and all reports point to no, doesn't work . If we ever get some time over in the near future, I'll try to get a Win7 env going and see what's going on.

Hey, thanks for the kind words and the time you've invested in this to get it running smoothly on all your rigs!

Miner uptime - just put it on the todo list. Watchdog as well, will be added shortly.

Yep, we will for sure add variants incl the heavy family. Close to 100% of the available time since release has been about support and weeding out early issues. Still have some more work to do in that space, but as soon as we can relax a little we'll go back to the kernels.

Yep, fully agree. Watchdog mechanism on the TODO list so you can choose yourself what to do.