[JCE]Fast & stable CN/v8/Heavy/Tube/XHV miner, CPU+GPU, Vega56 1800+ RX580 1200+

[Iamtutut]

JCE please note:

RYO is going to fork with a new algo "CN GPU": Fork Block: 228750 @ Feb 14th 2019 UTC 12.00

Github: https://github.com/ryo-currency/ryo-currency/pull/163
Testpool: https://tnpool.ryo-currency.com/

[migo77]

JCE, monero is forking in one month too...

https://www.reddit.com/r/Monero/comments/ap6iiw/monero_will_fork_at_block_1788000_march_9th/

[Lonnegan64]

RYO is going to fork with a new algo "CN GPU"

Wow, with floating point operations!   That should keep away ASICs for a loooong time  

5. New mining algo Cryptonight-GPU (CN-GPU).
Our previously developed POW Cryptonight-heavy was made to put GPU miners in a safe harbor, from ASICs and botnets threat. Keeping an eye on recent attacks of various coins by ASICs, botnets and FPGAs, we developed brand new mining algo. Keeping in mind GPU miners, our goal is to achieve our concept of fair GPU mining:

The most possible equality for both AMD and NVIDIA lineups of GPUs.
Scalable performance from low-end to high-end GPU.
Further slowing down CPUs in mining, making botnet creation times more inefficient.
Keeping algo ASIC-resistant.
Making algo FPGA-resistant.
Remove ability to attack network using Nicehash.
As you can see, the task is nowhere trivial and it took several weeks of hard work which resulted in the completion of all 6 goals:

Hashrate of NVIDIA GPUs increased up to 35% (depending on model) compared to CN-Heavy. Testing showed the potential of getting close results for comparable by compute capabilities cards. Though some AMD cards show decrease in hashrate compared to CN-heavy.
It is simple like that: If your GPU A is faster in Flops than GPU B - it will be faster in CN-GPU algo.
CPUs are even more slowed down e.g: Intel i3 - 4h/s (maximum - 4 threads), AMD Ryzen 1700 - 100hs (max - 16 threads)
Known ASICs are not capable of handling such computations, the cost of creation of an ASIC of this type is too high to be considered possible.
FPGAs can be programmed to execute any algo, but FP32 math is heavy even for this kind of devices, making the whole idea of spending dozens of thousands of USD and getting relative result to couple hi-end GPUs.
It is obvious that NH won't be supported a while. But keep in mind that if the algo will be popular among other projects - there is a possibility of being added there.
As a result, we come up with an algo that heavily relies on compute capabilities of chip and not dependant on the amount of GPU memory. The CN-GPU based FP32 math is the first of a kind mining algo in crypto world.

[hammuh]

I sometimes get booted from pool with latest linux version of JCE cpu miner. Am mining Turtlecoin to Steadyhash pool.

miner: jce_cn_cpu_miner.linux.033q.zip
os: ubuntu 16.04 & 18.04
log:
07:58:04 | Rejected by the pool in 54 ms.
07:58:04 | Connection failed: The pool kicked you out as Unauthenticated, its Difficulty 600023 is probably too high for your computing power. If the pool allows fixed Difficulty, fix it to a lower value.
07:58:04 | Connection interrupted, waiting 5s then retry, attempt #1
07:58:04 | Connection failed: Socket receive error: socket explicitly closed by the pool
07:58:04 | Connection interrupted, waiting 5s then retry, attempt #2
07:58:09 | Connecting to mining pool trtl.steadyhash.org:3853 ...
07:58:10 | Connecting to mining pool trtl.steadyhash.org:3853 ...
07:58:10 | Connected to pool. Now logging in...

Had 3 different ubuntu machines mining to same pool. When I woke up I saw it was at the ubuntu command line on all 3 machines instead of actually logging in.

Note that I got some windows machines on xmrig that don't seem to experience this issue.
Unsure if pool or jce is the cause.

[Lonnegan64]

Is it a quite weak machine? I had that problem a while ago with Monero and some older machines. The pool rised the difficulty higher and higher till the machine had no chance to return a hash in the given time. As a solution, I added the smallest allowed difficulty after the wallet address in the config file. With your pool it should be ".100000"

[hammuh]

Is it a quite weak machine? I had that problem a while ago with Monero and some older machines. The pool rised the difficulty higher and higher till the machine had no chance to return a hash in the given time. As a solution, I added the smallest allowed difficulty after the wallet address in the config file. With your pool it should be ".100000"

I'm using fixed difficulty, but I think the main problem is the linux JCE just goes to command line after IP ban instead of reconnecting. It should keep trying to reconnect to the pool.

[migo77]

Is it a quite weak machine? I had that problem a while ago with Monero and some older machines. The pool rised the difficulty higher and higher till the machine had no chance to return a hash in the given time. As a solution, I added the smallest allowed difficulty after the wallet address in the config file. With your pool it should be ".100000"

I'm using fixed difficulty, but I think the main problem is the linux JCE just goes to command line after IP ban instead of reconnecting. It should keep trying to reconnect to the pool.

hi, add --forever --keepalive to your cmd line when starting jce miner.

M/

[kissmarx]

JCE please note:

RYO is going to fork with a new algo "CN GPU": Fork Block: 228750 @ Feb 14th 2019 UTC 12.00

Github: https://github.com/ryo-currency/ryo-currency/pull/163
Testpool: https://tnpool.ryo-currency.com/

I'm also waiting with this one to work with JCE.

[JCE-Miner]

Hi all!

@Unclwish: i may have a fix for your crash, but not sure as I cannot reproduce. I need more tests.

Webchain and Hycon: as said previously, i really don't think i'll have time for them, as they are coin-specific non-standard CN forks. Look at SRB which supports them for GPU mining, and the xmrig forks for CPU.

CN-GPU: it's so different that's no longer CN-ish I think i'll add them but Monero v9 will be the high priority fork, since, as you may have observed, i've very very little dev time left this year. The long part is not to support the fork, but to provide extra speed, otherwise it's non-sense to get fees for the same speed as the reference, open-source miners. And optimizing assembly takes a lot of time.

pool kick: yes  --forever --keepalive is the way to keep connected.

[stsocrat]

Monero v9 is prior! We're waiting for it on cpu and gpu!

SRB is very unstable and love to crash the system.
Stack is unoptimized

Ryo was profitable only first 2 days after changing algo...

[NCarter84]

Will there be a patch/fix for CN-Turtle? It seems like the miner is considerably slow on this algo.

[Iamtutut]

Will there be a patch/fix for CN-Turtle? It seems like the miner is considerably slow on this algo.

I get 32KH/s with 4 RX574
I get 4,8KH/s with Ryzen 2400G

What's your setup and your HR ?

[NCarter84]

Will there be a patch/fix for CN-Turtle? It seems like the miner is considerably slow on this algo.

I get 32KH/s with 4 RX574
I get 4,8KH/s with Ryzen 2400G

What's your setup and your HR ?

I don't have the numbers off hand, I just remember testing the CPU one and it was 300-400 hs slower than XMRig.

I haven't tested it fully on my GPUs yet.

I assumed it was a release issue.

[NCarter84]

Will there be a patch/fix for CN-Turtle? It seems like the miner is considerably slow on this algo.

I get 32KH/s with 4 RX574
I get 4,8KH/s with Ryzen 2400G

What's your setup and your HR ?

Just did some testing, getting 3.5 khs on Turtle2... SRB is double that.

[Iamtutut]

Will there be a patch/fix for CN-Turtle? It seems like the miner is considerably slow on this algo.

I get 32KH/s with 4 RX574
I get 4,8KH/s with Ryzen 2400G

What's your setup and your HR ?

Just did some testing, getting 3.5 khs on Turtle2... SRB is double that.

What config ? What hardware ?

The speed I get is what was expected from turtlecoin devs.

[HardToComeBy]

CN-GPU: it's so different that's no longer CN-ish I think i'll add them but Monero v9 will be the high priority fork,
since, as you may have observed, i've very very little dev time left this year.

Everything is getting a fork it seems. Well understood you surely have stuff you have to do that isn't
about developing the miner, or even tech-related at all. Just wanted to say your work is appreciated.

Thank you.

[NCarter84]

Will there be a patch/fix for CN-Turtle? It seems like the miner is considerably slow on this algo.

I get 32KH/s with 4 RX574
I get 4,8KH/s with Ryzen 2400G

What's your setup and your HR ?

Just did some testing, getting 3.5 khs on Turtle2... SRB is double that.

What config ? What hardware ?

The speed I get is what was expected from turtlecoin devs.

Config is auto at the moment.. Mining on (5)470 and 570.

All other algos perform as expected.

[Iamtutut]

Set intensity to "1008" in config.txt (and call config.txt in your start.bat)

"gpu_threads_conf" :
[
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 3, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 3, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 4, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 4, "multi_hash": 1008},
],

Then if some GPUs can't handle it, lower the last number by steps of 16.

[NCarter84]

Set intensity to "1008" in config.txt (and call config.txt in your start.bat)

"gpu_threads_conf" :
[
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 0, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 1, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 2, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 3, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 3, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 4, "multi_hash": 1008},
   { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta" : 4, "index" : 4, "multi_hash": 1008},
],

Then if some GPUs can't handle it, lower the last number by steps of 16.

I'll give that a shot, I was hoping to avoid using custom configs... JCE is just as fast with auto settings as SRB is with custom threading.... I use a program that does alot of algo based mining (not just CN), so I'm trying to get away from custom and go more towards auto. (If that makes sense)

[Iamtutut]

I use 1240MHz for the core and 2020 to 2040MHz for the memory, may be you can try before using custom intensity.