Topic: [XMR] JCE Miner Cryptonight/forks, now with GPU! - page 51. (Read 90841 times)

Hi JCE,

i updated my 3 Rigs to JCE Miner. It works great, effective hash increase, but i have a problem.



At around 3:30 o´clock all 3 rigs deliver stale shares for around 1.5 hours, 5 days in a row. Other people in this pool don´t have this problem, other miner (for example SRB) don´t have this problem. If it is on 1 Rig then i say ok to much OC, but 3 realy different rigs with different cards and different drivers make the same problem? i think it is a jce miner problem. A Ryzen R5 1600 delivers also stales shares and with the older version 0.32m it works.
I use jce 0.32q at the moment. Any solution or other guys with this problem?

thnx for your great miner.
Upcoming October 18th fork of XMR supported?

cheers

Thank you for a great CPU/GPU miner. I'm currently getting an average of 360 H/s each on RX 560 2GB cards mining Cryptonight heavy. That's about 50 H/s more per card than when I was using them on SMOS with XMR-stak or XMR-rig. Plus with the --no cpu command I'm able to cpu mine a different coin with a different algo miner and there is no noticeable loss in performance for either coin being mined. Maximum hashrates all around.

The RX 560 4GB and RX 580 rigs are next on the list of moving to your miner program. Thanks again and the dev fee is definitely reasonable and worth every bit.

It would certainly be nice of you were to write a multi-algo miner to cover them all. HODL comes to mind.......

Thanks again,
Chris B.

Oh, i never tried this feature, sure it's a lot more useful than the autoswitch when Monero forks (twice a year). I'm still not confident to have time enough to implement it, but you convinced me it's not just a gadget feature

I hope i'll be able to release the v8-capable CPU version soon.

not two. I use this features very often. I can connect xmrig miner to XNP and don't touch miner, only config XNP to connect to different pools. XNP says xmirg which algo to use.

Hi all!

Sorry I had very little time to do the Support since i'm focusing on the V8 fork, and there are little time remaining to do all the benches and tests. The problem with assembly dev is that it takes a LOT of time, step by step.

Thanks for the warm feedback

ditto

I use the same fee system as Claymore, I already explained it, so there are randomized start/duration of fee sessions on the same algo that you use, for both CPU and GPU. Like Claymore did.
One difference, I use non-aggressive opaque fee sessions: some shares, from time to time, on a 0.9% average, are sent to me, and not counted in the effective hashrate counter. This this different from Claymore who colored them Purple.
And having learnt from SRB feedbacks, the fees are non-blocking (if the fee fails the miner continues fine, and does not produce revenge stale shares like Claymore did). And having observed the tagged fees in SRB triggered people restarting the miner just before the fee session, a form of cheating, they are opaque and randomized, on purpose.
The overall behavior is that you'll get at least 99.1% of your hashing power whatever happens.
On CPU fees are 1.5% (AES) or 3% (non-AES) and in case of mix, the fee level is weighted-averaged.

This is a nice feature... which is useful twice a year at best, so i probably won't have time for it

Sure send, i'll take time to read it. I appologize to all who sent me a message i haven't read yet, but as said above, i'm struggling at finishing my v8 assembly in time

I skip all questions about GPU for now, I'm focusing on the CPU version, I want to release all CPU versions (32/64, AES/non-aes, Win/Linux) in time.

Have same issue (mentioned above).  Often-times, it works itself out after an hour or two.  However, you can also put a watchdog limit in, and an auto-restart loop around the miner, and it may get to optimal speeds faster.

Hello!
You miner is perfect!!
Good work.
Can you add in miner mining algorithm negotiation like xmirg
https://github.com/xmrig/xmrig-proxy/blob/master/doc/STRATUM_EXT.md

Hi, JCE! I want to send you a personal message with your permission! This is important.

I'm understand now... On latest 1803 launching GPU-Z didn't nothing except freezes during mining... And on latest driver max stable intensity is 944 on heavy algo and 8Gb vmem...

I am on Win10 1709 + blockchain beta drivers.

What system and drivers you're use? On Windows 10 and latest drivers max intensity on heavy is 944. Even 960 gives significant drop in speed. So as launched GPU-Z... It didn't add speed, but it can decrease it...

I've got a problem with the warm-up on my RX580s, not all cards in a sistem end up at full optimal speed after the warmup on heavy/haven/saber. This happens even if I have gpu-z in the background (which adds another 15h/s per card fluctuation after the warmup). I am on "p" version right now, on "n" version I thought it did much better, but wanted to use refined watchdog and get a small boost in mining speed with the latest version. What am I doing wrong?
I use 976 intensity, happens with lower intensity too. If I turn off a card that has optimal speed after warmup, and turn it back on, it has 15% less speed and doesn't get back up to optimal. Something needs to be reworked in the handling of the warmup, I also see a VRAM cluttering, an 8gb cards ends up showing it has 11gb of vram used in gpu-z (maybe bug?). Maybe we need some way to flush the vram and this is what's causing it, especially for those that restart the miner quite often (automatic profit switchers).

Pretty solid Miner JCE ! I have not yet fine tuned my 12 rx580 with your miner and already got 1kh increase in the 24h avg chart !

Ha thanks for the reply !  Will test it when I go back home in 2 days.

for an auto-restart, you just need a label definition before the miner, and a goto after.  I.e.:

Found my answer on pages 53 and 58. Thanks !

Will work on miner automatic restart after watchdog close it

My 12 rx580 working on your miner ! All pretty fine ! Thanks.

Hi ! nice miner i tried it local yesterday before planing to put it on my rigs. Before it i would like to know how devfees works ? Is it like Claymore and you connect to your pool from time to time for few secs/mins ? i've not seen anything on my test yesterday.

Thanks.

hi jes'

jce will automaticatly change algo on the fork or not?

maybe with optimisation,we don't loose 10%?

32p version??

Heh -  I'm a PPT veteran - been running these vegas for almost a year

.875-.894 / .887-.906.  Generally 160-170 at wall.