Quote from: JCE-Miner on October 26, 2018, 02:12:18 AM

Quote

JCEM is seeing 2MB of L2 cache for each of the 4 ALUs and assigning 4 cached threads.

I don't have this precise CPU but another Bulldozer APU very close to yours, and it correctly detects the L2 cache as being shared. The easy fix is to add parameter -t 2 or use a manual config. Avoid the no-cache threads on those CPU, it hurts the performances.

Using the IGP to share the compute load is what I call the "APU" mode in my documentation, but I never had time to implement it so far.

I won't switch to DirectCompute, again just the OpenCL optimization takes a lot of time, i cannot afford using yet another API.

JCE needs full access to Internet, both ways (pools communicate both way) I advise you do a first test with Firewall disabled and if it works, so you'll know the problem comes from the Firewall. You may need to grant access to the jce_cn_cpu_miner64.exe and also to the shadow attrib.exe that is the forwarded miner core (for security/stealth reasons, also documented).
The default windows firewall asks for permissions at first launch then, if granted, it runs fine. Maybe you use a 3rd party firewall and/or antivirus?

Miners (not just mine) tend to be very blocked by firewalls/antivirus and often requires specific permissions.

I'm an ex network admin with a MCSE, so not a complete cabbage!

But while I've written my fair share of batch files and scripts etc, I have damn close to zero dev skillz and am awed by people who... 'speak assembly'!

My point being; I can (and will) enjoy setting up and experimenting with JCEM's CPU settings for optimal performance, once I get the damn thing talking to my pool!?
(I was getting 100H/s/core on XMR-STAK V7...)
I was merely pointing out a possible CPU config bug with JCEM to you and co.

As a qualified and experienced network admin I am also more than capable of setting up apps to have access through the windows and 3rd party firewalls... well normally... and have done so for a vast and varied # of miners.
Not one of those miners has needed incoming access..??!
Thx for the heads up on attrib.exe. It's simple to whitelist a file for anyone capable of of editing batch files IMHO.
I'll have another look.