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

My RX 2G work well with 464+464 or 464+480 with no screen attached, but the main GPU has to be downsized to 432+432.
I don't use the latest drivers yet, i'm on some 18.5 or something, i didn't take time to update.

Any idea how can i get two threads with 448 on 2gb Rx 560/550? so far 16 work size and 64 alpha is the best speed.

Fine. We are all confused

Was checking someone the latest 18.7.1 drivers? Because I have very much invalid share on them. And a lot of low diff messages, Return to 18.6.1 and everything is ok

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.

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)

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.

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)

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.

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.

Impressive, I'm back to cryptonight-v1 hashrates on my 470s.

So GPU only mining is only 0.9% fee correct?

Leeeeets give feedback (again):

Aeon mining is recognized as common cryptonight mining.

Dude, holy macaroni, wanted to screen shot your miner with 560 2gb Elpida, 583-587 h/s with my first successful strap still have to go higher frequency and do more changes to get more hash.
memory controller utilization; 54% and more spikes to 57-59% in HWinfo.
had to do lots of bios tweaking very low level, the strap i used will still improve alot! thanks! (that elpida isn't even a high bandwidth/quality one, thats an average one thats normally clocked to 1750 mhz , i have cheapo ones that are 1750mhz factory overclocked, yet the straps i try to do are relaxed so these can now give 530-550 h/s with your miner)

Hello miners,

I'm using the last version of JCEMiner(31c) on CNLite V7(set FORK=4 in the .bat), mining Turtlecoin.
I mine with CPU+GPU(Threadripper 1950x & Sapphire Nitro+ Vega56).

Config: https://imgur.com/JCFukAv
Hashrates on the miner:https://imgur.com/aPMszui
Hashrates on the pool: https://imgur.com/dqVebcX

The CPU is OC 10% from 3.4Ghz to 3.75Ghz.
For the Vega i'm using(1500Mhz/950mV on the gpu and 925Mhz/925mV on the memory). The Vega is serving also a fullhd display.
The full output wattage reported on the system in stand-by is 85W and when mining 330W.
The CPU itself is showing 10W in standby and around 100W when mining.
The temp of the CPU is around 60 degrees with air cooling(Noctua U12S with 2 fans).
The Vega is around 50 degrees at 2000 rpm for the fans.

I think the hashrates are good but unfortunately not a lot of coins are using this CNLite V7 fork.

Happy mining!

My 1700@3800 and 3133 runs at more than 2680 h/s on CN Lite.

My setting is pretty simple:

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!

I know all of this. My goal is not max speed from CPU. I use it just for small bonus to my GPU's. My problem is 0 shares sometimes all the time...

Elpida 560 goes to 26 intensity (sometimes is sad with a driver/ windows combo) Hynix doesnt like 26 and can only 25. with JCE so far 432X2 or 448+416

Has this been done yet?

p.s. I am in low power mode for the hot summer, but I am pleased with the VEGA speeds, even at 880mv for clocks and memory.

Hello Jce,

Hope you are having a good day.

I`m a big fan of your miner as it is the first one that works good with Vega and i love the way you keep making it better.

I have a small question/request that involves automatic algo switching.

I know this seems not so useful but in my case it is.

I mine on MoneroOcean, and this pool currently mines best performing V7 alt coins and pays in Monero so the profit is better. I have heard from the developer on Discord that they are planing to also add Heavy and Light coins in the mix, but only miners that support it will work. From what i can understand the miner will need to change algo on the fly from V7 to heavy for example to mine the most profitable coin. He said and i quote "Yes, working on xmrig patch now for that" so i do think that the devs of XMRig have or will have a miner that can auto switch but i do not know how they implement it.

I know that your miner compiles the code at start but would it be able to compile it for more algorithms and keep it in memory until it needs to be used?


I really think this will be the next go to miner in the future so wanted to see if this is possible.

Thank you!

Apart from your problem with the dev fee reconnect: You shouldn't use double hash with CNv7 on an AMD FX. Bulldozer has got 2 MB L2 cache per module. That's exactly the scratchpad size of one CNv7 thread. So don't us double hash, which results in 4 MB scratchpad size, use four single hash threads and put one per module, ergo (under Windows) cores 0, 2, 4 and 6 (or 1, 3, 5 and 7). That's way faster than your config. With CNv7 you should get a hashrate of approximalely 290 H/s.

The maximum you can get with an AMD FX is, to use the circumstance that it has – beneath its 2 MB L2 cache per module – an 8 MB L3 victim cache, which is not inclusive as it is the case with all Intel CPUs. Data in the L2 cache is never in the L3 cache and vice versa. So with bulldozer, you can start 8 single hash CNv7 threads dedicated to the cores 0, 1, 2, 3, 4, 5, 6 and 7. This config will result in a lot of traffic between L2 and L3, that's why performance will not scale linear with the number of threads, but still all data is cached, no slow memory access. It will give you the max. performance, in your case around 340 H/s with FX-8320.

Using cpu miner 0.31a. Algo cn-v7 on nicehash via ssl port 33363. AMD FX 8320 on two double threads. Speed about 175-190 h/s. Pool diff 100001.

Problem: Sometimes miner didn't find any share during hours! Untill restart them. All goes normal. Miner show speed, periodically recieves new jobs, no errors. But no shares for 2-3 hours?
After restarting miner, it start to find shares as must.
I think that it's due to devfee. I think that sometimes after mining devfee, it stop to find shares at all... Just thinking... But not every luanch this happens. Now I check after 20-30 minutes and if no shares finded, restart miner... This problem is on all previous versions. I just didn't try many hours before, and thinked that I'm not lucky... But after restarting miner it starts to find them.... It's strange...

Lines mining is recognised as Loki mining. Please take a look

Here is what i used, don't remember exact numbers but hash was around 900 h/s from RX550 2G Hynix

Hi guys. Has anyone tried Masari on RX550 / 2 GB. I can not adjust parameters either as stable. on the buffin, the cards give out a maximum of 950 h/s for a short time and then the system drops, and 4 cards on the Lexa give out only 800 h/s and  then the system drops.