[XMR] JCE Miner Cryptonight/forks, now with GPU! - page 34.

BS0D

newbie

Activity: 29

Merit: 0

Quote from: vmozara on November 09, 2018, 04:54:49 AM

Quote from: BS0D on November 09, 2018, 04:52:26 AM

[JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s

I've got 1800h/s with cn-tube on V64. Very good result.

Please can you share your setup?

I easily got 1800 on single vega pc but on my rigs hashrates are anywhere from 1500 to 1800. Hoping that b6 version will resolve that and provide consistent hashrate

I use that, but got one vega:
"gpu_threads_conf" :
[
{"index": 0, "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 32, "multi_hash": 960},
{"index": 0, "mode": "GPU", "worksize": 8, "alpha": 64, "beta": 16, "multi_hash": 1008}
]

This conf seems very close to max available memory usage and after miner restart it cannot allocate memory for one of threads. IDK if that is about vega memory or swapfile. It somehow keeps some data after use. SRB solves the same like issue when restarting vega and releasing memory if I'm right.

vmozara

member

Activity: 190

Merit: 59

Quote from: BS0D on November 09, 2018, 04:52:26 AM

[JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s

I've got 1800h/s with cn-tube on V64. Very good result.

Please can you share your setup?

I easily got 1800 on single vega pc but on my rigs hashrates are anywhere from 1500 to 1800. Hoping that b6 version will resolve that and provide consistent hashrate

BS0D

newbie

Activity: 29

Merit: 0

[JCE] Ultrafast CN-Heavy/Tube/HVX miner, low power, Vega56 1750+ h/s

I've got 1800h/s with cn-tube on V64. Very good result.

dnkn

newbie

Activity: 11

Merit: 0

Dunno if it's of any help to fix unstable hashrate but I settled on this config for rx570 4gb (880-910 per card).

{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":448 },
{ "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 16, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":448 },

And the same but multihash 992 gives me 1830-1870 from vega56. 11.1kh from 6 gpu rig. 1014watts. That rig has been working for 24 hours and hashrate drop was insignificant (10.9kh). But the other rx vega rig works best with multihash 960. I may be wrong but looks like both threads have to have equal multihash and that was not the case in the previous versions.

Big thanks for this great miner!

JCE-Miner

member

Activity: 350

Merit: 22

I won't comment about the speed, happy if you got it better, but about the settings: Cast, SRB, TeamRed and JCE are close source miners, with different code each. We obviously don't use the reference code (the one of XMRig/stak). So we have each our own best settings, and we don't even use the same units, SRB intensity setting (a number somewhere between 0 and ~100) is unlike my multi_hash which is often arount 500, 1000 or 2000, alpha and beta. For each miner, take time to tune, even between two revisions of same miner.

On GitHub I often get tickets from people who complain they cannot apply one-to-one their xmrstak config. I don't know how and where to say we're two unrelated software Cry

0.33b6 done, now testing. Planned fixes:

Quote

OpenCL O-2.10 bug solved
More stable hashrate
Little perf boost on all algos ~0.15%
Temperature Watchdog (AMD GPUs only)

lebuawu2

jr. member

Activity: 176

Merit: 2

Quote from: ?? on ??

My Vega56 rig is doing much better than it was on SRB. I had to adapt some of the settings I was using on SRB to JCE to get the most hash (per GPU, 1 thread with 1008 multi_hash and 1 thread with 880 multi_hash)

My RX580 8GBs are par for the course compared to SRB no matter what I tried but I'm still using JCE because I like the effective hash stat

Interesting config, is it better than both thread with multi_hash 944?

JCE-Miner

member

Activity: 350

Merit: 22

http://json.org/

Quote

ws
""
'0009' ws
'000a' ws
'000d' ws
'0020' ws

Quote

Whitespace can be inserted between any pair of tokens.

So my JSON is conformant, and said differently, JSON do'nt care about blankspaces and indentation.

0.33b6 to be released in less than one day, with the OpenCL bug O.2.10 fixed.

BS0D

newbie

Activity: 29

Merit: 0

Quote from: JCE-Miner on November 08, 2018, 02:11:46 PM

JSON: is it really forbidden by the json standard to write

Code:

"a" :
{42}

rather than

Code:

"a" :{
42}

?

It may be acceptable by json standard but any json validator fixes the code that way.
May be the problem occurs when using 'json.parse' where every single string should be understood as it should be. For example the string starting with "hashrate": should end with a value or a bracket.
I maybe wrong ofcourse.

JCE-Miner

member

Activity: 350

Merit: 22

Well configured, i should provide performances between SRB and TeamRed on CN-v8. Look at the Github doc, at the end, there are some examples of good configurations. Overall the difference is tight between the three, so if one runs better on your rig, no problem.
I'm talking about version b3 and later, on previous, my perf was pretty bad.
Even about v7, some said i was faster, some slower, it probably depends on the precise configuration, drivers and cards settings.
And a was talking about average recent cards, including RX550, 560..., not just your precise Vega.

OpenCL bug: please confirm your path contained some non-English characters. I tried with some accented letters and it fails like you. Stupid i didn't test such a common case Sad

dingdongtobias

newbie

Activity: 156

Merit: 0

Quote from: JCE-Miner on November 08, 2018, 02:11:46 PM

Hi all,

JSON: is it really forbidden by the json standard to write

Code:

"a" : 
{42}

rather than

Code:

"a" :{
42}

?
Otherwise, JCE provides a xrm-stak compatible mode, but with less info.

Fees of 2.5% on CN-v8 are those of TeamRed, JCE fees on CN-v8 (and v7, stellite, all non-heavy...) are 0.9%
But so far TeamRed is faster on the recent cards, i'm second, fees deduced. Fees included (mine are 1.6% lower) it should be a tie. I'm the fastest on older cards like HD7000 however.

Quote

Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10

I finally reproduced that error thanks to your log. This is a critical (but not dangerous as it fails at the beginning) bug. I hope i can fix it quick, otherwise i'll release the b6 with the bug and fix after.

where you get that you second ? Roll Eyes

my vegas slwer then on SRB

JCE-Miner

member

Activity: 350

Merit: 22

Quote from: Ultrasonik on November 08, 2018, 02:19:11 PM

Quote from: JCE-Miner on November 08, 2018, 02:11:46 PM

Quote

Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10

I finally reproduced that error thanks to your log. This is a critical (but not dangerous as it fails at the beginning) bug. I hope i can fix it quick, otherwise i'll release the b6 with the bug and fix after.

thanks! if I can help, I will provide the necessary information!

Yes, can you give me the full path of the folder where you start the .bat from (the current dir)?
i feel like non-standard pathes disturb the OpenCL init

yeah i got it, using some crazy exotic chars in the path. It kills the OpenCL init.
JCE, as a security, looks for any custom OpenCL dlls in its path, because this is a simple way to hack the OpenCL kernels. But when the dir is too exotic, so it just fails.

Ultrasonik

jr. member

Activity: 103

Merit: 2

Quote from: JCE-Miner on November 08, 2018, 02:11:46 PM

Quote

Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10

I finally reproduced that error thanks to your log. This is a critical (but not dangerous as it fails at the beginning) bug. I hope i can fix it quick, otherwise i'll release the b6 with the bug and fix after.

thanks! if I can help, I will provide the necessary information!

JCE-Miner

member

Activity: 350

Merit: 22

Hi all,

JSON: is it really forbidden by the json standard to write

Code:

"a" : 
{42}

rather than

Code:

"a" :{
42}

?
Otherwise, JCE provides a xrm-stak compatible mode, but with less info.

Fees of 2.5% on CN-v8 are those of TeamRed, JCE fees on CN-v8 (and v7, stellite, all non-heavy...) are 0.9%
But so far TeamRed is faster on the recent cards, i'm second, fees deduced. Fees included (mine are 1.6% lower) it should be a tie. I'm the fastest on older cards like HD7000 however.

Quote

Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10

I finally reproduced that error thanks to your log. This is a critical (but not dangerous as it fails at the beginning) bug. I hope i can fix it quick, otherwise i'll release the b6 with the bug and fix after.

UnclWish

sr. member

Activity: 1484

Merit: 253

Quote from: ?? on ??

my log

For Windows 64-bits
Detecting OpenCL-capable GPUs...
Found GPU 0, with:
Vendor: AMD
Processor: Ellesmere
Device: 01:00
Compute-Units: 32
Cache Memory: 16 KB
Local Memory: 32 KB
Global Memory: 8192 MB
Addressing: 64-bits

Preparing 2 Mining Threads...

+-- Thread 0 config ------------------------+
| Run on GPU: 0 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+

+-- Thread 1 config ------------------------+
| Run on GPU: 0 |
| Multi-hash: 864 |
| Worksize: 8 |
| Factor Alpha 64 |
| Factor Beta 16 |
+-------------------------------------------+

Cryptonight Variation: Cryptonight-BitTube v2 of July-2018

Low intensity.

Starting GPU Thread 0, on GPU 0
Created OpenCL Context for GPU 0 at 000002a5cb731410
Created OpenCL Thread 0 Command-Queue for GPU 0 at 000002a5cb7cc200
Scratchpad Allocation success for OpenCL Thread 0
Allocating big 3456MB scratchpad for OpenCL Thread 0...
Compiling kernels of OpenCL Thread 0...
Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10

Starting GPU Thread 1, on GPU 0
Created OpenCL Thread 1 Command-Queue for GPU 0 at 000002a5d14944a0
Scratchpad Allocation success for OpenCL Thread 1
Allocating big 3456MB scratchpad for OpenCL Thread 1...
Compiling kernels of OpenCL Thread 1...
Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10
GPU Watchdog minimum hashrate: 10
Keep-Alive enabled
Devfee for GPU is 2.3%

21:55:34 | OpenCL Thread 1 failed, Stop.
21:55:34 | BitTube (TUBE) Mining session starts!

21:55:34 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
21:55:34 | during this time, the hashrate may be unstable and inconsistent.
21:55:34 | Let the miner warm-up if you're tuning for performance.
21:55:34 | OpenCL Thread 0 failed, Stop.
21:55:34 | Unloaded OpenCL kernels of GPU Thread 1
21:55:34 | Unloaded OpenCL kernels of GPU Thread 0
21:55:34 | Released OpenCL Thread 1 Scratchpad at 000002a5d1a360b0
21:55:34 | Released OpenCL Thread 0 Scratchpad at 000002a5d198ddd0
21:55:34 | Released OpenCL Thread 1 Command-Queue of GPU 0 at 000002a5d14944a0
21:55:34 | Released OpenCL Thread 0 Command-Queue of GPU 0 at 000002a5cb7cc200
21:55:34 | Released OpenCL Context 000002a5cb731410 of GPU 0
21:55:35 | Connecting to mining pool bittube.miner.rocks:5555 ...
21:55:35 | Pool connection socket closed.
21:55:35 | Mining thread 0 stopped.
21:55:35 | Mining thread 1 stopped.

integrated GPU not avaiable

What about pagefile size? Did you have his size as amount of cards multiplied on 8Gb?

UnclWish

sr. member

Activity: 1484

Merit: 253

Quote from: ?? on ??

Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10
(other miners work amd rx470 , recommended driver, compute mode)

Quote from: UnclWish on November 08, 2018, 01:03:43 PM

Windows 7? It's not supported. GPU miner works only on Windows 8+.

of course i have Win 10 ! (SRB miner works without problems)
[/quote]
Did you have integrated Intel GPU? Check your devices indexes.

Lermite

newbie

Activity: 54

Merit: 0

Are you sure you didn't mess with the GPU indexes in the config file?

BS0D

newbie

Activity: 29

Merit: 0

Didn't find any ready to use jce-monitor and tried to make it myself. Being not much strong in js I've stuck with json syntax error.
Miner seems to send unvalid json with syntax like
"hashrate":
{
instead of
"hashrate": {
and
"gpu_status":
[
{
instead of
"gpu_status": [{
Will try to rewrite it later. Maybe I've missed smth. Or I'll find the way to make json valid to parse strings for html normally.

UnclWish

sr. member

Activity: 1484

Merit: 253

Quote from: Ultrasonik on November 08, 2018, 12:32:34 PM

what am I doing wrong? Cry

work only CPU but GPU error:

Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10
(other miners work amd rx470 , recommended driver, compute mode)

my BAT
set FORK=13
jce_cn_gpu_miner64.exe --no-cpu --doublecheck --watchdog 10 --retrydelay 10 --keepalive --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*

Windows 7? It's not supported. GPU miner works only on Windows 8+.

Ultrasonik

jr. member

Activity: 103

Merit: 2

what am I doing wrong? Cry

work only CPU but GPU error:

Compilation of OpenCL kernels failed.
Error: CL_BUILD_PROGRAM_FAILURE Code: O-2.10
(other miners work amd rx470 , recommended driver, compute mode)

my BAT
set FORK=13
jce_cn_gpu_miner64.exe --no-cpu --doublecheck --watchdog 10 --retrydelay 10 --keepalive --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*

1033ruben

newbie

Activity: 22

Merit: 0

Quote from: Nightworker88 on November 06, 2018, 09:18:50 PM

1033ruben

exactly with JCE miner it is complitly simple:

open the miner folder - find "start", click right mouse on it .edit.

then just change:

1. pool address
2. port number
3. ssl or no ssl
4. wallet adress.payment id
5.chosse algo : in the end of the list write number
6. last line is the .bat ( if you want change some paramaters, please read the help, does mean start the help.bat

so, for example my simple bat:

jce_cn_gpu_miner64.exe --no-cpu -g 1,2,3,4 --bus-order --doublecheck --watchdog 10 --retrydelay 10 --keepalive --auto --any --forever --variation %FORK% --low -o %POOL%:%PORT% -u %WALLET% -p %PASSWORD% %SSL% %*

Cheesy

THANKS FOR YOUR REPLY!!! I guess my question is how do I optimize it for the the cpus I recently mentioned the 8700K, RYYZEN5 1600 AND THE 6800K, and the 2 amd rigs one is 6 rx 560 and the other is 5 rx 570
THANKS IN ADVANCE
RUBEN

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