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

Hi! Thank you very much! Great work as always!

Milan

hello,
while i didn't test on every possible card in existence, the gpu version should work down to the hd6000
If you were talking about the Linux version, it has no gpu support at all.

Hi,
I am assuming you can not mine AMD R9 200 series with these versions?

linux version 0.33q to be uploaded in about an hour, i'm finishing the package.

i expect you reach 800+ on new masari as an order of magnitude on a HD7950/270. i depends on the card, and of course you should flash the bios to use better memory timings, if not already done.

edit: it's online

Hi JCE, updated/fixed Linux CPU version? I've increased you linux mining fee income a bit now:) Trying to mine MSR now What is your MSR HR on old 270x and 280x cards? I've some 270x and 280x on linux runnig ETP, wondering if it make sense to switch to win10 and JCE?

Thanx,

Milan

Thank you for feedback! I will use legacy mode until you find solution.

Very interresting, so i may find the bug with no need to reproduce. I suspected the sync (that --legacy disable) to be able to cause such problem.
Thanks!

After adding --legacy miner start to work on one of two GPU. But if remove --legacy no 1st or 2nd GPU didn't work separately. After connecting to nicehash attrib.exe close with application error.
Bug is not for 1st GPU - it happens on any one of two GPU...
Windows 10 x64 latest 19.1.2 drivers. It was on 19.1.1 and on b15,b16 versions too.

Start string is:
jce_cn_gpu_miner%BITS%.exe -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %* --nicehash --retrydelay 5 --variation 5 --forever -c config1st580Heavy.txt --no-cpu

Yes, use the private messages feature of that forum please, i don't use social medias like Discord (too time consuming).
Also, i dev alone, no pural developers

@Unclwish: i mined the same way as you (Nicehash Heavy on GPU 0, one thread) and it worked for me. Sad i couldn't reproduce the bug. What happens when you add parameter --legacy ?

I'm building the 0.33b18 GPU, with the same changes as CPU:


edit: it's online now

Dear developers how can I contact you?

Change your settings for the 580. I have 8,5KH/s to 8,6KH/s with my 574s (except the crappy one at 7KH/s with lower intensity). Core 1240, mem 2060 (one at 2035) with 1008 intensity.

No Vega, so I dunno about them. I'm waiting for Navi

Guys, what results should one expect on TRTL v2 with polaris and vega? I have 8.2khs with rx578 micron 1200/2140@900mV and 15.5 khs with vega 56 hynix 1380/1050@875mV with another miner.
Should I expect boost with jce?
BTW, my R5 [email protected] is doing nice 10khs )) Thanks, JCE

God thanks ! And thanks Graft (soon another name) project ! ... Will be huge in few years ! Hope the effort you put it will reward you in the long term

A 33q CPU is online but I just noticed a bug when mining Masari v8 on a AES cpu with multi-hash=2 (reported on Github).
So I re-release it with the fix included. If you already downloaded 33q, wait a bit and redownload. The linux and GPU version will be released with the fix directly.

edit: it's fixed now. Then come the Linux and GPU version. I'll still give a try to reproduce Unclwish bug.

Ok-ok. I'll wait. Note that cards are both RX 580 8Gb. Now I forced to set 2nd GPU 1 thread and 16 multi_hash to start mining at 1st GPU and 2nd GPU almost free, but even 1x16 gives some load on 2nd GPU...

This may be true for any algo...
On TRTL v2, a AES cpu is close to an asic: all instructions are native (the 128-bits multiply, the 64 bits divide, the squareroot, and of course the AES) with all data fitting into the cache, assuming you have a decent CPU (read: not an Atom).

The next release will default Turtle to v2, as it has just forked, and will enable it among the eligible algo for pool autoswitch.
I'll release CPU version first.

As an exception, i'll ship the new Graft fork right now, with no test on a real pool (tested only on a local node). As --variation 22.
Sorry Unclwish I won't delay the release to investigate your bug since the Turtle fork is somewhat an emergency issue.

FPGAs will have even more impressive boost with this low-mem algo. Don't worry ))) Only heavy type algos leave hope for gpus

Hi all!

Unclwish: i note, i'll try to reproduce the bug on a 2-gpu rig.

HYC: both Hycon and Webchain are non-standard CN forks that would require a lot more refactoring of my netcode than the other forks, so, looking at how little dev time i've left now, i bypassed them for now. My next fork should be Graft. Take a look at SRB who added support for those both forks recently on GPU, and on CPU you can get the reference miner, possibly compiled with zero fees.
Both those forks are not CPU-friendly, and coin-specific, and since my miner is mostly a CPU miner, I somehow overlooked them on purpose. Turtle v2 and Masari v8 are a lot more interresting to mine on CPU.
Now I focus on CN-Waltz for Graft, which is a cleaner and better documented fork.

JCE as a virus: thanks all for the report, and yes that already happened several times, and there's little I can do above putting a warning about the fake releases on all my download pages (here page 1 and Github). I tends to happen to every miner software, very like being detected as a virus by Win Defender and al. That's the game

So sad how all those coin prices are on a down trend. Haven got its price divided by 10

So, after around 19hs mining TURTLECOIN with the new algo, a bit of feedback:

Reminder: my PC/rig is composed of Ryzen 5 2400G (12GB DDR4 2400) on a X470 mobo and 4X AMD RX570 4GB with bios mod.

My GPU hashrate is 4,22X higher than with the previous algo, which means GPUs are much better off against FPGAs. I have now around 33KH/s, I had at most 7,8KH/s before.
My CPU hashrate is 6X higher than previously (I had 860H/s, now 5150H/s) which means to me that the new algo really favors CPUs for better decentralisation. The Ryzen G has little cache (8MB L3) and I use it for display, meaning that I can't access the whole L3 cache. I expect normal Ryzen series to get an even more impressive boost in performance.

The new algo is more power hungry, that doesn't bother me at all considering the HUGGGGE boost in performance. With the CN lite V7 it was 450W/H (CPU + GPU), now 570W/H (CPU + GPU) with CN ultra lite.

Among my RX570s, one has a much weaker ASIC than the others, so I had to reduce the intensity compared to the other GPUs, otherwise it hangs out after less than 30mn mining. So the weak one intensity is 960, the others including my beloved little Sapphire ITX is 1008.

The network fee is ridiculously low (love it ), 0.03TRTL for a >10K payment by the pool.



Thanks to JCE for the amazing miner, thanks to TURTLECOIN devs for really taking care of their mining community

Hi, DEV) Are you planing to add HYC coin?