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

Yes, indeed, he is right:

3T => 58 H/s
3T + helper => 64 H/s
4T => 70 H/s

And that despite Deneb has only 6 MB L3 cache.  But I forgot the special cache architecture of AMD systems. Intel systems have inclusive caches. So the size of the L3 cache is the maximum cacheable size, because the data in L2 and L1 are just subsets of a copy. AMD systems instead have exclusive caches, where no data is ever stored in L2 and L3 at the same time. That's why you can add L2 and L3 cache size. Deneb has 4x 512 KB L2. Together with the 6 MB L3 you get 8 MB cache altogether; or room for 4 threads. 

But it still can be helpful for non-AES Intel CPUs with limited L3 (Lynnfield) or for Phenom II X6 to use the last two cores, as well

Dual mine forbidden with AES and Cryptonight Heavy.
AES because it's always far worse than regular threads, Heavy because there's no longer smooth parts in cryptonight version Heavy, so threads have no longer any resource to share.

Dual is for non-aes, C-Night[v7], C-Light[v7], 32 or 64 bits.

The L3 cache of the G4400 is not big enough for 2 Monero threads. Use just one either or switch to a cryptonight-lite coin like TurtleCoin. Then you can use both cores without flooding the cache.

For Windows 64-bits
Analyzing Processors topology...
Intel(R) Pentium(R) CPU G4400 @ 3.30GHz
Architecture codename: Skylake
  SSE2          : Yes
  SSE3          : Yes
  SSE4          : Yes
  AES           : Yes
  AVX           : No

Found CPU 0, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  3072 KB, shared with CPU 1
Found CPU 1, with:
  L1 Cache:    32 KB
  L2 Cache:   256 KB
  L3 Cache:  3072 KB, shared with CPU 0

Preparing 2 Mining Threads...

+-- Thread 0 config -----------------------------+
| Run on CPU:             0                      |
| Use cache:              yes                    |
| Assembly module:        generic_aes            |
+------------------------------------------------+

+-- Thread 1 config -----------------------------+
| Run on CPU:             1                      |
| Use cache:              yes                    |
| Assembly module:        generic_aes            |
+------------------------------------------------+

Cryptonight Variation: Cryptonight V7 fork of April-2018

Low intensity.
Starting Mining thread 0, affinity: CPU 0
Thread 0 successfully bound to CPU 0
Allocated shared Large Page at: 0000027232a00000
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 0 of NUMA node 0 at: 0000027232c00000
Starting Mining thread 1, affinity: CPU 1
Thread 1 successfully bound to CPU 1
Allocated 2MB Cached Large Page Scratchpad Buffer for CPU 1 of NUMA node 0 at: 0000027232e00000
Connecting to mining pool pool.minexmr.com:4444 ...
Devfee is 1.5%

00:18:36 | Monero (XMR) Mining session starts!

Intel Pentium G4400 @ 3.30GHz 2 cores 52.71 H/s monero, 11 watts.

Four threads ? So it's better to use 4 normal threads than 3 + dualmine ? [heart broken]
If that's what you say, so it's another proof the dual mine is useless outside the very rare case of a 2M-cache dual core cpu.

Four threads ? So it's better to use 4 normal threads than 3 + dualmine ? [heart broken]
If that's what you say, so it's another proof the dual mine is useless outside the very rare case of a 2M-cache dual core cpu.

You set algo variation 4 - this is cryptolightV7. Check your pool address and port. Did you right chose algo for your pool and port? Maybe you want to cryptonightV7? This is 3 variation algo...

Without dual mining the Phenom II X4 905e hashes up to 58 H/s. Thanks to dual mining on the last core, it's 64 H/s

I setup my PhenomII 955 @stock and I got 94-98H/s, startupconfig on SS.

Intel® Core i5-6600 Processor

config.txt


start.bat exe line


640 H/S at 30 watts, monero

I always get "Low difficulty share" error. I tried different difficulties, no change. Any ideas?

Thanks

Dual mining is perfect for AMD Phenom II X4. It has an L3 cache of 6 MB, so 3 cryptonight threads fit into it. But is has 4 cores, so with a normal miner, one core is without a job. Thanks to dual mining I can fill the L3 with 3 threads and add a "helper thread" to the 4th core. It looks like this:

"cpu_threads_conf" :
[
     { "cpu_architecture" : "deneb", "affine_to_cpu" : 0, "use_cache" : true },
     { "cpu_architecture" : "deneb", "affine_to_cpu" : 1, "use_cache" : true },
     { "cpu_architecture" : "deneb", "affine_to_cpu" : 2, "use_cache" : true },
     { "cpu_architecture" : "deneb", "affine_to_cpu" : 3, "use_cache" : true, "dual_mine_with": 2 },
]

Without dual mining the Phenom II X4 905e hashes up to 58 H/s. Thanks to dual mining on the last core, it's 64 H/s

The only CPU so far where i saw a perf increase was a core2 duo Conroe (2 cores, 2M cache).

Hi

Just finish testing dualmining as you recommended, the good news, shares are accepted, the bad news hash decreased to 128 and system freezes after a couple minutes.

Gonna test 0.21 right now.

Thanks.