Hello all!
Ryzen 1700@ CN-Light : with 1M scratchpad, 16M cache and logical 16 CPUs, sure the best config is 16 threads.
I pull ~1825 h/s in Turtle (CN-Light v7) from my R5 1600 stock. A R7 should go above, maybe you have a Large Page config problem. Or another app that floods your cache.
583-587 h/s with my first successful strap
Wh.. wh.. what? ~585 from a RX560? My best 560 goes up to 530 with JCE, using standard One-click patched memory straps, and i'm already happy with it. Would you share your timings? Since mining is a competitive game, the good answer should be No, but i ask just in case
I've been a custom strap author before, on old HD7800s (with the well know BBBG memory) but those cards are a lot more rare today, even if still quite powerful (JCE pushes a HD7850 2Gb to 525 h/s, close to a RX550)
Has this been done yet?
The second upload of JCE
unofficially uses a different detect code, but not sure at all it fixes anything. I'm waiting for my Bulldozer APU to be able to debug well the APU case. I could copy the working detect code from Stak, but that's illegal since JCE is close source. I want to write mine, even if it causes delays.
@UnclWish: thanks for yet another cray nicehash netcode bug report. It may be possible the devfee switch is a problem, i admit the case
slow CPU + SSL + nicehash + wait for 2 hours is not a test case I anticiapted.
So GPU only mining is only 0.9% fee correct?
Correct. The devfee is logged at startup, GPU and/or CPU fee level. They are separate and not cumulated (CPU 1.5% and GPU 0.9% is not an overall 2.4%, that's just 1.5% on CPU and,
separately, 0.9% on GPU)
Aeon mining is recognized as common cryptonight mining.
Hoo, i'm getting lost with all those coins that fork, de-fork, re-fork, over-fork... Thanks for report, i'll default Aeon to correct fork in next version.
Anyone know of a monitoring tool compatible with JCE? I have 4 instances going and it would be much easier to look in a central location than have browser windows/ssh sessions up!
Forager supports JCE for a long time. I asked some of my user to request JCE support in Awesome Miner, but it seems it hasn't been done yet. I don't want to ask directly, it would pass for an indirect advertisement for JCE, but you should ask the dev on his topic.
Note that I got several complains about how bad was my JSON API, and I admit I rushed it, it's easy to read by a human, but hard to parse. so any monitor tool should focus on the XMR-Stak compatible mode (param --stakjson), which is a lot more clean and stable.
