Re: [CPU] JCE Miner Cryptonight/forks, brand new, super fast!
Thanks, I was just typing that exact same answer : Monero is variation 3. Use --help to get the list of variations.
It warms up my heart
at least somebody uses the dual thread 
Next priority now is dual-share, which is the exact opposite (for cpu with more cache than threads, like Xeon)
About Xeon, note the thread limit is now 64, so the 40-core config we discussed here can be merged into one single JCE instance.
You can try dualmine, the config example above is good, the trick is often to dualmine the last thread with the one before
https://ark.intel.com/fr/products/90729/Intel-Core-i3-6100-Processor-3M-Cache-3_70-GHz
For you, I advise (with no way to be sure)
edit:
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.
About the core i3 : before tweaking the dual thread, try with a simple -t 4 param to force four threads. It may simply be the best config.
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
It warms up my heart
at least somebody uses the dual thread Next priority now is dual-share, which is the exact opposite (for cpu with more cache than threads, like Xeon)
About Xeon, note the thread limit is now 64, so the 40-core config we discussed here can be merged into one single JCE instance.
You can try dualmine, the config example above is good, the trick is often to dualmine the last thread with the one before
https://ark.intel.com/fr/products/90729/Intel-Core-i3-6100-Processor-3M-Cache-3_70-GHz
For you, I advise (with no way to be sure)
Code:
"cpu_threads_conf" :
[
{ "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : true, "dual_mine_with": 0 },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 2, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 3, "use_cache" : true, "dual_mine_with": 2 },
]
[
{ "cpu_architecture" : "auto", "affine_to_cpu" : 0, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 1, "use_cache" : true, "dual_mine_with": 0 },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 2, "use_cache" : true },
{ "cpu_architecture" : "auto", "affine_to_cpu" : 3, "use_cache" : true, "dual_mine_with": 2 },
]
edit:
Quote
I setup my PhenomII 955 @stock and I got 94-98H/s, startupconfig on SS.
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.
About the core i3 : before tweaking the dual thread, try with a simple -t 4 param to force four threads. It may simply be the best config.