guys! i recently got a rx550, 2gb. Any idea if i can get more than 300h/s on cn-heavy? 
No, 2Gb too small amount to have normal speed on cn-heavy. You can increase speed only by use overclocking and editing memory straps in bios. 
Topic: [XMR] JCE Miner Cryptonight/forks, now with GPU! - page 42. (Read 90841 times)
Can someone help? My RX470 4GB cards cant start at all...When i start my miner at the very start my rig crash every time. I tried --auto mode and its the same. Change the setting of my cards and its still the same....THE ONLY rig that work have RX480 8GB cards ..... Using 18.5.1 and 1803win edition 60Gig virtual mem. Anyone with same problem like me?
your problem I guess is the same with _ap_ which is in auto mode 4GB GPU have 2 thread and multi_hash 864, so better use manual config 4GB GPU 1 thread multi_hash 944 or 2 thread but multi_hash 472.
Tnx it worked but now my main GPU always crash.... Do you think if i set the integrated gpu from the cpu for main gpu gonna help? Thank you again!
You win gold metal for honesty and modesty. 
TR miner seems to be really strong at new CN. I have big issues getting it running on every rig, but where it works, it works good and pool side hashrate seems to be correct as well.
TR miner seems to be really strong at new CN. I have big issues getting it running on every rig, but where it works, it works good and pool side hashrate seems to be correct as well.
I can recognize when a dev is good, and they are.
They are two people, which is a important point for time. Look how i messed up with the CNv8 deadline because i was away at the wrong time. May have had a buddy dev, it wouldn't have happended. Two people specialized on cn-v8 for RX/vega against me, alone, having to support CPU aes, and non-aes, 32 and 64 bits, and GPU... I cannot win.
I may specialize in older cards they don't support, or just give up all GPUs. But +5% is a huge gap, i don't think I can fill it up.
Still need to bench the real hashrate, after all Claymore 11 was also +5% on screen, but -5% on pool. But beating ROCm with OpenCL is hardly possible.
They are two people, which is a important point for time. Look how i messed up with the CNv8 deadline because i was away at the wrong time. May have had a buddy dev, it wouldn't have happended. Two people specialized on cn-v8 for RX/vega against me, alone, having to support CPU aes, and non-aes, 32 and 64 bits, and GPU... I cannot win.
I may specialize in older cards they don't support, or just give up all GPUs. But +5% is a huge gap, i don't think I can fill it up.
Still need to bench the real hashrate, after all Claymore 11 was also +5% on screen, but -5% on pool. But beating ROCm with OpenCL is hardly possible.
many thanks, it's working now!
what steps recommend increase the multi hash? 580 hashrate is very good (prev miner: 930H/s, jce now: 1030H/s), but the 570 a little bit slow (prev miner: 760H/s, jce now: 680H/s)
All, as I thought... Miner used settings for 8gb card on 4gb card...what steps recommend increase the multi hash? 580 hashrate is very good (prev miner: 930H/s, jce now: 1030H/s), but the 570 a little bit slow (prev miner: 760H/s, jce now: 680H/s)
Optimal settings... For 8Gb try
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":944 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":944 },
for 4Gb:
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":472 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":472 },
If with 472 will be error try one of 472 lower to 464.
Thanks. I will try..
not fixed yet, the b3 version was to fix the driver 14 bug.
i just took a look at TeamRedMiner, and… wow they did a nice job. looks like the new Claymore grade miner.
i'll do more benches but if i'm too far behind in both consumption and speed, i'll give up the GPU version and focus back to CPU, where i provide the best miner. i may have beaten SRB OpenCL but they use ROCm GCN assembly, a domain i'm not that good.
somehow they did like i did for non-aes cpu, write ultra-optimized assembly that is far faster than anything else.
2.5% fees is high but they worth it.
i just took a look at TeamRedMiner, and… wow they did a nice job. looks like the new Claymore grade miner.
i'll do more benches but if i'm too far behind in both consumption and speed, i'll give up the GPU version and focus back to CPU, where i provide the best miner. i may have beaten SRB OpenCL but they use ROCm GCN assembly, a domain i'm not that good.
somehow they did like i did for non-aes cpu, write ultra-optimized assembly that is far faster than anything else.
2.5% fees is high but they worth it.
Yeah - teamred is pretty impressive on cnv2. I benched against srb and your b2 version on a few vegas, and they came out well ahead (~ 5%) for similar power draw, even after that massive fee. Anything in b3 that would be worth benching? Still loving your miner for CPU and heavy & variants on GPU, but b2 was still lagging srb for cnv2, which is now itself lagging teamred :|
One issue i do have w/ TR - cnv2 seems to cause occasional massive power spikes, and their miner seems to have made it even worse - so much so that their mean and median power draw has diverged significantly. Their reporting could be better too...
not fixed yet, the b3 version was to fix the driver 14 bug.
i just took a look at TeamRedMiner, and… wow they did a nice job. looks like the new Claymore grade miner.
i'll do more benches but if i'm too far behind in both consumption and speed, i'll give up the GPU version and focus back to CPU, where i provide the best miner. i may have beaten SRB OpenCL but they use ROCm GCN assembly, a domain i'm not that good.
somehow they did like i did for non-aes cpu, write ultra-optimized assembly that is far faster than anything else.
2.5% fees is high but they worth it.
i just took a look at TeamRedMiner, and… wow they did a nice job. looks like the new Claymore grade miner.
i'll do more benches but if i'm too far behind in both consumption and speed, i'll give up the GPU version and focus back to CPU, where i provide the best miner. i may have beaten SRB OpenCL but they use ROCm GCN assembly, a domain i'm not that good.
somehow they did like i did for non-aes cpu, write ultra-optimized assembly that is far faster than anything else.
2.5% fees is high but they worth it.
I got that fault when my intensity was too high. Try to lower it just to see if it works, then tune
Hey JCE,
Issue still persists!:
Issue still persists!:
Code:
For Windows 64-bits
Analyzing Processors topology...
Intel(R) Celeron(R) CPU G3930 @ 2.90GHz
Assembly codename: generic_aes
SSE2 : Yes
SSE3 : Yes
SSE4 : Yes
AES : Yes
AVX : No
AVX2 : No
Found CPU 0, with:
L1 Cache: 32 KB
L2 Cache: 256 KB
L3 Cache: 2048 KB, shared with CPU 1
Found CPU 1, with:
L1 Cache: 32 KB
L2 Cache: 256 KB
L3 Cache: 2048 KB, shared with CPU 0
Detecting OpenCL-capable GPUs...
Found GPU 0, with:
Vendor: Intel
Processor: Intel(R) HD Graphics 610
Device: ff:ff
Compute-Units: 12
Cache Memory: 256 KB
Local Memory: 64 KB
Global Memory: 1592 MB
Addressing: 64-bits
Found GPU 1, with:
Vendor: AMD
Processor: Ellesmere
Device: 06:00
Compute-Units: 36
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8192 MB
Addressing: 64-bits
Found GPU 2, with:
Vendor: AMD
Processor: gfx900
Device: 09:00
Compute-Units: 64
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8176 MB
Addressing: 64-bits
Found GPU 3, with:
Vendor: AMD
Processor: gfx900
Device: 03:00
Compute-Units: 64
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8176 MB
Addressing: 64-bits
Preparing 7 Mining Threads...
+-- Thread 0 config ------------------------+
| Run on CPU: 0 |
| Use cache: yes |
| Multi-hash: no |
| Assembly module: generic_aes |
+-------------------------------------------+
+-- Thread 1 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 2 config ------------------------+
| Run on GPU: 1 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 3 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 4 config ------------------------+
| Run on GPU: 2 |
| Multi-hash: 1984 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 5 config ------------------------+
| Run on GPU: 0 |
| Multi-hash: 1120 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
+-- Thread 6 config ------------------------+
| Run on GPU: 0 |
| Multi-hash: 1120 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 8 |
+-------------------------------------------+
Cryptonight Variation: Cryptonight V8 fork of Oct-2018
Low intensity.
Starting CPU Thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0000000008400000
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 0 of NUMA node 0 at: 0000000008600000
Starting GPU Thread 1, on GPU 1
Created OpenCL Context for GPU 1 at 0000000007d644b0
Created OpenCL Thread 1 Command-Queue for GPU 1 at 0000000007d64610
Scratchpad Allocation success for OpenCL Thread 1
Allocating big 3968MB scratchpad for OpenCL Thread 1...
Compiling kernels of OpenCL Thread 1...
Kernels of OpenCL Thread 1 compiled.
Starting GPU Thread 2, on GPU 1
Created OpenCL Thread 2 Command-Queue for GPU 1 at 000000000d18a620
Scratchpad Allocation success for OpenCL Thread 2
Allocating big 3968MB scratchpad for OpenCL Thread 2...
Compiling kernels of OpenCL Thread 2...
Kernels of OpenCL Thread 2 compiled.
Starting GPU Thread 3, on GPU 2
Created OpenCL Context for GPU 2 at 0000000007f1ff40
Created OpenCL Thread 3 Command-Queue for GPU 2 at 00000000118530b0
Scratchpad Allocation success for OpenCL Thread 3
Allocating big 3968MB scratchpad for OpenCL Thread 3...
Compiling kernels of OpenCL Thread 3...
Kernels of OpenCL Thread 3 compiled.
Starting GPU Thread 4, on GPU 2
Created OpenCL Thread 4 Command-Queue for GPU 2 at 0000000011852b70
Scratchpad Allocation success for OpenCL Thread 4
Allocating big 3968MB scratchpad for OpenCL Thread 4...
Compiling kernels of OpenCL Thread 4...
Kernels of OpenCL Thread 4 compiled.
Starting GPU Thread 5, on GPU 0
Created OpenCL Context for GPU 0 at 000000001160b0b0
Created OpenCL Thread 5 Command-Queue for GPU 0 at 0000000011598020
Scratchpad Allocation success for OpenCL Thread 5
Allocating big 2240MB scratchpad for OpenCL Thread 5...
Compiling kernels of OpenCL Thread 5...
Kernels of OpenCL Thread 5 compiled.
Starting GPU Thread 6, on GPU 0
Created OpenCL Thread 6 Command-Queue for GPU 0 at 0000000011598190
Scratchpad Allocation success for OpenCL Thread 6
Allocating big 2240MB scratchpad for OpenCL Thread 6...
Compiling kernels of OpenCL Thread 6...
Kernels of OpenCL Thread 6 compiled.
Keep-Alive enabled
Devfee for CPU is 1.5%
Devfee for GPU is 0.9%
21:01:42 | MoneroOcean 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.
21:01:42 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
21:01:42 | during this time, the hashrate may be unstable and inconsistent.
21:01:42 | Let the miner warm-up if you're tuning for performance.
21:01:43 | Connecting to mining pool gulf.moneroocean.stream:10064 ...
21:01:43 | Connected to pool. Now logging in...
21:01:44 | Successfuly logged as //PRIVATE INFO//
21:01: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 . . .
guys! i recently got a rx550, 2gb. Any idea if i can get more than 300h/s on cn-heavy?
Someone has good settings for MoneroV8 for the RX550? I can´t get a stable hashrate. I have 6 similiar RX550 with same bios. Hashrate is very unstable and mostly 1 card is slower then all other, and this change all 5min. Monero V7 works stable, and with SRB it works stable too, but with srb the effective pool hashrate is 400h slower then the reported hashrate.
Memory is 2Mb?Try this parameters:
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":464 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 8, "delta" : 8, "epsilon" : 8, "zeta" : 8, "index" : 1, "multi_hash":464 }
Then try to increase both multi_hash parameters untill your card have enough memory or speed became lower even at start.
Hello,
I cannot get JCE mine Stellite, do you have an example of commande line for it ?
I tryed to 0 in the fork but it doesn't work, pool is miner rocks and wallet without payment ID.
I cannot get JCE mine Stellite, do you have an example of commande line for it ?
I tryed to 0 in the fork but it doesn't work, pool is miner rocks and wallet without payment ID.
Nevermind it is an adress error, but this coin is not so good anyway.
Someone has good settings for MoneroV8 for the RX550? I can´t get a stable hashrate. I have 6 similiar RX550 with same bios. Hashrate is very unstable and mostly 1 card is slower then all other, and this change all 5min. Monero V7 works stable, and with SRB it works stable too, but with srb the effective pool hashrate is 400h slower then the reported hashrate.
Hi all!
First, a new appologize for all messages I hadn't read yet and support i skipped, i'm really lacking time.
I'm about to ship a new GPU version, with
*About the drivers 14, that was the same bug as in Stak and Xmrig, because i used the original reference code. Starting with JCE 0.33b3 my code is brand new and very different. So the bug is not fixed, it just vanished away. Tested on a HD6950 with drivers 14.12.
If you have GPUs 0, 1, 2 and 3, and want to mine ony on GPU 1 and 3 for example, add parameter:
-g 1,3
Note there's so space around the comma. -g stands for restrict Gpus to
edit:
0.33b3 GPU is online
First, a new appologize for all messages I hadn't read yet and support i skipped, i'm really lacking time.
I'm about to ship a new GPU version, with
Code:
* Fixed compatibility with AMD drivers 14*
* Tahiti-specific optimization v8 +1%
* Light optimization v8 for other GPUs
* Now only Intel and AMD devices are detected, other are just ignored
*About the drivers 14, that was the same bug as in Stak and Xmrig, because i used the original reference code. Starting with JCE 0.33b3 my code is brand new and very different. So the bug is not fixed, it just vanished away. Tested on a HD6950 with drivers 14.12.
Quote
"Failed to allocate shared Large Page, using normal memory (slower). Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower)."
That's a message about the CPU mining, because --auto also configures the CPU. To stay on GPU only, add parameter --no-cpuQuote
How can i turn off Onboard GPU?
There's a Claymore-stype parameter for this: -gIf you have GPUs 0, 1, 2 and 3, and want to mine ony on GPU 1 and 3 for example, add parameter:
-g 1,3
Note there's so space around the comma. -g stands for restrict Gpus to
edit:
0.33b3 GPU is online
Quote
Hey. RX480 video card 8GB nitro + error "Compilation of OpenCL kernels failed.
what version of drivers and Windows?Adrenalin 18.6.1
Win10x64
Here is what he writes in auto mode "Failed to allocate shared Large Page, using normal memory (slower). Failed to allocate 2MB Large Page Scratchpad Buffer, using normal memory (slower)."
Run Administrator no effect
I tried to put 8gb RAM no effect (
Quote
Hey. RX480 video card 8GB nitro + error "Compilation of OpenCL kernels failed.
what version of drivers and Windows?Adrenalin 18.6.1
Win10x64
Yes, it did not help (
I used this miner a few days.
It's so good but I have two problems.
1- How can i turn off Onboard GPU?
2- Can i add low hashrate parameters like claymore?
It's so good but I have two problems.
1- How can i turn off Onboard GPU?
2- Can i add low hashrate parameters like claymore?
Can someone help? My RX470 4GB cards cant start at all...When i start my miner at the very start my rig crash every time. I tried --auto mode and its the same. Change the setting of my cards and its still the same....THE ONLY rig that work have RX480 8GB cards ..... Using 18.5.1 and 1803win edition 60Gig virtual mem. Anyone with same problem like me?
your problem I guess is the same with _ap_ which is in auto mode 4GB GPU have 2 thread and multi_hash 864, so better use manual config 4GB GPU 1 thread multi_hash 944 or 2 thread but multi_hash 472.
Jump to: