Quote from: Dmitry69 on July 10, 2018, 08:54:26 AM

GPU:sapphire RX550 2GB(1071/1500@1100/1950) + CPU: XEON E5430, Hash: 490H/s + 82H/s
Win10x64(ver:1709), drv: Win7-Crimson-ReLive-Beta-Blockchain-Workloads-Aug23.
Back on SRBminer(1.6.3) + JCE_cpu_miner.(0.31c), Hash: 482H/s + 82H/s

This is a very interresting point.

Let's imagine something: Since I've dedicated netcode for Nicehash, it would be very simple for me just not to report the bad shares. I would display a correct physical 490 H/s and no reject.
Question: in such case, would you come back to JCE?

The morale to understand is about the Effective hashrate, do you get a better real-life hashrate on JCE than on other miners? A lot of user say so. Don't get too focused on error messages, and especialy not on those from Nicehash which has a very strange behavior, look at the real end results. If JCE displays more errors, maybe that's just because it never hides any one.

About nicehash, it has a zero tolerance about Stale shares. If a share gets stale a the very end of its computation, JCE doesn't drop it and still send it to Nicehash, in case it could be accepted, betting on the ping delay. If it fails, it logs the failure. Normal.

Btw, i get better results with multi_hash 432 or 464, and reaches ~518, which is crazy considering the rx550 is such a small low power card. But the RX550 and 560 depend a lot on the memory quality, my worse rx560 never went above 355h/s, which is stupid low.

I still have room for CN-Heavy optims, but i'm getting stuck with my old cards, they're close to hardware max and do not report well the speed increases. My bonaire for example is still at 268 h/s whatever i try, and claymore was also maxing at that exact same number.
On my dual HD 7950 i'm now at 1096, still behind claymore 9.7 (1146) but above other miners.

Back to CPU, JCE is supposed to be the fastest, since i'm the only dev to use dedicated assemblies for every possible combination of CPU+algo+multihash+cache+..... This is why the binary is a trillion times bigger than others. Also i've found a OpenCL optim i could port back to CPU, even the 64-bits. The hashrate may be something like +0.2% higher. Since i'm playing with the hardware max, that's a welcome improvement, yet negligeible.

Quote from: Larvitar on July 10, 2018, 02:03:52 PM

JCE-Miner, I'm running now the miner in my 2nd Ryzen. Is a Ryzen 5 1600 at 3.75GHz, RAM at 2933.
It's the --auto tuning the best optimisation so far to R5 1600?

The best CN-Light/Turtle/Aeon config for R 1600 is in the github doc:

Code:

"cpu_threads_conf" :
[
{ "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true, "multi_hash":2 },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : true, "multi_hash":1 },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 2, "use_cache" : true, "multi_hash":1 },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 3, "use_cache" : true, "multi_hash":1 },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 4, "use_cache" : true, "multi_hash":1 },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 5, "use_cache" : true, "multi_hash":1 },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 6, "use_cache" : true, "multi_hash":2 },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 7, "use_cache" : true, "multi_hash":1 },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 8, "use_cache" : true, "multi_hash":1 },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 9, "use_cache" : true, "multi_hash":1 },
{ "cpu_architecture" : "auto", "affine_to_cpu" :10, "use_cache" : true, "multi_hash":1 },
{ "cpu_architecture" : "auto", "affine_to_cpu" :11, "use_cache" : true, "multi_hash":1 },
]

This is the best configuration to mine Cryptolight, TurtleCoin or IPBC on a Ryzen 1600/1600X (12 logical CPUs, 16M cache).

IPBC is no longer Light, now it's Heavy, i need to update my doc.