Folding Forum

CPU: 13th Gen Intel(R) Core(TM) i9-13900K

So far I am seeing 200K PPD @5.4MHz out of the box. No tweaking yet.
Motherboard: MSI Z790 Carbon WiFi
RAM: 16G DDR5 Kingston Fury Beast
GPU: RTX4090
Cooler: MSI Coreliquid 280R
PSU: MSI MPG A1000G

If it is a single folding slot using all available threads, it's definitely not good ... limit the slot thread number to the number of performance threads.

I spent a little time with it. When set to -1, the cpu:30. I experimented with setting the cpu to 8, 16 and 20 and didn't see any real difference in performance. Project 16969.

That sounds either problematic or disappointing.

My ~8-year-old e5-2690v0 @ 2.9GHz (turbo boost OFF, DL380g8) running CPU:30 gets ~270k PPD on p16969.

FWIW I have found that v0 (32nm) cpus far outperform v1 and v2 (22nm) cpus for F@H. I have only worked with the Xeons of this generation, not the consumer level chips.

Ben N1NP

red454 wrote: ↑Fri Nov 11, 2022 1:10 am I experimented with setting the cpu to 8, 16 and 20 and didn't see any real difference in performance.

You should see most performance when limiting the number of threads to fit your P-cores only. As FaH overall performance is capped by the performance of your slowest CPU core, you don't want to share work between P-cores and E-cores.

Things are complicated by Windows 11 dumb scheduler which doesn't understand complications like this, which might get into its head to put work on E-cores if you run FaH on more than 8 threads. Try setting 16 threads (assuming no GPU folding!) and disable E-cores altogether and see what happens... Because of the limited smarts of the scheduler, I'm not sure how effective it will be to create two FaH CPU cores, one with 16 threads for your P-cores and one with however many threads you want to dedicate on the E-cores. Who knows where each thread will end up, as Windows tends to throw threads around all over the CPU for no seemingly good reason.