Pages:
Author

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

full member
Activity: 729
Merit: 114

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.
member
Activity: 190
Merit: 59
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)
jr. member
Activity: 225
Merit: 1
Has anyone tried this miner on threadripper 2950x.
newbie
Activity: 54
Merit: 0
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
full member
Activity: 1274
Merit: 105
Hi,
The latest GPU miner is jce_cn_gpu_miner.032q.zip?
On the first post of this thread the latest is 032p version.
member
Activity: 340
Merit: 29
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
newbie
Activity: 46
Merit: 0
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?
member
Activity: 340
Merit: 29
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! Smiley

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 Smiley
member
Activity: 340
Merit: 29
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 },
],

EDIT: sorry... these are for cn7.  But why waste a vega on heavy or variants right now?  Unless prices for TUBE or RYO or whatever come waaaay up, Vegas are better suited to cn7 coins (XMR).
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.

Which driver do you use?
Card installed with RX 580 cards. So I always install latest driver. Now it's 18.9.3.
And I noticed that for Pitcairn R9 270X driver version didn't affects on speed at all. I checked this allready about 2 yaers and allways update driver. No one didn't change speed on 270X card.
full member
Activity: 191
Merit: 100
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.

Which driver do you use?
newbie
Activity: 39
Merit: 0

Hey!

I cannot give any precise number, even if the official Monero dev says about -10%.

What's new in V8:
* The tweak on variable B after the AES is removed
* But replaced by a simple XOR
* There's a new 64 bits divide/remain
* There's a new square root
* There's a new 64-bits multiply
* There are three new accesses to the scratchpad
* The main loop now have variables A, B, C and new D, while previous had only A and B, C being a temporary. It doubles the need of registers.

So i expect it to be a bit slower on 64-bits CPU since they have enough registers to handle all this, and the 64-bits divide/remain and the squareroot are all native instructions.
On 32-bits, there will be a higher performance drop, i expect, since they will run out of registers.
On GPU, both the divide and the triple access to Memory will have a big impact, i expect. Not benched yet. Because GPU memory is always asynch and such accesses to VRAM cost a lot of time. It will increase the gap between good and bad memory-equipped cards, and tighten the performance gap on cards having the same memory controller, like RX550 against RX560

Again, all this is theorical impact, i haven't finished my assembly implementation. When done i'll release the 0.33 for Windows and Linux CPU first, then the GPU version.

Really good to know you are on top of it. But can you tell us what gains you get from doing it in assembly ?
newbie
Activity: 15
Merit: 0
How to set the next pool when the current pool is disconnected / error? (not by minutes)
member
Activity: 350
Merit: 22
Hey JCE,

Can you estimate how much of a hash-rate drop we will have on CNv2?

Thank You!



Hey!

I cannot give any precise number, even if the official Monero dev says about -10%.

What's new in V8:
* The tweak on variable B after the AES is removed
* But replaced by a simple XOR
* There's a new 64 bits divide/remain
* There's a new square root
* There's a new 64-bits multiply
* There are three new accesses to the scratchpad
* The main loop now have variables A, B, C and new D, while previous had only A and B, C being a temporary. It doubles the need of registers.

So i expect it to be a bit slower on 64-bits CPU since they have enough registers to handle all this, and the 64-bits divide/remain and the squareroot are all native instructions.
On 32-bits, there will be a higher performance drop, i expect, since they will run out of registers.
On GPU, both the divide and the triple access to Memory will have a big impact, i expect. Not benched yet. Because GPU memory is always asynch and such accesses to VRAM cost a lot of time. It will increase the gap between good and bad memory-equipped cards, and tighten the performance gap on cards having the same memory controller, like RX550 against RX560

Again, all this is theorical impact, i haven't finished my assembly implementation. When done i'll release the 0.33 for Windows and Linux CPU first, then the GPU version.
newbie
Activity: 39
Merit: 0
Hey JCE,

Can you estimate how much of a hash-rate drop we will have on CNv2?

Thank You!

newbie
Activity: 46
Merit: 0
How to check reported hash rate on other miners at minexmr.com?

It is difficult for me to compare miners on that pool.

Thanks

You can use WALLET.workerID+DIFF
newbie
Activity: 15
Merit: 0
How to check reported hash rate on other miners at minexmr.com?

It is difficult for me to compare miners on that pool.

Thanks
newbie
Activity: 10
Merit: 0
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...
sr. member
Activity: 1484
Merit: 253
how do i set difficulty for algo using jce gpu miner please?

Usually it's not miner settings. It must be set via pool adress or wallet name. Maybe via password. Look at your pool settings.
newbie
Activity: 19
Merit: 0
how do i set difficulty for algo using jce gpu miner please?
Pages:
Jump to: