Pages:
Author

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

sr. member
Activity: 1484
Merit: 253
If you bench against Claymore 11.3 look at the hashrate reported by the pool, because on my HD7950 rig i have a lower hashrate on screen (559 JCE against 585 Claymore per card) but a better pool hashrate.

on 2G cards (HD7850, 7870) i'm better, even on screen. i never tested on 730
On my Pitcairn 270X 4Gb Claymore 11.3 gives 550 H/s (manual modded bios with OC), JCE after start gives 500-525 H/s. After 10-15 min JCE gives 555-560 H/s.
member
Activity: 350
Merit: 22
If you bench against Claymore 11.3 look at the hashrate reported by the pool, because on my HD7950 rig i have a lower hashrate on screen (559 JCE against 585 Claymore per card) but a better pool hashrate.

on 2G cards (HD7850, 7870) i'm better, even on screen. i never tested on 730
jr. member
Activity: 176
Merit: 2
Can anyone share the best config to mine CN Heavy for RX Vega 56??
Thanks

you can try below config with driver 18.6.1.

{ "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":992 },
{ "mode" : "GPU", "worksize" : 16, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":992 },
newbie
Activity: 10
Merit: 0
Can anyone share the best config to mine CN Heavy for RX Vega 56??
Thanks
sr. member
Activity: 1484
Merit: 253
I ran the little test with old rx 370 and hd 7970 cards with version 032q - worse than clay 11.3. 4x370 - 1.4kH, 5x7970 - 2.2kH; in the claymore 1.7kH and 2.4kH. No optimization with old videocards?
Probably you didn't wait enough to recieve max speed. For full speed you need to wait about 10-15 minutes on JCE.
newbie
Activity: 52
Merit: 0
I ran the little test with old rx 370 and hd 7970 cards with version 032q - worse than clay 11.3. 4x370 - 1.4kH, 5x7970 - 2.2kH; in the claymore 1.7kH and 2.4kH. No optimization with old videocards?
sr. member
Activity: 1484
Merit: 253
the attrib trick is a stealth mode to bypass some antiviruses, and it's very documented in the doc:
https://github.com/jceminer/cn_cpu_miner#privacy-and-security

Quote
It doesn't:
•Punch through your firewall: you have to open it manually if needed
•Run any command, not even attrib (see below)

hard to be closer to what you experienced
and yes it is safe Wink and not new, just your firewall did its job

i'm not done yet for v8 because i'm writing it in assembly. i think i've room for optimizations Wink


Thanks for clarifying that JCE!

However, I think that creating a virus like behaviour in a miner
can do only harm. A person who decided mining should
also be able to add JCE in the exclusions list of his Anti-Virus software.

Good luck with optimizations in V8, we all want them!
Sometimes it's strange situation with antiviruses. They sometime blocks attrib.exe, JCE miner exe is on exclusions, but attrib.exe is blocked...
member
Activity: 762
Merit: 35
the attrib trick is a stealth mode to bypass some antiviruses, and it's very documented in the doc:
https://github.com/jceminer/cn_cpu_miner#privacy-and-security

Quote
It doesn't:
•Punch through your firewall: you have to open it manually if needed
•Run any command, not even attrib (see below)

hard to be closer to what you experienced
and yes it is safe Wink and not new, just your firewall did its job

i'm not done yet for v8 because i'm writing it in assembly. i think i've room for optimizations Wink


Thanks for clarifying that JCE!

However, I think that creating a virus like behaviour in a miner
can do only harm. A person who decided mining should
also be able to add JCE in the exclusions list of his Anti-Virus software.

Good luck with optimizations in V8, we all want them!
member
Activity: 350
Merit: 22
the attrib trick is a stealth mode to bypass some antiviruses, and it's very documented in the doc:
https://github.com/jceminer/cn_cpu_miner#privacy-and-security

Quote
It doesn't:
•Punch through your firewall: you have to open it manually if needed
•Run any command, not even attrib (see below)

hard to be closer to what you experienced
and yes it is safe Wink and not new, just your firewall did its job

i'm not done yet for v8 because i'm writing it in assembly. i think i've room for optimizations Wink
member
Activity: 762
Merit: 35
hi JCE, I just updated to the latest CPU miner version n.
Today, when i started it, my firewall requested  of attrib.exe
to the pool i'm mining at. This was not the case with the previous version.

Could you provide more information about this and is this safe?

member
Activity: 190
Merit: 59
JCE, did you try next monero algo? You think you will be able to make effective miner for it? There is a test pool at killallasics.com so i was just wondering if you already tried anything  Grin Grin
member
Activity: 350
Merit: 22
Hi all,

CPU devfee: it's now documented that if you enable the CPU mining, then pause it, the fee ratio will be higher than if you enabled only the GPU.
But that's ok, i'll make the next fee session after the pause at pure GPU level (0.9%), that's more fair, and is quite a corner case.

Screen on GPU: sure it slows the GPU a bit, try to lower the multi_hash a bit on that GPU to compensate.

I'll add also the ten top biggest shares found, for fun.
newbie
Activity: 19
Merit: 0
hi, gpu 0 for me has lower hash rate then the other gpu's, same OC settings and parameters in miner, is it because it has a monitor plugged in? difference in hashrate is noticable

also 1 gpu on CN heavy is averaging around 460h/s but has spiked to 590 h/s! is that normal on CN-heavy?
newbie
Activity: 54
Merit: 0
You explained the cpu fee which wasn't voided while the cpu is paused.

Is this bug corrected in the 0.32q?

It bothers me because having to stop then restart the mining only to disabled the cpu is much longer than pausing it, but it's still worth if it avoids some buggy fees.

member
Activity: 350
Merit: 22
JCE already reports the value of the shares it finds (value, not diff) and it sends it to the pool only when the diff is higher or equal.
some guy here tested it on its own pool and, after a cosmetical bugfix i found thanks to his test, it proven to be 100% accurate now. so I still think it's both mathematically and technically useless, with the existing share counter being enough.

but, since you took time to ask it, i'll still add it to the native json report, that's easy to do and somehow fun to look when you get a very high share. even Claymore reported the big shares, so it's ok, for fun Wink

next planned release is the cpu version for 32/64 bits linux and windows.
newbie
Activity: 11
Merit: 0
Well the value of best shares history comes to the fore when someone mines solo (like I do) cause it helps to understand whether all your large shares got to solve the block. It helps to understand if your pool is working fine. Cause if you've had like 4 shares with bigger value then the current network difficulty but got only 3 blocks then you should check what went wrong on the pool side.
If it's not difficult to implement then it would be nice to have that.
member
Activity: 350
Merit: 22
Thanks!

the multi-pool is planned, i just never took time to finish it and always switched to other topics Sad
the next big one will be to support Monero V8

i never understood the point about the big shares, since mining is a game of random, if you mine at 5000 H/s you'll get a 5'000'000 big share every 1000 seconds, and so on. To me, that's as useless as keeping the history of a Roulette, all shares are independent, if you mine at difficulty 10000, a share 10000 or 1000000000000 will worth the same.


if there's a technical value of keeping the history of big share, i'm reading you Wink
newbie
Activity: 11
Merit: 0
Many thanks to the creator of this great miner, I'm using it on 560/470/570/Vegas and it delivers the best hashrate among any other miners I've tried but I miss two features: failover pools and best shares in api (I know that I can turn stak compatibility mode on and see those but it would be much better to have that in jce format report as jce format also shows fans/temperatures).
newbie
Activity: 11
Merit: 0
Quote
I probably applied my Pitcairn optim to the rx550 by mistake, i fix it in version q (for quick, I hope).

It's ok now  Cheesy
member
Activity: 350
Merit: 22
Someone checked on RX 550 2GB (c 1315MHz, m 2000MHz) , Windows 10 (1709) 64bit, Drivers 18.9.2?
Quote
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":432 },
On my 3 (rx 550) the version 32m have best stable h/s near 530 (together more than 1580 h/s), batt on 32n and 32p I have declines to 450, 470 and one example is around 530, or two near 530, or 490  (together closer 1400 h/s and even less).
I probably applied my Pitcairn optim to the rx550 by mistake, i fix it in version q (for quick, I hope).
It will include a new CPU optim for non-AES, I now can reach 119 h/s on CN-v7 on my Core2 xeon 2.666G. A nice +2% perf.

edit:
Version 0.32q GPU is online
Same as the 0.32p that i removed, but with more CPU speed and fixed rx550 regression (my rx550 rig is broken currently (PSU problem), so i couldn't test, but i just put back the same code as the m version, so it should fix).
Pages:
Jump to: