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

Tested heavy on xmrig... Speed is lower about 4-5% on RX 588 than max speed on JCE, but stable...
For me xmrig unacceptible - it doesn't work properly on latest drivers! Many compute errors!
JCE, waiting your fixed version!

XMR Stak didn't work with 14.4 driver.... XMRig start hashing but freez or make driver crash and stop hashing.

i've try to reinstall image with new w8.1 OS and try again with 14.4 Driver JCE Miner in auto mode or manual config ==> the driver crash.

Hi JCE, I'm testing on my 3 - 6950 card with 0.33b4 /0.33b6 i've also try  8 and 16 worksize. But i didn't understand whats is alpha and beta values ?!

2 VTX 6950 2Gb
1 Gigabyte 6950 2Gb
Also A Pitcairn GPU but didn't try yet.

2 os on W8.1 64
1 os on W10 x64

No card mine, and don't have error. I've never seen any hash start 

I post  my config perhaps  and i did it something wrong ?!

My start cmd file

ce_cn_gpu_miner64.exe --no-cpu -c config.txt -o pool.supportxmr.com:5555  -u 44kXLYVXRE############PDcW4kQx+5000 -p 6950_JCE

pause

Log File

Analyzing Processor topology...
AMD Athlon(tm) Processor 1640B
Assembly codename: athlon64
  SSE2    : Yes
  SSE3    : Yes
  SSE4    : No
  AES     : No
  AVX     : No
  AVX2    : No
Found CPU 0, with:
  L1 Cache:    64 KB
  L2 Cache:   512 KB
Detecting OpenCL-capable GPUs...
Found GPU 0, with:
  Vendor:                         AMD
  Processor:                   Cayman
  Device:                       02:00
  Compute-Units:                   22
  Cache Memory:                  0 KB
  Local Memory:                 32 KB
  Global Memory:              2048 MB
  Addressing:                 32-bits
Preparing 1 Mining Threads...

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

Cryptonight Variation: Cryptonight V8 fork of Oct-2018


Starting GPU Thread 0, on GPU 0
Created OpenCL Context for GPU 0 at 000001c29b8c6660
Created OpenCL Thread 0 Command-Queue for GPU 0 at 000001c29d012f80
Scratchpad Allocation success for OpenCL Thread 0
Allocating big 1728MB scratchpad for OpenCL Thread 0...
Compiling kernels of OpenCL Thread 0...
Kernels of OpenCL Thread 0 compiled.
09:02:21 | Monero (XMR/XMV) Mining session starts!

09:02:21 | GPU Compute allocation starts at 80% and reaches 100% after ~5min,
09:02:21 | during this time, the hashrate may be unstable and inconsistent.
09:02:21 | Let the miner warm-up if you're tuning for performance.
09:02:22 | Connecting to mining pool pool.supportxmr.com:5555 ...
09:02:22 | Connected to pool. Now logging in...
09:02:22 | Successfuly logged as 44kXLYVEmkUXRECm8eza1PF###############EJ9cePDcW4kQx+5000
09:02:22 | Pool changes Difficulty to 5000.
09:02:23 | Pool sends a new Job.
09:02:53 | Hashrate GPU Thread 0: 0.00 h/s - Total GPU 0: 0.00 h/s
09:02:53 | Total: 0.00 h/s - Max: 0.00 h/s
09:03:02 | GPU 0: Temp: 37C - Fan: 24% -- Shares: Good: 0 Bad: 0
09:03:45 | Pool sends a new Job.
09:04:49 | Pool sends a new Job.
09:05:59 | Pool sends a new Job.
09:06:14 | Stop signal received, Quitting...

that's ok to give the news, and yeah i no longer can pretend i've a high lead on cn-heavy, i'll edit my doc to remove that statement and lower back the fees. i got the lead for... one or two weeks. i expected TeamRed to release a fast Heavy code, not xmrig i admit.

I'm not sure it's right to mention another miner in this thread but I think it may help the author to fix the heavy hashrate bugs. The thing is that latest xmrig has managed to achieve very good speeds on heavy and it's stable. I've switched all my rigs to test it and it does the job. I'm getting  ~1800h from vega 56 and ~920-960h from 570 4gb and ~400 from r7 370 and ~580-600h from 560 4gb but unstable. So 560s are working with jce 0.33b4
It's open source so it's easy to see how it was achieved.

It was b6 version and haven algo.
There was no big gpus, only rx470 4gb that shows really the same hashrate with r9 290x

But shares sent and effective hashrate is low for 290x and normal for rx470
It is not diff problem as I had also weak cpu mining along with gpus in this miner windows. It has much lower hashrate but reported and effective values are very close.
So I think it is some kind of hardware errors that I cannot see in miner output or some bug in haven (heavy) code for Tahiti/Hawaii

I confirmed the same problem on another test rig with vega56, rx570 8gb and r9 390 8gb. While vega and rx570 show correct numbers - hawaii 390 card reported more hashrate than actual one based on submitted shares.

First rig was using old Aug23 blockchain drivers. Test rig is using 18.5.1 driver


Please provide settings of your test so I can try to reproduce with my cards

I don't fake my numbers, and especially not on such a corner market as the old HD7000/6000 mining Heavy. However, the result are intriguing, what version do you use? If that's the B-X, so it could be false negative shares (good shares badly detected as wrong and thus not sent to pool) which would say my hybrid sync still need fixes, even on HD7000.
If that's on the b5/b6, so... i've little explaination so far, except that my new implementation itself (not counting the hybrid parts) is glitchy and already produces a lot of false negative. In such case, it would be a very major bug. I'll do some emergency tests, lucky i've a lot of old cards to test on.

A less extreme explanation would be that you used (explicitly or not) a very high Diff, making your fast card on ease but not your slow cards. In such case, the effective hashrate of the slow cards would start low and converge to the theorical hashrate after a very long time. Like when you mine with CPU on Nicehash.

for HD6950, a user on Github advises to use worksize=32 and multi_hash=864, one one thread.
Take a look at the HD6000 user topic here:
https://github.com/jceminer/cn_gpu_miner/issues/26

also try with worksize=16 and 8

edit: hashing Ryo with low Diff (5000) on my dual HD7950 (totaling 845h/s) and 840h/s effective hashrate so far with the B-x, with 1% bad shares, as expected. I strongly advise you redo your test with either a fixed low Diff or your big GPU paused.

Hello i'm new with your Miner

I've 3 - 6950 card so i'm very interesting by your miner !

On win10 x64 and 14.4 amd driver in auto mod i've NO hash.
i also try on Win8.1 and 14.4 no hash too.

I'vre try -c and manuel config "the gpu_thread_conf"

Could you tell me what to write in the config file for get best HASH ? (i d'idnt fine explanation about parameters)

Thx for your work, i hope u can help me  

2 jce-miner

It seems that your miner shows fake hashrate mining heavy on old cards

This is the report for shares and effective hashrate
08:41:58 | * GPU 0 -  350/0/0 - 251.91 h/s
08:41:58 | * GPU 1 -  352/0/0 - 253.35 h/s
08:41:58 | * GPU 2 - 1052/0/0 - 757.17 h/s
08:41:58 | * GPU 3 -  594/0/0 - 427.53 h/s

This is common hashrate report

08:45:36 | Hashrate GPU Thread 3: 371.92 h/s - Total GPU 0: 371.92 h/s
08:45:36 | Hashrate GPU Thread 4: 356.66 h/s - Total GPU 1: 356.66 h/s
08:45:36 | Hashrate GPU Thread 5: 395.44 h/s
08:45:36 | Hashrate GPU Thread 6: 395.14 h/s - Total GPU 2: 790.58 h/s
08:45:36 | Hashrate GPU Thread 7: 785.26 h/s - Total GPU 3: 785.26 h/s

GPU0 and 1 are hd7990
GPU 2 is rx470 4gb
GPU3 is R9 290x 4gb

Parameters are

"gpu_threads_conf" :
[
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 0, "multi_hash":672 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 1, "multi_hash":672 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 2, "multi_hash":464 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 2, "multi_hash":464 },
     { "mode" : "GPU", "worksize" : 8, "alpha" : 64, "beta" : 8, "gamma" : 4, "delta" : 4, "epsilon" : 4, "zeta":4, "index" : 3, "multi_hash":864 },
],


So, on Vega and Polaris cards your miner shows correct estimation of hashrate. On Hawaii and Tahiti - more than 1.5 times "fake"

@migo77

I've got a request for a CentOS (and other old linuxes) support on Github, didn't compared if it was you, i may do it but I cannot give this a high priority considering the little dev time I have. It would be the niche (old os) of a niche (linux) of a niche (cpu minning).

To get more speed from your Dual-Xeon, set-up this manual config:


The first part should be as good, or a bit better than the actual config.
Then enable some of the extra lines below, add them one by one while it gives extra performance.
That's theorical, i don't own the same Xeon as you, but i expect you can get more speed than with stak.

proxy: nope, no proxy nor socks support, it would allow illegal use of JCE as a embedded trojan/malware or on corporate servers. It's probably hackable, but i won't give any support for this.
This is the security rule Claymore applied (no proxy, no socks) and i do the same.
On claymore it connected but hashed bad on purpose. I prefer just forbid it.

about trojan: I know JCE is flagged as virus/trojan/nuclear waste/whatever but there's nothing i can do, that's documented, just disable your AV or add an exception. The github page itself is still online, your browser AV blocks it.

Version b7 on the way, with:
* Reworked the Heavy code (again)
* bad shares mostly fixed
* Speed gain ~2% backported to the HD6000s
* AES parts removed from my code generator, making JCE start faster.

Also version 0.33g for CPU with better support of MoneroOcean parameters, and CN-Fest

JCE, make next version with bad shares fix, please!

Could you add a linux cli option for mining via socks proxy ?

like the -x option in cpuminer : -x SOCKS5://127.0.0.1:9050

Thanks 

The warm-up behavior isn't just since b5.  I reported this a month or two ago (in this forum) on at least 32q, for 580s mining heavy/variants.  Given that it almost always eventually finds the optimal h/r (and stays there,) coupled w/ this being the most stable miner i've used (i.e. long uptimes,) i haven't been terribly bothered by it.

I have yet to migrate off of 32q, so can't offer much insight on current performance/behavior.

Yes, on b-x version max speed on RX 588 achieved often after 5-6 min. But after some time, 10-15+ minutes, speed start to fluctuate on 1 of GPUs and drops about 20%, after several minutes it start to flactuate on others GPUs and drops speed about 20-25% too.
Maybe when you test b-x version and after reaching max speed you can see 5-10 minutes stable max speed.

hey bud, your github page has been flagged as malicious when i try to download the latest GPU version with firefox.... I tried another github page and doesnt show same msg.

+ when i open the zip 033b6, before extracting, my antivirus detect Skeeyah.a!rfn trojan ....

I have 033b2 version AND when i open the 033b2 zip the antirivus doesnt detect a trojan !

Look over it, your GitHub account might be compromised.

I'll wait before updating

Hi JCE, yes I know about configuration options and I'm using them I'm linux admin with experience I'm interested in your high efficiency on old HW, but in some cases I cant' achieve it.

That old opteron is detected as generic_sse2 and speed is the same as xmr-stak that I'm using, it is around 150h/s with arch set to athlon64 I see nice increase in hr with JCE at 170h/s which is fine and worth higher fee. That athlon reports sse4a instruction set, but your algorithm for sse4 doesn't work. I checked various thread/cache/multihash options and this is max I was able to achieve. Is there anything else we can do for more optimizations?

JCE runs fine on:

Dual Intel(R) Xeon(R) CPU E5450 @ 3.00GHz
Assembly codename: core2_sse4
  SSE2    : Yes
  SSE3    : Yes
  SSE4    : Yes
  AES     : No
  AVX     : No
  AVX2    : No

Found CPU 0, with:
  L1 Cache:    32 KB
  L2 Cache:  6144 KB, shared with CPU 2
Found CPU 2, with:
  L1 Cache:    32 KB
  L2 Cache:  6144 KB, shared with CPU 0
Found CPU 4, with:
  L1 Cache:    32 KB
  L2 Cache:  6144 KB, shared with CPU 6
Found CPU 6, with:
  L1 Cache:    32 KB
  L2 Cache:  6144 KB, shared with CPU 4
Found CPU 1, with:
  L1 Cache:    32 KB
  L2 Cache:  6144 KB, shared with CPU 3
Found CPU 3, with:
  L1 Cache:    32 KB
  L2 Cache:  6144 KB, shared with CPU 1
Found CPU 5, with:
  L1 Cache:    32 KB
  L2 Cache:  6144 KB, shared with CPU 7
Found CPU 7, with:
  L1 Cache:    32 KB
  L2 Cache:  6144 KB, shared with CPU 5

HTTP Local Server on port 16000

Preparing 8 Mining Threads...

+-- Thread 0 config ------------------------+
| Run on CPU:            0                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       core2_sse4         |
+-------------------------------------------+

+-- Thread 1 config ------------------------+
| Run on CPU:            1                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       core2_sse4         |
+-------------------------------------------+

+-- Thread 2 config ------------------------+
| Run on CPU:            2                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       core2_sse4         |
+-------------------------------------------+

+-- Thread 3 config ------------------------+
| Run on CPU:            3                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       core2_sse4         |
+-------------------------------------------+

+-- Thread 4 config ------------------------+
| Run on CPU:            4                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       core2_sse4         |
+-------------------------------------------+

+-- Thread 5 config ------------------------+
| Run on CPU:            5                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       core2_sse4         |
+-------------------------------------------+

+-- Thread 6 config ------------------------+
| Run on CPU:            6                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       core2_sse4         |
+-------------------------------------------+

+-- Thread 7 config ------------------------+
| Run on CPU:            7                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       core2_sse4         |
+-------------------------------------------+

Cryptonight Variation: Cryptonight V8 fork of Oct-2018


Starting CPU Thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0x7f556c800000
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7f556c600000

Starting CPU Thread 1, affinity: CPU 1
Thread 1 successfully bound to CPU 1
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7f556c400000

Starting CPU Thread 2, affinity: CPU 2
Thread 2 successfully bound to CPU 2
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7f556c200000

Starting CPU Thread 3, affinity: CPU 3
Thread 3 successfully bound to CPU 3
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7f5566400000

Starting CPU Thread 4, affinity: CPU 4
Thread 4 successfully bound to CPU 4
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7f5565800000

Starting CPU Thread 5, affinity: CPU 5
Thread 5 successfully bound to CPU 5
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7f5564c00000

Starting CPU Thread 6, affinity: CPU 6
Thread 6 successfully bound to CPU 6
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7f5564000000

Starting CPU Thread 7, affinity: CPU 7
Thread 7 successfully bound to CPU 7
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7f554b400000
Devfee for CPU is 3%

18:30:13 | Monero (XMR/XMV) Mining session starts!

During mining time, press:
 h      display hashrate for each mining thread.
 r      display full report.
 p      pause all.
 q      quit.

18:30:14 | Connecting to mining pool pool.supportxmr.com:5555 ...
18:30:14 | Connected to pool. Now logging in...
18:30:14 | Successfuly logged as 48DZQquvFBjGCi3KcVCGDUhHbCZpgaAjTC5siqZd9K7ogfAKajwbG2hLS8NBy4CjAuCsqAAUywpXMEN vgv17YyP4RCWh94n
18:30:14 | Pool changes Difficulty to 10000.
18:30:30 | Pool sends a new Job.
18:30:44 | Hashrate CPU Thread 0: 27.73 h/s
18:30:44 | Hashrate CPU Thread 1: 27.72 h/s
18:30:44 | Hashrate CPU Thread 2: 27.72 h/s
18:30:44 | Hashrate CPU Thread 3: 27.72 h/s
18:30:44 | Hashrate CPU Thread 4: 27.72 h/s
18:30:44 | Hashrate CPU Thread 5: 27.73 h/s
18:30:44 | Hashrate CPU Thread 6: 27.72 h/s
18:30:44 | Hashrate CPU Thread 7: 27.72 h/s
18:30:44 | Total: 221.74 h/s - Max: 221.74 h/s

on this system is JCE faster 221h/s than XMR-stak  180h/s.

The BAD:

On other xeon boxes I can't achieve better performance than xmr-stak at all e.g.:

{
  "hashrate":
  {
    "thread_0": 18.95,
    "thread_1": 18.95,
    "thread_2": 18.95,
    "thread_3": 18.94,
    "thread_4": 19.04,
    "thread_5": 19.04,
    "thread_6": 19.04,
    "thread_7": 19.03,
    "thread_all": [18.95, 18.95, 18.95, 18.94, 19.04, 19.04, 19.04, 19.03],
    "total": 151.89,
    "max": 152.69
  },
  "result":
  {
     "reconnections": 0,
     "currency": "Monero (XMR/XMV)",
     "difficulty": 5000,
     "shares": 5265,
     "hashes": 26334400,
     "uptime": "49:23:16",
     "effective": 148.12
  },
  "miner":
  {
     "version": "jce/0.33f/cpu",
     "platform": "Dual Intel(R) Xeon(R) CPU E5520 @ 2.27GHz",
     "system": "Linux 64-bits",
     "algorithm": "15"
  }
}

On this system is hr same as with xmr-stak but fee is higher.

Another "problematic" system is:

Analyzing Processors topology...
Dual Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz
Assembly codename: generic_aes_avx
  SSE2    : Yes
  SSE3    : Yes
  SSE4    : Yes
  AES     : Yes
  AVX     : Yes
  AVX2    : No

Found CPU 0, with:
  L1 Cache:    32 KB, shared with CPU 12
  L2 Cache:   256 KB, shared with CPU 12
  L3 Cache: 15360 KB, shared with CPU 12, 1, 13, 2, 14, 3, 15, 4, 16, 5, 17
Found CPU 12, with:
  L1 Cache:    32 KB, shared with CPU 0
  L2 Cache:   256 KB, shared with CPU 0
  L3 Cache: 15360 KB, shared with CPU 0, 1, 13, 2, 14, 3, 15, 4, 16, 5, 17
Found CPU 1, with:
  L1 Cache:    32 KB, shared with CPU 13
  L2 Cache:   256 KB, shared with CPU 13
  L3 Cache: 15360 KB, shared with CPU 0, 12, 13, 2, 14, 3, 15, 4, 16, 5, 17
Found CPU 13, with:
  L1 Cache:    32 KB, shared with CPU 1
  L2 Cache:   256 KB, shared with CPU 1
  L3 Cache: 15360 KB, shared with CPU 0, 12, 1, 2, 14, 3, 15, 4, 16, 5, 17
Found CPU 2, with:
  L1 Cache:    32 KB, shared with CPU 14
  L2 Cache:   256 KB, shared with CPU 14
  L3 Cache: 15360 KB, shared with CPU 0, 12, 1, 13, 14, 3, 15, 4, 16, 5, 17
Found CPU 14, with:
  L1 Cache:    32 KB, shared with CPU 2
  L2 Cache:   256 KB, shared with CPU 2
  L3 Cache: 15360 KB, shared with CPU 0, 12, 1, 13, 2, 3, 15, 4, 16, 5, 17
Found CPU 3, with:
  L1 Cache:    32 KB, shared with CPU 15
  L2 Cache:   256 KB, shared with CPU 15
  L3 Cache: 15360 KB, shared with CPU 0, 12, 1, 13, 2, 14, 15, 4, 16, 5, 17
Found CPU 15, with:
  L1 Cache:    32 KB, shared with CPU 3
  L2 Cache:   256 KB, shared with CPU 3
  L3 Cache: 15360 KB, shared with CPU 0, 12, 1, 13, 2, 14, 3, 4, 16, 5, 17
Found CPU 4, with:
  L1 Cache:    32 KB, shared with CPU 16
  L2 Cache:   256 KB, shared with CPU 16
  L3 Cache: 15360 KB, shared with CPU 0, 12, 1, 13, 2, 14, 3, 15, 16, 5, 17
Found CPU 16, with:
  L1 Cache:    32 KB, shared with CPU 4
  L2 Cache:   256 KB, shared with CPU 4
  L3 Cache: 15360 KB, shared with CPU 0, 12, 1, 13, 2, 14, 3, 15, 4, 5, 17
Found CPU 5, with:
  L1 Cache:    32 KB, shared with CPU 17
  L2 Cache:   256 KB, shared with CPU 17
  L3 Cache: 15360 KB, shared with CPU 0, 12, 1, 13, 2, 14, 3, 15, 4, 16, 17
Found CPU 17, with:
  L1 Cache:    32 KB, shared with CPU 5
  L2 Cache:   256 KB, shared with CPU 5
  L3 Cache: 15360 KB, shared with CPU 0, 12, 1, 13, 2, 14, 3, 15, 4, 16, 5
Found CPU 6, with:
  L1 Cache:    32 KB, shared with CPU 18
  L2 Cache:   256 KB, shared with CPU 18
  L3 Cache: 15360 KB, shared with CPU 18, 7, 19, 8, 20, 9, 21, 10, 22, 11, 23
Found CPU 18, with:
  L1 Cache:    32 KB, shared with CPU 6
  L2 Cache:   256 KB, shared with CPU 6
  L3 Cache: 15360 KB, shared with CPU 6, 7, 19, 8, 20, 9, 21, 10, 22, 11, 23
Found CPU 7, with:
  L1 Cache:    32 KB, shared with CPU 19
  L2 Cache:   256 KB, shared with CPU 19
  L3 Cache: 15360 KB, shared with CPU 6, 18, 19, 8, 20, 9, 21, 10, 22, 11, 23
Found CPU 19, with:
  L1 Cache:    32 KB, shared with CPU 7
  L2 Cache:   256 KB, shared with CPU 7
  L3 Cache: 15360 KB, shared with CPU 6, 18, 7, 8, 20, 9, 21, 10, 22, 11, 23
Found CPU 8, with:
  L1 Cache:    32 KB, shared with CPU 20
  L2 Cache:   256 KB, shared with CPU 20
  L3 Cache: 15360 KB, shared with CPU 6, 18, 7, 19, 20, 9, 21, 10, 22, 11, 23
Found CPU 20, with:
  L1 Cache:    32 KB, shared with CPU 8
  L2 Cache:   256 KB, shared with CPU 8
  L3 Cache: 15360 KB, shared with CPU 6, 18, 7, 19, 8, 9, 21, 10, 22, 11, 23
Found CPU 9, with:
  L1 Cache:    32 KB, shared with CPU 21
  L2 Cache:   256 KB, shared with CPU 21
  L3 Cache: 15360 KB, shared with CPU 6, 18, 7, 19, 8, 20, 21, 10, 22, 11, 23
Found CPU 21, with:
  L1 Cache:    32 KB, shared with CPU 9
  L2 Cache:   256 KB, shared with CPU 9
  L3 Cache: 15360 KB, shared with CPU 6, 18, 7, 19, 8, 20, 9, 10, 22, 11, 23
Found CPU 10, with:
  L1 Cache:    32 KB, shared with CPU 22
  L2 Cache:   256 KB, shared with CPU 22
  L3 Cache: 15360 KB, shared with CPU 6, 18, 7, 19, 8, 20, 9, 21, 22, 11, 23
Found CPU 22, with:
  L1 Cache:    32 KB, shared with CPU 10
  L2 Cache:   256 KB, shared with CPU 10
  L3 Cache: 15360 KB, shared with CPU 6, 18, 7, 19, 8, 20, 9, 21, 10, 11, 23
Found CPU 11, with:
  L1 Cache:    32 KB, shared with CPU 23
  L2 Cache:   256 KB, shared with CPU 23
  L3 Cache: 15360 KB, shared with CPU 6, 18, 7, 19, 8, 20, 9, 21, 10, 22, 23
Found CPU 23, with:
  L1 Cache:    32 KB, shared with CPU 11
  L2 Cache:   256 KB, shared with CPU 11
  L3 Cache: 15360 KB, shared with CPU 6, 18, 7, 19, 8, 20, 9, 21, 10, 22, 11

HTTP Local Server on port 16000

Preparing 13 Mining Threads...

+-- Thread 0 config ------------------------+
| Run on CPU:            1                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

+-- Thread 1 config ------------------------+
| Run on CPU:            2                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

+-- Thread 2 config ------------------------+
| Run on CPU:            3                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

+-- Thread 3 config ------------------------+
| Run on CPU:            4                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

+-- Thread 4 config ------------------------+
| Run on CPU:            5                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

+-- Thread 5 config ------------------------+
| Run on CPU:            6                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

+-- Thread 6 config ------------------------+
| Run on CPU:            7                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

+-- Thread 7 config ------------------------+
| Run on CPU:            8                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

+-- Thread 8 config ------------------------+
| Run on CPU:            9                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

+-- Thread 9 config ------------------------+
| Run on CPU:            10                 |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

+-- Thread 10 config -----------------------+
| Run on CPU:            11                 |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

+-- Thread 11 config -----------------------+
| Run on CPU:            0                  |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

+-- Thread 12 config -----------------------+
| Run on CPU:            12                 |
| Use cache:             yes                |
| Multi-hash:            no                 |
| Assembly module:       generic_aes_avx    |
+-------------------------------------------+

Cryptonight Variation: Cryptonight V8 fork of Oct-2018


Starting CPU Thread 0, affinity: CPU 1
Thread 0 successfully bound to CPU 1
Allocated shared Large Page at: 0x7fcd5e800000
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fcd5e600000

Starting CPU Thread 1, affinity: CPU 2
Thread 1 successfully bound to CPU 2
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fcd5da00000

Starting CPU Thread 2, affinity: CPU 3
Thread 2 successfully bound to CPU 3
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fcd5ce00000

Starting CPU Thread 3, affinity: CPU 4
Thread 3 successfully bound to CPU 4
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fcd5c200000

Starting CPU Thread 4, affinity: CPU 5
Thread 4 successfully bound to CPU 5
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fcd47400000

Starting CPU Thread 5, affinity: CPU 6
Thread 5 successfully bound to CPU 6
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fcd46800000

Starting CPU Thread 6, affinity: CPU 7
Thread 6 successfully bound to CPU 7
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fcd45c00000

Starting CPU Thread 7, affinity: CPU 8
Thread 7 successfully bound to CPU 8
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fcd45000000

Starting CPU Thread 8, affinity: CPU 9
Thread 8 successfully bound to CPU 9
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fcd44400000

Starting CPU Thread 9, affinity: CPU 10
Thread 9 successfully bound to CPU 10
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fcd44200000

Starting CPU Thread 10, affinity: CPU 11
Thread 10 successfully bound to CPU 11
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fcd2ec00000

Starting CPU Thread 11, affinity: CPU 0
Thread 11 successfully bound to CPU 0
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fcd2e000000

Starting CPU Thread 12, affinity: CPU 12
Thread 12 successfully bound to CPU 12
Allocated 2MB Cached Large Page Scratchpad Buffer at: 0x7fcd2d400000
Devfee for CPU is 1.5%

20:08:43 | Monero (XMR/XMV) Mining session starts!

During mining time, press:
 h      display hashrate for each mining thread.
 r      display full report.
 p      pause all.
 q      quit.

20:08:43 | Connecting to mining pool pool.supportxmr.com:5555 ...
20:08:43 | Connected to pool. Now logging in...
20:08:44 | Successfuly logged as 48DZQquvFBjGCi3KcVCGDUhHbCZpgaAjTC5siqZd9K7ogfAKajwbG2hLS8NBy4CjAuCsqAAUywpXMEN vgv17YyP4RCWh94n
20:08:44 | Pool changes Difficulty to 10000.
20:08:55 | CPU Thread 7 finds a Share, value 10000
20:08:55 | Accepted by the pool in 38 ms.
20:09:01 | Hashrate CPU Thread 0: 48.65 h/s
20:09:01 | Hashrate CPU Thread 1: 47.42 h/s
20:09:01 | Hashrate CPU Thread 2: 47.11 h/s
20:09:01 | Hashrate CPU Thread 3: 48.59 h/s
20:09:01 | Hashrate CPU Thread 4: 48.64 h/s
20:09:01 | Hashrate CPU Thread 5: 49.15 h/s
20:09:01 | Hashrate CPU Thread 6: 49.35 h/s
20:09:01 | Hashrate CPU Thread 7: 48.02 h/s
20:09:01 | Hashrate CPU Thread 8: 48.00 h/s
20:09:01 | Hashrate CPU Thread 9: 49.49 h/s
20:09:01 | Hashrate CPU Thread 10: 49.28 h/s
20:09:01 | Hashrate CPU Thread 11: 36.67 h/s
20:09:01 | Hashrate CPU Thread 12: 36.23 h/s
20:09:01 | Total: 606.55 h/s - Max: 606.55 h/s

With JCE is 607h/s maximal hr but with xmr-stak I'm on 650h/s. Tested with various core/thread/cache options. Can we do it better?  

And I have 180 little core2duo miners on which can your miner shine, but I need version for old glib, because I can't upgrade env on this machines due users sw limitations.  I've commented on bug reported and some guy compiled xmrig staticaly for me which works like this:

1|proxy-lo | 2018-11-16 18:27 +01:00: The proxy currently has 171 miners connected at 2294 h/s with an average diff of 134
1|proxy-lo | 2018-11-16 18:27 +01:00: The proxy currently has 171 miners connected at 2293 h/s with an average diff of 134
1|proxy-lo | 2018-11-16 18:27 +01:00: Received new block template from pool.supportxmr.com
1|proxy-lo | 2018-11-16 18:27 +01:00: The proxy currently has 171 miners connected at 2293 h/s with an average diff of 134

I can test for you if you have som experiments if needed and maybe we can make your miner better If I'm bothering you with too much technical details let me know I'll stop. Maybe you can suggest some options, optimizations or something that can help.

Thanx.

b-x
3x RX 550 2GB (1315MHz core, 2050MHz mem, drivers 18.11.1, Win 10 1809)


I see there better h/s, but it drops to the way it was in b6. and waves

Using the B-X version yields a combined hashrate in the range of 838 to 841 on two radeon hd 7850s (pitcairn), up from 825-828 on b6, so about a 10h/s improvement or ~1,6% increase.
After an uptime of 7 hours, 425 good shares and 0 bad shares have been found.
Total hashrate for gpu0 is approximately 413,96 h/s (this has a 1440p display plugged into it) and for gpu1 is 426,39 h/s (no display).
Oc gpu0: 1230 core, 1420 mem.
Oc gpu1: 1205 core 1432 mem.

The following launch parameter was used with miningpoolhub . Omitting '--no-warmup' yields a very unstable hashrate.

The config.txt had to be slightly changed for the B-X version. Previously this config was used:

but on the newer version this config yields a better result

Furthermore, there's a 1-4 h/s difference between using multi_hash:416 on thread 1 on gpu0 (multi_hash:432 on thread 2), and using multi_hash:416 on thread 2 (multi_hash:432 on thread 1) on gpu0. Overall, from this very brief testing, the B-X version seems better than b6 on these gpus. Thank you for your hard work and time!
Edit: Forgot to mention, the driver used is Adrenalin Edition 18.6.1

Interresting, i hope i can understand and fix that hashrate speed bug

The hybridness is an internal detail, from the user point of view, Nothing changes.
I could make the CPU usage negligible, so that's normal you don't see any difference.

I'm making the 0.33b7 which will be the b-x with a little more "hybridness" for weak cards, and the bad shares fixed, or at least a lot less frequent.
To be release in a few days.

On v8 i can mine at 470 h/s on my HD7950 with b7, and 427 on Heavy, that's a lot faster than other miners. But few people still mine with such old cards.
Algo switch for devfee is on SRB only, i never switch algo on GPU (on CPU i do, but for MoneroOcean, not for fees).

Still, it may have been some netcode desync or something, i had fixed a lot of related bugs, but you may have had bad luck and found it at first try. Not impossible.

edit: the b7 still give higher and more stable hashrate on my RX rig, but that's the 3rd time i observe such. Maybe some mental bias. BTW it's quite good compared to b6 so i'll release once my tests are done.