Quote from: JayDDee on January 17, 2025, 09:08:11 PM

Quote from: tatral on January 17, 2025, 08:08:51 PM

I tested each core separately on the 12700s and concluded that first 16 cores are p-type (with alternating threads) and last 4 are e-type. However when using more than 4 cores the performance only suffers. As of now the best setting is 4 p threads, using only even-numbered ones.

Indeed I use the prebuilt binaries. I'll try compiling myself and see what I get.

That's interestng. I have no personal experience with a hybrid so I'm learning too.
Yespower is I/O bound, AKA memory hard, so compute performance is less important than cache size
and memory performance. E-cores have smaller cache and lower clock but I would have expected them
to help some without interfering with the P-cores. It's basically trial and error, and it's probably different for each
CPU based on its combination of P vs E cores.

Alternating threads is pretty standard for yespower on non-hybrid CPUs, it avoids hyperthreading and distributes the cache load evenly.

If you're seeing all the CPUs the binaries should be ok, your initial post implied something weird was going on and the miner wasn't seeing all the cores.

So if yespower is memory bond than cpu speed, how i can configure the memory in Linux to work best for cpuminer-opt v25.1? Is hugepages setting has any effects for cpuminer-opt? Or that it just need ram with recent speed or l1,l2,l3 of processor size?

I am using cpuminer-opt v25.1 with yespowerr16 on Debian 12 x86_64 linux.