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

[polsska]

I tried now on my home pc with Vega 64 and hashrate went from 2200 to about 1550 I tried mining wownero

Did you read what the author wrote about this version?

By the way, on the same settings - wownero v8 on RX550 2GB (Win 10 "64bit 1809", drivers 18.10.1) -  260 h/s,
 monero v7 - 530 h/s

[vmozara]

I tried now on my home pc with Vega 64 and hashrate went from 2200 to about 1550 I tried mining wownero

Did you read what the author wrote about this version?

By the way - wownero v8 on RX550 2GB (Win 10 "64bit 1809", drivers 18.10.1) -  260 h/s,
 monero v7 - 530 h/s

No  I just downloaded. I go to see 

[Nightworker88]

Hello JCE- Miner


last days i tried your really awesome cpu miner! -on all of my rigs -perfect hash!!

 -- sorry for Mr. Claymore, i was using all his miners now for years,  cpu and amd, but he nearly stopped developing .......

want use from now on your GPU Miner, but i am an technician engineer, know a lot of ms windows and server, but i am not for programming ...

SO my first important questions:

1.) which drivers do you recommend to use, i have only R9 290(x) 4GB (some 8 GB) -i used Crimson 15.12, cause of Mr. Claymore suggestion ( tried Adrenalin 18.6.1, less hash)
2.) with auto config i get about 120-150 hash less on V7 than on Claymore`s Crypto.

  any idea what could i try in a config file?? (last two days i tried a lot, but i am sure i made more wrong than i checked!)

thanks much - have really "some" rigs and would really like to change for your miner, but difference in the end is big with auto settings and now i just gave up, my head is smoking

[JCE-Miner]

Hi all!

I read the status:
* CPU version works fine
* GPU on RX and Vega works. Not optimized yet, and speed is terrible on RX550 as you report, but it works.
* GPU compile hangs on old cards

I'll have very very little dev time until end of this month, i'll do my best to fix the Pitcairn/older cards version but not sure at all. And i'll be away of my rigs, with remote debugging not on option (remote bench is possible, but not remote dev which implies sending clear code through network).
Considering how i had to rush the gpu version, it's not that bad.
I add a warning in the GPU doc telling the V8 may hang on older cards.

JCE has no autoswitch yet, at the moment of the fork, you'll have to stop it, remove the --variation 3, and restart it.

@Nightworker88:
The GPU autoconfig aims at being safe but is not optimal, try to play with the parameter multi_hash, alpha and beta to get optimal performance. The GPU doc
https://github.com/jceminer/cn_gpu_miner
provides some example, but they are still for Monero v7
For CPU, autoconfig aims for absolute performance.

to use a manual config, remove any parameter --auto and add - c config.txt with config.txt being your configuration file. The package comes with an example.
Be careful, if you use a manual config, you'll have to set the CPU config manually too.

Does it means that after the fork V7 stops to works and v8 will be instead of it? What about heavy and other v7/cryptonight childs algos?

On Monero currency, yes, but that's a Monero affair. For JCE, V8 is just yet another fork, number 15, other coins that remain on V7 like Graft will be mineable as-is with no change. Heavy, Turtle, Bittube are not concerned, they stay on their respective algo, and are still mineable with JCE 0.33

One question arises: what to do with the marketplaces like Nicehash? I currently default them to V7, but I should switch them to V8 by default in a near future.

[wyzdic]

Hi all!

I read the status:
* CPU version works fine
* GPU on RX and Vega works. Not optimized yet, and speed is terrible on RX550 as you report, but it works.
* GPU compile hangs on old cards

I'll have very very little dev time until end of this month, i'll do my best to fix the Pitcairn/older cards version but not sure at all. And i'll be away of my rigs, with remote debugging not on option (remote bench is possible, but not remote dev which implies sending clear code through network).
Considering how i had to rush the gpu version, it's not that bad.
I add a warning in the GPU doc telling the V8 may hang on older cards.

JCE has no autoswitch yet, at the moment of the fork, you'll have to stop it, remove the --variation 3, and restart it.

@Nightworker88:
The GPU autoconfig aims at being safe but is not optimal, try to play with the parameter multi_hash, alpha and beta to get optimal performance. The GPU doc
https://github.com/jceminer/cn_gpu_miner
provides some example, but they are still for Monero v7
For CPU, autoconfig aims for absolute performance.

to use a manual config, remove any parameter --auto and add - c config.txt with config.txt being your configuration file. The package comes with an example.
Be careful, if you use a manual config, you'll have to set the CPU config manually too.

Does it means that after the fork V7 stops to works and v8 will be instead of it? What about heavy and other v7/cryptonight childs algos?

On Monero currency, yes, but that's a Monero affair. For JCE, V8 is just yet another fork, number 15, other coins that remain on V7 like Graft will be mineable as-is with no change. Heavy, Turtle, Bittube are not concerned, they stay on their respective algo, and are still mineable with JCE 0.33

One question arises: what to do with the marketplaces like Nicehash? I currently default them to V7, but I should switch them to V8 by default in a near future.

V8 is very bad for Vega
Vega64 only have 15xx h/s
Use SRB have 20xx h/s

[JCE-Miner]

I know the performances are bad, i didn't even optimize it, i use the reference implementation from Monero. I rushed to provide a version that just works on common cards before the fork, but that's a very bad timing for me as i've almost no time to dev until november.
The CPU version however has been optimized and should be the fastest miner in all cases.

[Uaciuganadu]

Hello,

Any ideas why this is failing? Only with the latest version.

Code:

18:40:06 | Connecting to mining pool killallasics.moneroworld.com:7777 ...
18:40:06 | Fonero (FNO) Mining session starts!

During mining time, press:
 h      display hashrate for each mining thread.
 r      display full report.
 p      pause all.
 u      pause CPUs.
 0-F    pause GPU 0-15.
 t      GPU temperature and fan speed.
 q      quit.

18:40:06 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
18:40:06 | during this time, the hashrate may be unstable and inconsistent.
18:40:06 | Let the miner warm-up if you're tuning for performance.
18:40:06 | Connected to pool. Now logging in...
18:40:06 | Successfuly logged as 9v4vTVwqZzfjCFyPi7b9Uv1hHntJxycC4XvRyEscqwtq8aycw5xGpTxFyasurgf2KRBfbdAJY4AVcemL1JCegXU4EZfMtaz
18:40:06 | Pool changes Difficulty to 10000.
Abort was called at 318 line in file:
D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp
Press any key to continue . . .

[UnclWish]

I know the performances are bad, i didn't even optimize it, i use the reference implementation from Monero. I rushed to provide a version that just works on common cards before the fork, but that's a very bad timing for me as i've almost no time to dev until november.
The CPU version however has been optimized and should be the fastest miner in all cases.

Yes, v8 works but speed is low... Now it's need optimizations...
On nicehash exists so v7 as v8... But profit on v8 is very-very low yet...
Maybe on nicehash you make auto-chosing of algo due to adress pointed to connect? This would be pretty nice... If I point cryptonightv7.eu.nicehash.com I can mine only v7 not any other algo...

[UnclWish]

Version GPU 0.33a didn't compiles kernel for v8 for Pitcairn 270X 4Gb card. No errors, just hangs on building kernel for thread 1.
For other algos all wroks fine...

[JCE-Miner]

@Uaciuganadu:
What GPU do you use?
Don't forget to add parameter --variation 15 to mine v8, in case you hadn't did it.

Pitcairn: other already reported the Pitcairn compile fails, I documented it on the Github page, but cannot fix yet, as I said, i'm away from my rigs until november. That fork is a very bad timing for me. I barery had time to test the OpenCL, and had just none to optimize.

Even when it works, the performance of the code, which is not mine but the naive reference one, is very very bad, as expected.

[heavyarms1912]

@Uaciuganadu:
What GPU do you use?
Don't forget to add parameter --variation 15 to mine v8, in case you hadn't did it.

Pitcairn: other already reported the Pitcairn compile fails, I documented it on the Github page, but cannot fix yet, as I said, i'm away from my rigs until november. That fork is a very bad timing for me. I barery had time to test the OpenCL, and had just none to optimize.

Even when it works, the performance of the code, which is not mine but the naive reference one, is very very bad, as expected.

Get similar error.  --variation 15 is set.
Tested on killallasics.moneroworld.com pool which is v8 ready.

Pool worked on xmr-stak.

[JCE-Miner]

I know it's not because of the pool

I added a big warning in the Github doc to state the GPU v8 is just not usable as-is, it rarely works, and when it does, it's very very slow.
I'm wondering if it was a good idea to provide such an unfinished version. I had choice between being 2 weeks late or provide a broken code. Two bad choices.
I could have reversed the status by making the GPU version first, and disable the double-check, but the CPU version is what defined JCE as the fastest miner so I gave it the priority.

online is the
GPU 0.33b

No more fees on paused CPUs
The GPU init on Windows 7 now displays a clear message instead of garbage symbols
Warmup restarts after a long pause on GPU (because of pause or disconnect)

that's a bunch of little fixes i planned before, and it fixes nothing about the bad v8

[QuirkSilver]

obvious new monero algo uses more compute. rx 560 2gb will shine here, where 550 will struggle. optimum miners making use of compute cores utilization efficiently will result in more hash for less electricity.
Anyway, sounds like a big thing for FPGAs but also acorn (afaik acorn accelerators does computational work way faster? as in more power savings for v8)

[UnclWish]

Tested v8 on 64-bit CPU's. On AMD FX8320 and Core i3 6100... Noticed significant drop in speed compared with v7 with the same config... About 25-30% less...

[Uaciuganadu]

@Uaciuganadu:
What GPU do you use?
Don't forget to add parameter --variation 15 to mine v8, in case you hadn't did it.

Pitcairn: other already reported the Pitcairn compile fails, I documented it on the Github page, but cannot fix yet, as I said, i'm away from my rigs until november. That fork is a very bad timing for me. I barery had time to test the OpenCL, and had just none to optimize.

Even when it works, the performance of the code, which is not mine but the naive reference one, is very very bad, as expected.

Same GPU`s as before 2Vega and one rx580, but the 33 version is broken for me on both v7 and v8.

Code:

13:49:44 | Pool changes Difficulty to 64000.
Abort was called at 318 line in file:
D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp
Press any key to continue . . .

I will have to switch to something else till November or when you get the time to debug the code again.

[UnclWish]

@Uaciuganadu:
What GPU do you use?
Don't forget to add parameter --variation 15 to mine v8, in case you hadn't did it.

Pitcairn: other already reported the Pitcairn compile fails, I documented it on the Github page, but cannot fix yet, as I said, i'm away from my rigs until november. That fork is a very bad timing for me. I barery had time to test the OpenCL, and had just none to optimize.

Even when it works, the performance of the code, which is not mine but the naive reference one, is very very bad, as expected.

Same GPU`s as before 2Vega and one rx580, but the 33 version is broken for me on both v7 and v8.

Code:

13:49:44 | Pool changes Difficulty to 64000.
Abort was called at 318 line in file:
D:\qb\workspace\19992\src\vpg-compute-neo\runtime\os_interface\windows\wddm.cpp
Press any key to continue . . .

I will have to switch to something else till November or when you get the time to debug the code again.

On my RX580 v8 works normal, except low speed. Try to launch only RX 580... Or check port of pool and variation of algo...

[coke15]

hi jes'

hum version 0.33B  en v8 ,on rig 5x570  2800h/s?
in v7 :4500h/s   in v8 with xmrig 4100h/s

i use the same config.txt:
{ "mode" : "GPU", "worksize" : 4, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":880 },
{ "mode" : "GPU", "worksize" : 4, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":880 },

?

[Rock and Paper]

Whats the recommended driver? im using 18.9.3 and my rig freezes.

i have mix gpu in my system, 3 x 580, 2 x 570, 1 x 470, 1 x r9 Fury and 2 x Nvidia 1070.

Using win 1709, any one can help me with freeze problem.

[frozen80]

Whats the recommended driver? im using 18.9.3 and my rig freezes.

i have mix gpu in my system, 3 x 580, 2 x 570, 1 x 470, 1 x r9 Fury and 2 x Nvidia 1070.

Using win 1709, any one can help me with freeze problem.

You should try 18.6.1

[JCE-Miner]

hum version 0.33B  en v8 ,on rig 5x570  2800h/s?
in v7 :4500h/s   in v8 with xmrig 4100h/s

Same answer as before: v8 GPU in JCE is very unfinished, and either fails to start or mines very slow. I just ran out of time and now i've no access to any decent dev env to finish it. As crazy as it sounds, I cannot even run my own GPU miner, i'm writting right now from a decade old laptop, in the middle of nowhere. I put as many warnings as I could on the Github page, and cannot do anything more for now. I may provide non-openCL related fixes meanwhile, but the v8 will remain bad until november. I won the race against time for CPU, but lost for GPU

The only good thing is that the perf problem is consistent for all who could have make it run, and same for the Pitcairn hang at startup, so once i'm back to my rigs, fixing should be easy.

and my rig freezes.

If you're trying v8 GPU, just give up until I release a decent version in ~2 weeks. The current code is just not usable as-is. Sorry for such a long delay. You can still use the CPU part that runs fine.
If that's on V7 or other, use a manual configuration and lower the multi_hash parameter. Lowering parameter worksize from 8 to 4 sometimes helps too.