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

[pbfarmer]

JC - can't even begin to say how impressed I am w/ this miner.  Breathed new life into my rigs - higher rates, lower power, more stable, a win on all fronts!

Couple of things I noticed, though haven't been a major concern. 
  i) the warmup sometimes leaves some of my 580 8gbs suboptimal for up to a couple hours, and it seems to be random which ones it happens to (different every start.)  Optimally they all run around 1130-1200, but sometimes a couple get left around 1K for a while.
  ii) i notice one 580 dropping to 1K mid-run for at least 30-60 min, but came back eventually.

Despite these issues, your miner is waaaaay more stable for the same settings than anything else I've run, even at lower power levels.  I think a big part is due to you not switching algos for the donation - I don't know why it's so hard for other people to understand how bad that can be.

Also, one request: Can you add a 'last share' timestamp per gpu?  Would help to visually identify stuck GPUs - not that I've encountered any yet w/ this

[wyzdic]

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 },

Thank you... Can you also share for Bittube?? Really appreciate...

This is mine for a ref 64 + 56 (flashed to 64), using latest miner (32q) and latest driver (18.9.3).  Getting ~2200 + 2150:

"gpu_threads_conf" :
[
  { "mode" : "GPU", "worksize" : 16, "alpha" : 128, "beta" : 16, "index" : 3, "multi_hash":1968 },
  { "mode" : "GPU", "worksize" : 16, "alpha" : 128, "beta" : 16, "index" : 3, "multi_hash":1968 },
  { "mode" : "GPU", "worksize" : 16, "alpha" : 128, "beta" : 16, "index" : 4, "multi_hash":1968 },
  { "mode" : "GPU", "worksize" : 16, "alpha" : 128, "beta" : 16, "index" : 4, "multi_hash":1968 },
],

Can you show your core/mem? 1408/1100?

[pbfarmer]

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 },

Thank you... Can you also share for Bittube?? Really appreciate...

This is mine for a ref 64 + 56 (flashed to 64), using latest miner (32q) and latest driver (18.9.3).  Getting ~2200 + 2150:

"gpu_threads_conf" :
[
  { "mode" : "GPU", "worksize" : 16, "alpha" : 128, "beta" : 16, "index" : 3, "multi_hash":1968 },
  { "mode" : "GPU", "worksize" : 16, "alpha" : 128, "beta" : 16, "index" : 3, "multi_hash":1968 },
  { "mode" : "GPU", "worksize" : 16, "alpha" : 128, "beta" : 16, "index" : 4, "multi_hash":1968 },
  { "mode" : "GPU", "worksize" : 16, "alpha" : 128, "beta" : 16, "index" : 4, "multi_hash":1968 },
],

Can you show your core/mem? 1408/1100?

1525/1145 @ 905 for the 64, 1500/1145 @ 915 for the 56. 

Haven't optimized them yet for this miner - these are settings from stak / cast, and i feel like they can do better now, at least maybe lower power.


EDIT: sorry, just realized OP asked for bittube (saber)... these are for cn7

[kostepanych2]

Hi,
The latest GPU miner is jce_cn_gpu_miner.032q.zip?
On the first post of this thread the latest is 032p version.

[Lermite]

The latest GPU miner is jce_cn_gpu_miner.032q.zip?
On the first post of this thread the latest is 032p version.

What matter are the available versions on the Github page: https://github.com/jceminer/cn_gpu_miner

[Mashy81]

Has anyone tried this miner on threadripper 2950x.

[vmozara]

Has anyone tried this miner on threadripper 2950x.

Search for Threadripper, ther was a topic around. Not sure about 2950x but somebody had 2990WX at 2.4 KH/s (number from my head, not sure)

[heavyarms1912]

1525/1145 @ 905 for the 64, 1500/1145 @ 915 for the 56. 

Haven't optimized them yet for this miner - these are settings from stak / cast, and i feel like they can do better now, at least maybe lower power.


EDIT: sorry, just realized OP asked for bittube (saber)... these are for cn7

I am guessing the voltage is higher than 910-915 and most likely that's consuming a lot more power for those extra 100 H/s. 
Can you check the actual core voltage while mining using HWInfo64 tool.

[pbfarmer]

1525/1145 @ 905 for the 64, 1500/1145 @ 915 for the 56.  

Haven't optimized them yet for this miner - these are settings from stak / cast, and i feel like they can do better now, at least maybe lower power.


EDIT: sorry, just realized OP asked for bittube (saber)... these are for cn7

I am guessing the voltage is higher than 910-915 and most likely that's consuming a lot more power for those extra 100 H/s.  
Can you check the actual core voltage while mining using HWInfo64 tool.

Heh -  I'm a PPT veteran - been running these vegas for almost a year

.875-.894 / .887-.906.  Generally 160-170 at wall.

[coke15]

hi jes'

jce will automaticatly change algo on the fork or not?

maybe with optimisation,we don't loose 10%?

32p version??

[HardKano]

Q. How much cost the fees?
Current fees are:

    3.0% when using at least one mining thread with non-AES architecture, or 32-bits
    1.5% when using only 64-bits AES architecture
    0.9% when using GPU

The fees are twice higher in non-AES mode and/or 32-bits because JCE offers a huge performance gain here.

Hi ! nice miner i tried it local yesterday before planing to put it on my rigs. Before it i would like to know how devfees works ? Is it like Claymore and you connect to your pool from time to time for few secs/mins ? i've not seen anything on my test yesterday.

Thanks.

[HardKano]

Q. How much cost the fees?
Current fees are:

    3.0% when using at least one mining thread with non-AES architecture, or 32-bits
    1.5% when using only 64-bits AES architecture
    0.9% when using GPU

The fees are twice higher in non-AES mode and/or 32-bits because JCE offers a huge performance gain here.

Hi ! nice miner i tried it local yesterday before planing to put it on my rigs. Before it i would like to know how devfees works ? Is it like Claymore and you connect to your pool from time to time for few secs/mins ? i've not seen anything on my test yesterday.

Thanks.

Found my answer on pages 53 and 58. Thanks !

Will work on miner automatic restart after watchdog close it

My 12 rx580 working on your miner ! All pretty fine ! Thanks.

[pbfarmer]

Q. How much cost the fees?
Current fees are:

    3.0% when using at least one mining thread with non-AES architecture, or 32-bits
    1.5% when using only 64-bits AES architecture
    0.9% when using GPU

The fees are twice higher in non-AES mode and/or 32-bits because JCE offers a huge performance gain here.

Hi ! nice miner i tried it local yesterday before planing to put it on my rigs. Before it i would like to know how devfees works ? Is it like Claymore and you connect to your pool from time to time for few secs/mins ? i've not seen anything on my test yesterday.

Thanks.

Found my answer on pages 53 and 58. Thanks !

Will work on miner automatic restart after watchdog close it

My 12 rx580 working on your miner ! All pretty fine ! Thanks.

for an auto-restart, you just need a label definition before the miner, and a goto after.  I.e.:

Code:

:minerStart

jce_cn_gpu_miner64.exe ...

timeout /t 10
goto minerStart

[HardKano]

for an auto-restart, you just need a label definition before the miner, and a goto after.  I.e.:

Code:

:minerStart

jce_cn_gpu_miner64.exe ...

timeout /t 10
goto minerStart

Ha thanks for the reply !  Will test it when I go back home in 2 days.

[HardKano]

Pretty solid Miner JCE ! I have not yet fine tuned my 12 rx580 with your miner and already got 1kh increase in the 24h avg chart !

[christiano88]

I've got a problem with the warm-up on my RX580s, not all cards in a sistem end up at full optimal speed after the warmup on heavy/haven/saber. This happens even if I have gpu-z in the background (which adds another 15h/s per card fluctuation after the warmup). I am on "p" version right now, on "n" version I thought it did much better, but wanted to use refined watchdog and get a small boost in mining speed with the latest version. What am I doing wrong?
I use 976 intensity, happens with lower intensity too. If I turn off a card that has optimal speed after warmup, and turn it back on, it has 15% less speed and doesn't get back up to optimal. Something needs to be reworked in the handling of the warmup, I also see a VRAM cluttering, an 8gb cards ends up showing it has 11gb of vram used in gpu-z (maybe bug?). Maybe we need some way to flush the vram and this is what's causing it, especially for those that restart the miner quite often (automatic profit switchers).

[UnclWish]

I've got a problem with the warm-up on my RX580s, not all cards in a sistem end up at full optimal speed after the warmup on heavy/haven/saber. This happens even if I have gpu-z in the background (which adds another 15h/s per card fluctuation after the warmup). I am on "p" version right now, on "n" version I thought it did much better, but wanted to use refined watchdog and get a small boost in mining speed with the latest version. What am I doing wrong?
I use 976 intensity, happens with lower intensity too. If I turn off a card that has optimal speed after warmup, and turn it back on, it has 15% less speed and doesn't get back up to optimal. Something needs to be reworked in the handling of the warmup, I also see a VRAM cluttering, an 8gb cards ends up showing it has 11gb of vram used in gpu-z (maybe bug?). Maybe we need some way to flush the vram and this is what's causing it, especially for those that restart the miner quite often (automatic profit switchers).

What system and drivers you're use? On Windows 10 and latest drivers max intensity on heavy is 944. Even 960 gives significant drop in speed. So as launched GPU-Z... It didn't add speed, but it can decrease it...

[christiano88]

I've got a problem with the warm-up on my RX580s, not all cards in a sistem end up at full optimal speed after the warmup on heavy/haven/saber. This happens even if I have gpu-z in the background (which adds another 15h/s per card fluctuation after the warmup). I am on "p" version right now, on "n" version I thought it did much better, but wanted to use refined watchdog and get a small boost in mining speed with the latest version. What am I doing wrong?
I use 976 intensity, happens with lower intensity too. If I turn off a card that has optimal speed after warmup, and turn it back on, it has 15% less speed and doesn't get back up to optimal. Something needs to be reworked in the handling of the warmup, I also see a VRAM cluttering, an 8gb cards ends up showing it has 11gb of vram used in gpu-z (maybe bug?). Maybe we need some way to flush the vram and this is what's causing it, especially for those that restart the miner quite often (automatic profit switchers).

What system and drivers you're use? On Windows 10 and latest drivers max intensity on heavy is 944. Even 960 gives significant drop in speed. So as launched GPU-Z... It didn't add speed, but it can decrease it...

I am on Win10 1709 + blockchain beta drivers.

[UnclWish]

I've got a problem with the warm-up on my RX580s, not all cards in a sistem end up at full optimal speed after the warmup on heavy/haven/saber. This happens even if I have gpu-z in the background (which adds another 15h/s per card fluctuation after the warmup). I am on "p" version right now, on "n" version I thought it did much better, but wanted to use refined watchdog and get a small boost in mining speed with the latest version. What am I doing wrong?
I use 976 intensity, happens with lower intensity too. If I turn off a card that has optimal speed after warmup, and turn it back on, it has 15% less speed and doesn't get back up to optimal. Something needs to be reworked in the handling of the warmup, I also see a VRAM cluttering, an 8gb cards ends up showing it has 11gb of vram used in gpu-z (maybe bug?). Maybe we need some way to flush the vram and this is what's causing it, especially for those that restart the miner quite often (automatic profit switchers).

What system and drivers you're use? On Windows 10 and latest drivers max intensity on heavy is 944. Even 960 gives significant drop in speed. So as launched GPU-Z... It didn't add speed, but it can decrease it...

I am on Win10 1709 + blockchain beta drivers.

I'm understand now... On latest 1803 launching GPU-Z didn't nothing except freezes during mining... And on latest driver max stable intensity is 944 on heavy algo and 8Gb vmem...

[freedom777]

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

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 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

Hi, JCE! I want to send you a personal message with your permission! This is important.